Services Tab
Revised 2017-08-31
RAMQTT Client
Drawing No. LP0997-C
- 156 -
Sixnet
®
Series SN/RAM
®
6000 & RAM 9000 Software Manual
If Already Registered is selected enter:
•
Device API Key:
The Device API Key is used to allow the device to publish to topics on the cloud.
Note:
This will be auto generated if the device auto-registers using the Master API Key.
•
Device ID:
The Device ID is used to identify which device on the cloud will receive messages from this
device.
Note:
This will be auto generated if the device auto-registers using the Master API Key.
Messages
See Messages
on page -161
Advanced Settings
Port:
Enter the port number associated with the Broker IP address or Domain Name.
The standard ports for MQTT are:
•
Unencrypted: 1883
•
Encrypted: 8883
Keep Alive (seconds):
The Keep Alive value is the maximum time in seconds an idle connection will be
allowed. If no data needs to be transmitted for this period, then an empty Keep Alive packet will be transmitted
to maintain the connection as active with the server. If the Keep Alive is set to 0, it will be disabled. The
acceptable value range is from 1 to 65535.
Caution:
Low values may generate large amounts of unnecessary data.
•
Recommended Setting: The optimal setting is unique to Cloud Service Provider.
Generic: 2 Hours (7200 seconds)
Fusion Connect: Less than 5 Minutes (285 seconds)
Retain Messages:
When the device publishes a message with the retain option selected as
Yes
, all new
subscribers to the topic will receive this message immediately. This allows new subscribers to get information
about the device without having to wait until the next publish interval.
Track Server Responses:
If this option is enabled, RAMQTT will receive a response message from the
Broker explaining the status of the message for each message sent. This allows RAMQTT to get more detailed
information on errors that the Broker might report.
Note:
Since each message sent to the Broker will trigger a received message from the Broker, this
will create additional overhead and increase overall data usage.
Use Message History:
Select whether RAMQTT will record data in between publish intervals. If this option is
enabled, RAMQTT will record changes as they happen and store them until RAQMQTT is ready to publish
changes. This allows messages to contain a history of changes instead of only the latest values.
3.5.14.3
Autodesk
®
Fusion
Connect
General
IoT Cloud:
Select the name of the Cloud Service Provider, from the drop down list, that will be receiving
messages from this device.
•
Autodesk Fusion Connect
Root Topic:
The text in this field will act as the root topic for MQTT messages being sent to the Broker.
For example, if the root topic is “redlion”, then all topics published by this device will be like the following:
•
Go"<root topic>/<device serialnumber>/<sub topic>""redlion/9721X12345678912/pressure"