...
In either of these two setups, the MQTT connection for each virtual Edge Node requires a unique Client ID. The Client ID in the the MQTT Transmission Configuration should be left blank allowing MQTT Transmission to auto-generate unique Client IDs for each Edge Node connection.
Anchor |
---|
| CollidingEdgeNodeID |
---|
| CollidingEdgeNodeID |
---|
|
Colliding Edge Node ID
...
Anchor |
---|
| DesignerClientIDs |
---|
| DesignerClientIDs |
---|
|
Finding Client IDs using Ignition Designer
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.
Image Added
Anchor |
---|
| ResolvingCollidingEdgeNodes |
---|
| ResolvingCollidingEdgeNodes |
---|
|
Resolving Colliding
Edge NodesTo 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.
Tip |
---|
Refer to the MQTT Configuration guide and the MQTT Transmission Transmitters and Tag Trees Tutorial/HowTo for configuration help. |
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 |
---|
| UnabletoResolve |
---|
| UnabletoResolve |
---|
|
Unable to Resolve?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.
For 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.