Sebastián Pastor
/
EtheriosCloudConnector
Important changes to repositories hosted on mbed.com
Mbed hosted mercurial repositories are deprecated and are due to be permanently deleted in July 2026.
To keep a copy of this software download the repository Zip archive or clone locally using Mercurial.
It is also possible to export all your personal repositories from the account settings page.
Embed:
(wiki syntax)
Data Structures
Here are the data structures with brief descriptions:
| connector_config_connect_type_t | Connection action which is used to to tell the connector to make connection to Device Cloud automatically or manually |
| connector_config_connection_type_t | Device connection type configuration for connector_request_id_config_connection_type callback |
| connector_config_device_id_method_t | Device ID method configuration returned by the application's callback for connector_request_id_config_device_id_method callback |
| connector_config_error_status_t | Error status structure for connector_request_id_config_error_status callback which is called when Cloud Connector encounters an error |
| connector_config_identity_verification_t | Identify verification configuration for connector_request_id_config_identity_verification callback |
| connector_config_ip_address_t | Device IP Address Configuration for connector_request_id_config_ip_addr callback |
| connector_config_keepalive_t | Keep-alive interval configuration used for the following callbacks: |
| connector_config_link_speed_t | Device link speed configuration for WAN connection type for connector_request_id_config_link_speed callback |
| connector_config_max_transaction_t | Device maximum transaction configuration for connector_request_id_config_max_transaction callback |
| connector_config_pointer_data_t | Application Binary Data Pointer Configuration for the following callbacks: |
| connector_config_pointer_string_t | Application String Pointer Configuration for the following callbacks: |
| connector_config_supported_t | Service supported status configuration for the following callbacks: |
| connector_config_vendor_id_t | Vendor ID configuration for connector_request_id_config_vendor_id callback |
| connector_config_wait_count_t | Device wait count configuration for connector_request_id_config_wait_count callback |
| connector_config_wan_type_t | Device WAN type configuration for connector_request_id_config_wan_type callback |
| connector_data_point_response_t | The data in the callback with request id connector_request_id_data_point_binary_response and connector_request_id_data_point_single_response will point to this data structure |
| connector_data_point_status_t | The data in the callback with request id connector_request_id_data_point_binary_status and connector_request_id_data_point_single_status will point to this data structure |
| connector_data_point_t | Data structure to make a linked list of data points to send it out in one transaction |
| connector_data_service_length_t | The callback data with request ID connector_request_id_data_service_send_length and connector_request_id_data_service_receive_reply_length will point to this structure |
| connector_data_service_receive_data_t | The callback data with request ID connector_request_id_data_service_receive_data will point to this structure |
| connector_data_service_receive_reply_data_t | The callback data with request ID connector_request_id_data_service_receive_reply_data will point to this structure |
| connector_data_service_receive_target_t | The callback data with request ID connector_request_id_data_service_receive_target will point to this structure |
| connector_data_service_send_data_t | The callback data with request ID connector_request_id_data_service_send_data will point to this structure |
| connector_data_service_send_response_t | The callback data with request ID connector_request_id_data_service_send_response will point to this structure |
| connector_data_service_status_t | The callback data with request ID connector_request_id_data_service_send_status and connector_request_id_data_service_receive_status will point to this structure |
| connector_file_system_close_t | Data structure used in connector_request_id_file_system_close callback |
| connector_file_system_get_error_t | Data structure used in connector_request_id_file_system_get_error callback, to get error status and description for a previously recorder error token |
| connector_file_system_hash_t | Data structure used in connector_request_id_file_system_hash callback |
| connector_file_system_lseek_t | Data structure used in connector_request_id_file_system_lseek callback |
| connector_file_system_open_t | Data structure used in connector_request_id_file_system_open callback |
| connector_file_system_opendir_t | Data structure used in connector_request_id_file_system_opendir callback |
| connector_file_system_read_t | Data structure used in connector_request_id_file_system_read callback |
| connector_file_system_readdir_t | Data structure used in connector_request_id_file_system_readdir callback |
| connector_file_system_remove_t | Data structure used in connector_request_id_file_system_remove callback |
| connector_file_system_session_error_t | Data structure used in connector_request_id_file_system_session_error callback |
| connector_file_system_stat_dir_entry_t | Data structure used in connector_request_id_file_system_stat_dir_entry callback, used to get status for for each directory entry in the directory path, received from Device Cloud for ls request |
| connector_file_system_stat_t | Data structure used in connector_request_id_file_system_stat callback, used to get status for a path received from Device Cloud for ls request |
| connector_file_system_statbuf_t | File status data structure is used to return the status of a directory or a file, specified by the path |
| connector_file_system_truncate_t | Data structure used in connector_request_id_file_system_ftruncate callback |
| connector_file_system_write_t | Data structure used in connector_request_id_file_system_write callback |
| connector_firmware_count_t | Firmware target count for connector_request_id_firmware_count callback which is called to return number of supported targets |
| connector_firmware_download_abort_t | Firmware download abort structure for connector_request_id_firmware_abort callback which is called when firmware download process is aborted |
| connector_firmware_download_complete_t | Firmware download complete structure containing information about firmware image data for connector_request_id_firmware_download_complete callback which is called when Device Cloud is done sending all image data |
| connector_firmware_download_data_t | Firmware download image data structure for connector_request_id_firmware_download_data callback which is called when the connector receives a block of image data for firmware download |
| connector_firmware_download_start_t | Firmware download start structure for connector_request_id_firmware_download_start callback which is called when the device is requested for firmware download |
| connector_firmware_info_t | Firmware information structure for connector_request_id_firmware_info callback to return information about the specific target |
| connector_firmware_reset_t | Firmware target reset structure for connector_request_id_firmware_reset callback which is called to reset the target |
| connector_firmware_version_t | Firmware version structure for connector_request_id_firmware_info callback to return the firmware version about the specific target |
| connector_initiate_stop_request_t | This data structure is used on connector_initiate_transport_stop in Initiate Action API to stop a transport |
| connector_network_close_t | Close request structure for connector_request_id_network_close callback which is called to close the connection to Device Cloud |
| connector_network_open_t | Network open data structure for connector_request_id_network_open callback which is called to open and connect to Device Cloud |
| connector_network_receive_t | Read request structure for connector_request_id_network_receive callback which is called to receive a specified number of bytes data from Device Cloud |
| connector_network_send_t | Send data structure for connector_request_id_network_send callback which is called to send data to Device Cloud |
| connector_os_free_t | Structure passed to connector_request_id_os_free callback |
| connector_os_malloc_t | Structure passed to connector_request_id_os_malloc callback |
| connector_os_system_up_time_t | Structure passed to connector_request_id_os_system_up_time callback |
| connector_os_yield_t | Structure passed to connector_request_id_os_yield callback |
| connector_request_data_point_binary_t | This data structure is used when the connector_initiate_action() API is called with connector_initiate_binary_point request id |
| connector_request_data_point_single_t | This data structure is used when the connector_initiate_action() API is called with connector_initiate_data_point_single request id |
| connector_request_data_service_send_t | This structure is used when sending a data to Device Cloud with connector_initiate_action() call.The action ID used for this call is connector_initiate_send_data |
| connector_request_id_t | Request IDs passed to callback identifying the type of request |
| connector_sm_cancel_request_t | This data structure is used when the device initiates the cancel session request |
| connector_sm_cli_request_t | This data structure is used when the callback is called to pass the CLI request received from Device Cloud |
| connector_sm_cli_response_length_t | This data structure is used when the callback is called to get the CLI response length |
| connector_sm_cli_response_t | This data structure is used when the callback is called to get the CLI response to Device Cloud |
| connector_sm_cli_status_t | This data structure is used when the callback is called to indicate the termination of CLI session |
| connector_sm_more_data_t | This data structure is used when the callback is called with the connector_request_id_more_data |
| connector_sm_opaque_response_t | This data structure is used when the callback is called to pass Device Cloud response for which the associated request is not present |
| connector_sm_ping_response_t | This data structure is used when the callback is called with the connector_request_id_sm_ping_response |
| connector_sm_receive_config_request_t | This data structure is used when the the callback is called with the connector_request_id_sm_config_request |
| connector_sm_receive_ping_request_t | This data structure is used when the the callback is called with the connector_request_id_sm_ping_request |
| connector_sm_send_ping_request_t | This data structure is used when the device initiates the ping request to Device Cloud |
| connector_status_tcp_event_t | TCP status structure is used for connector_request_id_status_tcp callback |
| connector_time_epoch_fractional_t | The data structure to represent seconds and milliseconds since the epoch (00:00:00 UTC on 1 January 1970) |
| connector_time_epoch_whole_t | The data structure to represent milliseconds since the epoch (00:00:00 UTC on 1 January 1970) |
Generated on Tue Jul 12 2022 19:18:39 by
1.7.2