Page History

...

Let’s start by confirming the connection status of the Edge Nodes with your Chariot or MQTT Distributor or Chariot broker instance server instance to identify which issue you have.

Anchor

...

ChariotClient ChariotClient

Chariot 

From the Chariot UI navigate to the 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.

Image Added

Anchor
DistributorClient DistributorClient

...

MQTT Distributor

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.

...

From the Chariot UI navigate to the 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.

Image Removed

Anchor
CollidingClientID CollidingClientID

Colliding Client ID

...

In the video below we have two transmitters with a tag tree of Company/Location/Process Area/Line/PLC where Line is the physical Edge Node device. With the tag path for the transmitter set to My Company, we can see that both edge nodes will publish on the following namespaces:

...

As a result, the MQTT Client will mark the data as stale and request a rebirth from the transmitter. Depending on the frequency of the published data this manifests as the data from different edge nodes toggling between stale and healthy. If you have multiple MQTT Clients subscribing to the namespace, this will likely create a firestorm of rebirth requests across the system.

We will use the logging associated with your Chariot or MQTT Engine instance to determine the physical or virtual Edge Nodes with duplicate Group and Node IDs.

From the Chariot UI navigate to the Alerts in the left menu bar. Select Types and enable the alerts for SPARKPLUG_GROUP_EDGE_COLLISION

Under Live Alerts, we can see in the logs the Edge Node ID along with the Client IDs causing the collisions.