This object links to a Broker Connection to publish all data collected by Edge ACM in a plaint text MQTT format
General
Name
A unique identifier for this object
Enabled
The current Enabled status of this publisher; nothing will be published if it is not enabled
Folder
The parent folder of this object
MQTT
Node ID
The unique identifier used by this publisher when publishing data
Publish QoS
The Quality of Service for published messages
0 - At most once (least bandwidth, least reliable)
1 - At least once (middle bandwidth, middle reliability)
2 - Once and only once (most bandwidth, most reliable)
Subscribe QoS
The requested Quality of Survice for subscribed messages (typically tag value writes from remote clients)
0 - At most once (least bandwidth, least reliable)
1 - At least once (middle bandwidth, middle reliability)
2 - Once and only once (most bandwidth, most reliable)
Broker Connection
The Broker Connection object used by this Sparkplug B Publisher object
Advanced MQTT
Delay Between Publishes (ms)
The time in milliseconds between published messages
Info
Information on the installed version of this object
MQTT topic examples
For the following example, eACM is collecting data from a device named “Device1”, with the tag “Tag1”.
AUTOSOL MQTT’s Standard publisher has a NodeID of “LocalNode” (set on the MQTT tab).
What topics shoudl appear in the broker?
When AUTOSOL MQTT starts up, tag data will appear with the topic:
LocalNode/Device1/Tag1
It has a timestamp reflecting time of publication and the payload is the value of the tag.
When AUTOSOL MQTT stops, or when communication with the end device is lost, a death message will indicate that the node is offline with the topic:
LocalNode/DEATH