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
Page History
...
Let’s start by confirming the connection status of the Edge Nodes with your Chariot or MQTT Distributor server instance to identify which issue you have.
| Anchor | ||||
|---|---|---|---|---|
|
From the Chariot UI navigate to Alerts in the left menu bar. Select Types and enable the alerts for MQTT_DISCONNECT
Under Live Alerts, if we can see in the logs that Chariot is logging the DUPLICATE_CLIENT_ID description, as shown below, you have Colliding Client IDs. If not, we have a Colliding Edge Node IDs issue.
| Anchor | ||||
|---|---|---|---|---|
|
From the Ignition UI connected to your instance of MQTT Distributor, navigate to Status > Diagnostic > Logs.
...
If we can see in the logs that the MQTT broker is continually forcefully disconnecting an existing connection to allow another client with the same Client ID to connect, as shown below, you have Colliding Client IDs. If not, we have a Colliding Edge Node IDs issue.
| Anchor | ||||
|---|---|---|---|---|
|
To resolve the colliding Client IDs you will need to review your system configurations on the physical Edge Nodes identified and remove the conflicts.
...
| Tip |
|---|
| Refer to the MQTT Transmission Transmitters and Tag Trees Tutorial/HowTo for detail on how a virtual Edge Node is dynamically created. |
| Anchor | ||||
|---|---|---|---|---|
|
MQTT Transmission uses the Sparkplug B specification which defines the topic namespace to publish data as spBv1.0/group_ID/message_type/edge_ID/[device_ID]
...
Now we can use the logging associated with your Chariot or MQTT Engine/Distributor instance to determine the physical or virtual Edge Nodes with duplicate Group and Node IDs.
| Anchor | ||||
|---|---|---|---|---|
|
From the Chariot UI navigate to Alerts in the left menu bar. Select Types and enable the alerts for SPARKPLUG_GROUP_EDGE_COLLISION
...
The next step is to review and update as necessary the configuration for each of the listed Client IDs. If using MQTT Transmission, see here for how to identify the Client IDs from Ignition Designer.
| Anchor | ||||
|---|---|---|---|---|
|
From the Ignition UI connected to your instance of MQTT Engine, navigate to Status > Diagnostic > Logs.
...
The next step is to review and update as necessary the configuration for each of the listed Client IDs. If using MQTT Transmission, see here for how to identify the Client IDs from Ignition Designer.
| Anchor | ||||
|---|---|---|---|---|
|
To identify the MQTT Client ID for each Edge Node in Designer, select the Tag Browser MQTT Transmission and expand the Transmission Info folder tree for each of your transmitters to expose the MQTT Client. ID.
| Anchor | ||||
|---|---|---|---|---|
|
To resolve the colliding Edge Node IDs you will need to review your system configurations which generated each of the conflicting Edge Nodes and remove the conflicts.
...
| Note |
|---|
| When troubleshooting remember that an update to any MQTT Transmission configuration parameter or a forced refresh of a transmitter, will mean that any dynamic Client IDs will be recreated. New logs will have reviewed after the update or refresh in order to correctly identify the problematic edge Nodes. |
| Anchor | ||||
|---|---|---|---|---|
|
If the troubleshooting tips did not help you resolve your issues, please open a ticket with Support making sure to include the MQTT Engine or MQTT Distributor logs as appropriate.
From the Ignition Logs view, select the Download icon to download a copy of the system-name.idb file to your local file system. You will need to compress (zip, 7z or rar) this file before sending to Support.
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
Overview
Content Tools