Page 72 of 110
Rev. G
m. Keep Alive Period: If there are no packets sent within this time, mCore will
send a small packet to keep the connection open and prevent
disconnection from the broker.
n. Initial Backoff: If mCore cannot establish a connection with the broker it
will back off for this time period and then try again. If it still does not get a
connection, it will double this value and will continue to try at longer and
longer multiples of this time setting.
o. Maximum Backoff: this setting is the maximum amount of time it will back
off when a connection cannot be established.
p. Publication QoS: MQTT has three Quality of Service settings. They are:
1. 0=Fire and Forget.
2. 1=Fire and Wait for acknowledgement. Note: with this setting
you are guaranteed to get a packet once, but it could be
received MORE than once. This level can slow data flow
considerably depending on the network latency.
3. 2=Fire and Wait for acknowledgement only ONCE. Note: this
ensures you will get the packet ONLY ONCE guaranteed, but it
also slows down the data flow drastically depending on the
system latency.
q. Subscription QoS: Same as above when acting as a subscriber.
r. Connection Timeout: this is the setting for how long to wait for a
connection to be established before entering the Initial Back off period.
s. Publication Timeout: This setting describes the amount of time to wait for
an acknowledgement from a publication message.
t. Subscription Timeout: This setting describes the amount of time to wait for
an acknowledgement from a subscription message.
4. At the Group Level, you can setup how you want each data group to trigger to
send.
To Next Page
Loading...