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
The two likely causes of large messages are:
As required by the Sparkplug Specification data is published on the are the NBIRTH, NDEATH, DBIRTH and DDEATH topics.
The payloads for each of these messages include every metric the device will ever report on. At a minimum these metrics must include the name, datatype and current value.
If you have large number of tags in a single folder, these messages can easily exceed the 128KB limit.
Tag pacing is the buffer period for outgoing Transmission messages which allows tag change events to be buffered to reduce the number of generated MQTT messages. If you set this pacing too slow, with a large volume of tag changes, messages can easily exceed the 128KB limit.
To find the largest published message size, navigate to the MQTT Transmission in the Ignition Designer Tag Browser. Drill down to your Transmitter and you should see the ‘Largest Mesg Xmit’ tag as shown below.
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 Transmission 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 | ||||||
---|---|---|---|---|---|---|
|