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.
Run routine
Include: connector_api.h More...
| Functions | |
| connector_status_t | connector_run (connector_handle_t const handle) | 
| Runs Cloud Connector as a blocking call. | |
Detailed Description
Include: connector_api.h
Function Documentation
| connector_status_t connector_run | ( | connector_handle_t const | handle ) | 
Runs Cloud Connector as a blocking call.
This blocking function is typically used in a separate thread (in a multi-threaded environment) to run Cloud Connector after it's been successfully initialized with an connector_init() call. This function only returns when Cloud Connector encounters an unexpected error. This function is similar to connector_step() except this is the blocking variant.
See Cloud Connector Threading Model section for more information on the differences between connector_run() and connector_step().
- Parameters:
- 
  [in] handle Handle returned from connector_init() call. 
- Return values:
- 
  connector_init_error Cloud Connector was not properly initialized. The application requires a call to connector_init() prior to calling this function. connector_abort Cloud Connector was aborted by callback function. connector_invalid_data_size An application callback returned an invalid response_length. This is an application callback defect and should be corrected. To locate the faulty callback, enable CONNECTOR_DEBUG. For more information on debugging, see the section on how to implement debug support. connector_invalid_data_range An application callback returned invalid response_data. This is an application callback defect and should be corrected. To locate the faulty callback, enable CONNECTOR_DEBUG. For more information on debugging, see the section on how to implement debug support. connector_keepalive_error Cloud Connector did not receive keep alive messages. Device Cloud may be offline. connector_bad_version Device Cloud rejected version number. connector_exceed_timeout Callback exceeded timeout value before it returned. connector_unsupported_security Cloud Connector received a packet with unsupported security. connector_invalid_data An application callback returned unexpected NULL response_data. This is an application callback defect and should be corrected. To locate the faulty callback, enable CONNECTOR_DEBUG. For more information on debugging, see the section on how to implement debug support. connector_device_error Close Callback returns error. If connector_step or connector_run is called again, it will re-establish the connection. connector_device_terminated Cloud Connector was terminated by user via connector_initiate_action call. 
Example Usage:
connector_status_t status; connector_handle_t connector_handle = connector_init(application_callback); status = connector_run(connector_handle);
Definition at line 556 of file connector_api.c.
Generated on Tue Jul 12 2022 19:18:38 by
 1.7.2
 1.7.2