Revised 2017-08-31
Services Tab
Drawing No. LP0997-C
RAMQTT Client
Sixnet
®
Series SN/RAM
®
6000 & RAM 9000 Software Manual
- 161 -
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)
Allow Incoming Messages:
If set to Yes, RAMQTT will subscribe to topics needed to receive messages from
the Broker. Use this option if RAMQTT should handle incoming messages.
If set to No, RAMQTT will not subscribe to any topics and will not receive any messages from the Broker. Use
this option if RAMQTT should only publish data.
3.5.14.8
All
IoT
Cloud
Service
Providers
Points:
Add (single) Point, or Add Multiple Points by entering the Tag Name, selecting the Type from the drop
down (when adding one point at a time) or pop up list (when adding multiple points). Points can also be
removed after identifying them and clicking on the Remove button.
Refresh, Apply, Test Connection, Show Status:
Use these buttons to refresh the screen, apply the changes,
test the connection or display status of the RAMQTT Client.
Base 1 0
: This toggles the system-wide register display format, which can be represented in two schemes:
Zero-based or One-based. Zero-Based is also called Native format, and all register ranges would begin
counting at 0. One-Based addressing starts all ranges with 1, and is the system commonly used with Modbus.
Each register label consists of the Tag name, followed by the address in two parts: type and address. Type and
address will change to match the Zero (Native) and One (Modbus) formatting conventions. An untagged
register will show an implied tag in <angle brackets>.
Messages
Minimum Publish Interval (seconds):
Minimum time in seconds between published I/O data point
messages. Messages are published as soon as any value changes, but subsequent changes will be separated
by this amount of time to prevent flooding. Increase this value to reduce data usage from high-frequency
changes. The acceptable value range is from 1 to 65535.
Device Info Message:
Choose the type of Device Info message to be sent. This is in addition to the I/O data
point update messages.
The standard message options are:
MESSAGE OPTION
MESSAGE DESCRIPTION
MESSAGE CONTENT
None
Sends no message
None