Contents
Cirrus Link Resources
Cirrus Link Website
Contact Us (Sales/Support)
Forum
Cirrus Link Modules Docs for Ignition 7.9.x
Inductive Resources
Ignition User Manual
Knowledge Base Articles
Inductive University
Forum
...
Optional MQTT client ID to use. If specified this will be used in the MQTT Transmission connect packet when connecting to the server. If left blank, a random client ID will be create of the form 'MT-xxxxxxxx-xxxx-xxxx'.
Warning |
---|
Caution: MQTT Clients IDs must be unique and if two clients attempt to connect with the same client ID, one will be forcefully disconnected from the server to allow the other client to connect. |
Anchor | ||||
---|---|---|---|---|
|
If the server does not receive, at minimum, a PINGREQ message from a client within 1.5 times the Keep Alive, it will terminate the connection and send the client's LWT if it has been defined.
For MQTT Transmission, this is an DEATH message.
...
Note |
---|
If both the Random Startup Delay and the Reconnect Delay are configured, the startup delay for any one client will be the aggregate of the two configured values. For example, with the Random Startup Delay = 10-1000ms and the Reconnect Delay = 1000ms, the startup delay for any one client will be between 1010 and 2000ms |
Anchor | ||||
---|---|---|---|---|
|
This section was added in release 4.0.18
...
Anchor | ||||
---|---|---|---|---|
|
Tip |
---|
Available in MQTT Transmission 4.0.16 and newer |
...
through 4.0.22 support the propagation of alarm events from the Edge to MQTT Engine on the Central Gateway to be inserted in the Ignition Alarm Journal but do not support the remote acknowledgment of those alarms MQTT Transmission 4.0.23 and newer support the propagation of alarm events from the Edge to MQTT Engine on the Central Gateway to be inserted in the Ignition Alarm Journal along with acknowledgements from the Central Gateway back to the Edge Review the Alarm Event Propagation document for system configuration details including the changes needed |
When enabled and alarms are enabled on tags, the contents of the triggered alarms will be transmitted via Sparkplug to MQTT Engine and will be inserted into the Ignition Alarm Journal on the server where MQTT Engine is installed.
Note |
---|
This is not full alarm support as the ability to clear or ack an alarm from MQTT Engine is not currently supported |
...
to the data/ignition.conf file and MQTT Engine |
When enabled and alarms are enabled on tags, the contents of the triggered alarms will be transmitted via Sparkplug to MQTT Engine and will be inserted into the Ignition Alarm Journal on the server where MQTT Engine is installed.
but replace the 'XX' with the proper index per the wrapper.java.additional statements:Anchor | ||||
---|---|---|---|---|
|
...
Warning |
---|
If using multiple Disk-Back History Stores, the TCP Database Port must be unique for each one. This requirement applies to all Disk-Backed History Stores (MQTT Transmission and all Injectors), MQTT Engine Alarm Stores and Chariot MQTT Server (uses TCP Port 9092) if co-located on the same platform |