We are looking to consolidate two different Ignition projects onto one Ignition instance.
Both projects evolved to use the Cirrus Link MQTT modules. One project connects to an AWS broker (using TLS and certs) while another connects to a local broker via Cirrus Link Distributor (no certs, basic connection).
The local MQTT connection works fine and pulls in data until I enable the AWS server connection. At that point the AWS broker pulls in data and works fine, but the local MQTT connection stops reporting data.
The only way to recover the local MQTT server connection is to disable the AWS connection, then restart the MQTT Engine module.
What is happening here? There is obviously a conflict here but I don’t even know where to start looking for it. Any guidance would be very appreciated!
What version of Ignition and of our Engine module? Any other modules from Cirrus Link on this Gateway? Versions?
I should see the Server Set column which is not shown in you screen shot. Odd.
To have two simultaneous connections you will need two Server Sets, one for each MQTT Server configured, and a second Transmitter. Associate the new Server Set with the appropriate Transmitter.
Thank you for your reply. When I compare the server I’m working on w/ the one I’m porting from I do see a difference. The one in question (without the set tab) is engine version 4.0.21. The distributor (hosting the local broker) is also version 4.0.21.
My other Ignition server which has the set tabs as you’ve described is version 4.0.29.
Would this alone explain the discrepancy? Before proceeding further would you advise that I first upgrade to the latest and greatest version of this module?
Yes, the differences in the UI and feature options are from the newer modules after v4.0.21.
In general I suggest testing with the newest modules because of the new features and fixes in the code. With the addition of the Server Set you can configure your Server connections for concurrent connections or redundant (failover) connection in case your primary Server goes offline. You can also selectively filter messages based on Topics independantly.
Not sure why your connection fails. I should see the logs in the Diagnostic Bundle to offer more information. You can send these from our Contact us portal at Contact us - Cirrus Link
Thank you Dan for your reply. It turns out we will need to upgrade our Ignition platform to 8.3 to correct this (we’re on 8.1.36). We’re scheduling this for next Monday so I will get back to you next week with how this turns out. Thank you for pointing us in the right direction.
