This object links to a Broker Connection to publish all data collected by Edge ACM in a plaint text MQTT format
...
General
...
...
Property |
|---|
...
Description |
|---|
Name |
...
The name of this item |
Enabled |
...
When enabled, data will be published |
...
. | |
Folder | The parent folder of this object |
MQTT
...
Property | Description | ||
|---|---|---|---|
Broker Connections | The Broker Connection objects used by this Sparkplug B Publisher object.
| ||
Assigned Schedules | The Publish Schedules that are associated with this publisher. AUTOSOL MQTT will only publish tags that match the publish group id’s assigned to these schedule objects. | ||
Node ID | The unique identifier used by this publisher when publishing data | ||
Publish QoS | The Quality of Service for published messages
| ||
Subscribe QoS | The requested Quality of |
...
Service for subscribed messages (typically tag value writes from remote clients)
|
Broker Connection
The Broker Connection object used by this Sparkplug B Publisher object
Advanced MQTT
...
Default Publish Rate | The time between data update messages
|
Advanced MQTT
...
Property | Description |
|---|---|
Delay Between Publishes |
...
The time |
...
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:
| Code Block |
|---|
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:
...