![]() ![]() This timeout represents the maximum duration that is allowed for no data transmission over the network through the transport send function. When sending an MQTT packet, the transport send function may be called multiple times until all of the required number of bytes are sent. The maximum duration between non-empty network transmissions while sending an MQTT packet via the MQTT_ProcessLoop or MQTT_ReceiveLoop API functions. Recommended to use a small timeout value. Possible values: Any positive 32 bit integer. Note If a dummy implementation of the MQTTGetCurrentTimeFunc_t timer function, is supplied to the library, then MQTT_RECV_POLLING_TIMEOUT_MS MUST be set to 0. If the timeout expires, the MQTT_ProcessLoop and MQTT_ReceiveLoop functions return MQTTRecvFailed. ![]() This timeout represents the maximum polling duration that is allowed without any data reception from the network for the incoming packet. When an incoming MQTT packet is detected, the transport receive function may be called multiple times until all of the expected number of bytes of the packet are received. The maximum duration between non-empty network reads while receiving an MQTT packet via the MQTT_ProcessLoop or MQTT_ReceiveLoop API functions. Possible values: Any positive integer up to SIZE_MAX. In that case, the value of MQTT_PINGRESP_TIMEOUT_MS is irrelevant to the behavior of the library. If a dummy implementation of the MQTTGetCurrentTimeFunc_t timer function, is supplied to the library, then the keep-alive mechanism is not supported by the MQTT_ProcessLoop API function. Note If this value is more than half of the keep alive interval, and the server does not receive the previous ping request, then it is likely that the server will disconnect the client before MQTTKeepAliveTimeout can be returned. ![]() If a ping response is not received before this timeout, then MQTT_ProcessLoop will return MQTTKeepAliveTimeout. Maximum number of milliseconds to wait for a ping response to a ping request as part of the keep-alive mechanism. If a custom config is provided, then MQTT_DO_NOT_USE_CUSTOM_CONFIG should not be defined. Without the custom config, the MQTT library builds with default values of config macros defined in core_mqtt_config_defaults.h file. They can be set with a #define in the config file ( core_mqtt_config.h) or by using a compiler option such as -D in gcc.ĭefine this macro to build the MQTT library without the custom config file core_mqtt_config.h. Some configuration settings are C pre-processor constants, and some are function-like macros for logging. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |