Introduction to the Devices Module 
The Devices module facilitates seamless real-time communication and data exchange with various field devices and industrial protocols, including standard interfaces like OPC-UA, MQTT, Modbus, and vendor protocols like Rockwell and CODESYS, and 100+ connectors.
On this Page:
Key Concepts and Terms
The Devices module facilitates seamless communication and data exchange with various field devices and industrial protocols, simplifying system architecture and enhancing connectivity. The configuration of the Devices module is performed in the following sections:
- Protocols: list the various connectors available to the Device Module
- Device Channel: Add a protocol to use by Device Module, definition configuration settings as needed.
- Device Node: a physical device, or external system, the Device Module will communicate using the Channel configuration for the protocol
- Device Point: individual items that are read from or written tp address in the Nodes, bound to a specific tag.
- Device AccessType: to each Point, the AccessType define it that address is read only, write only, or read-write.:
To Do: Add diagram
Configuration Workflow
Device Module Configuration Workflow | |
|---|---|
Action | Comments |
Create Channels | Select the Protocol from the list that supports your devices and use the Create Channel Button. |
Create Nodes | The Nodes are the various Devices using the protocols defined at the Channel. Their main configuration settings is the PrimaryStation that identifies the Network address. Learn more at Devices Nodes. |
Map Tags to Point addresses | Map Tags Addresses on each Device Nodes. (Import tools are available for large systems) |
Select or customize AccessTypes | Optionally, you can modify the read/write permission, and scan time using AccessTypes. |
Runtime Execution
When the Module Device is execution, it will start a process to keep a background communication with devices defined. All Device Points that are to be written to the devices, the device module will subscribe to be notified when that tag has a new value, to write it on the device.
In order to understand what is happing with the communication, there are various diagnostics tools to assist in monitoring if he communication is working as expected, even that tag is not being used in any displays yet.
The PropertyWatch allows ot inspect if the values in the UNS are arriving as expected.
The TraceWindow and ModuleInformation tool allows to all the network layer data with the device, for advanced diagnostics.
Features Highlights
Simplifies architecture by removing the need for additional communication products.
Supports on-premise, edge, enterprise-level, and cloud communication.
Includes a built-in MQTT Broker and OPC Server.
Provides MQTT SparkPlug B and OPC-UA simulators for demos and prototyping.
Features a Driver Toolkit for adding new interfaces.