Page 59 of 110
Rev. G
e. Client ID: This is a value included in the header of each message. It is used
as part of the default topic name. In addition, it can just be used by the
broker to help identify a publisher. If left at Default, mCore’s serial number
will be used.
f. Site Name: This value is a string that is inserted into the JSON packet and
can be used as a “hint” as to the source, but is not part of the topic name..
g. Username and Password: These are the credentials to authenticate the
publisher to the broker.
h. Publication Topic: This field is where you enter a string that will be the
topic name for the data published by mCore. If left at Default, the topic will
be mCore/client-id/pub, where client-id is the Client ID setting. Since this
itself defaults to the serial number, leaving both at default will produce a
topic of mCore/mc-0000-0000/pub where mc-0000-0000 is the serial
number of mCore.
i. Compression: We do offer two types of compression, gzip and zlib.
However, you do not have to use any compression and the subscriber
MUST be able to decompress the packets. Compression is transparent to
the broker.
j. 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.
k. 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.
l. Maximum Backoff: this setting is the maximum amount of time it will back
off when a connection cannot be established.
m. Publication QoS: MQTT has three Quality of Service settings. They are:
i. 0=Fire and Forget.
ii. 1=Send At Least Once by using an acknowledge to ensure that the
packet was received. Note that with this setting you are guaranteed
to get a packet once, but it could be received MORE than once. This
To Next Page
Loading...