eACM translates native RTU and PLC protocols into the highly efficient MQTT protocol utilizing AUTOSOL Edge ACM is a suite of applications installed on a field device that work in conjunction to poll real-time data and publish it using standardized Sparkplug B message formatting. Report. These applications are managed by the AUTOSOL App Manager.
eACM/Edge ACM: The polling engine that collects data from the field device using native protocols.
Enables report-by-exception data
...
to be sent to any MQTT broker
...
Provides backfill for data retention during communication outages.
...
Edge ACM Core Components:
AUTOSOL App Manager: Overall Application Interface
- Edge ACM: Polling Engine – collects data from End Device using native/field protocol(s)
AUTOSOL MQTT: Publisher – supports SparkplugB, publishes The publisher that publishes the polled data to a broker and receives can receive “writes” from Broker a broker intended for the connected end device.
Azure: Native The native MS Azure Connector for used when communicating with Azure enabled services.
File Handler: Enables Publishing of Publishes files via MQTT in Base64 format.
Priority Forward: Enables multiple connections to a single serial device port; directs traffic per user defined rules to avoid communication interruptions
OPC UA
asiBridge
AUTOSOL App Manager and Edge Manager
The AUTOSOL App Manager and Edge Manager are built-in, easy-to-use web pages used for configuration. The Edge Manager exists on the field devices and allows configuration of only that device. The AUTOSOL App Manager exists on a centralized Windows computer and allows configuration of multiple AUTOSOL Edge Nodes with lower bandwidth requirements than directly accessing their configuration websites.
Native Polling Protocols
eACM currently supports Modbus, Totalflow, ROC , FloBoss, Allen Bradleyand ControlLogix.
Example eACM Deployment
...
...
Technical References
MQTT Basics: https://www.hivemq.com/mqtt-essentials/
Sparkplug B Specification: https://github.com/eclipse/tahu