MQTT settings for receiving tag data from multiple Ignition edge systems

Ignition Modules
, ,
1

Hello,

We make mobile units that have ignition edge systems that send tag data over mqtt to our main system.
When activating and recieving data from a single unit there are no issues and everything is working great. However, when we activate a second unit we get bad stale error on all of our tag bindings in Perspective. We have noticed that the connection to the edge systems go in and out of online status while both are connected. Has anyone ever encountered this issue or similar issue using MQTT? Both units have unique IP adresses and function fine by themselves. The communication issue arises only when more than one is connected.

1 Like
2

The most common causes for this are colliding MQTT Client IDs or colliding Sparkplug Edge Node Descriptors. Take a look at this tutorial to help identify the problem: https://docs.chariot.io/display/CLD80/I+have+data+that+is+toggling+between+stale+and+healthy+at+my+subscribing+MQTT+Client
If you are not able to resolve, reach out to our support team support@cirrus-link.com

3

I have been researching this article, and i have a hunch that it is colliding sparkplug edge node descritptors as the tag path on both ignition edge systems are identical, e.g. “[edge]MQTT External/BIDI/AC_Current” on both systems. Does this mean I have to change the “[edge]” to something unique to avoid this issue?

Then all our tag bindings have to be unique for each system and a lot of manual work is required to set up each new system?

4

We ended up solving the issue by making the combination of Group ID and edge node ID unique. Before we had the uniqueness in our device ID, which caused the issue. This was the sparkplug settings

1 Like
5

Cross linking parallel topics: