Introduction to the Devices Module 
The Devices module facilitates seamless Devices Module (Concept) enables real-time communication and data exchange with
field equipment.
The Device Module provides direct protocol implementation for:
- Real-time Monitoring - Live process values from PLCs and sensors
- Control Commands - Write setpoints and triggers to devices
- Data Collection - Gather production metrics and equipment status
- System Integration - Connect diverse equipment brands and protocols
- Edge Computing - Process data locally before cloud transmission
On this page
:
Table of Contents maxLevel 2 minLevel 2 indent 10px exclude Steps
style none
Key Concepts
- *Channel*: Protocol instance with specific configuration settings (IP, port, timeout)
- *Node*: Physical device or external system connected through a channel
- *Point*: Individual data item (tag) mapped to a device address
- *AccessType*: Read/write permissions and scan rates for points
- *Protocol*: Communication driver for specific device types or standards
What It Does
- Communicates with PLCs, RTUs, and field devices using native protocols
- Manages real-time data exchange without external OPC servers
- Provides automatic tag synchronization with device addresses
- Handles multiple simultaneous protocol connections
- Monitors communication health and diagnostics
- Supports both polling and event-driven communication
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.:
Configuration Workflow
Device Module Configuration Workflow | ||
|---|---|---|
Step | Action | |
Description | |
|---|---|
Create Channels | Select |
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.
protocol from library | Configure connection parameters (IP, port, timeout) | |
Create Nodes | Add devices to channels | Set device addresses and station IDs |
Map Points | Link tags to device addresses | Use import tools for bulk configuration |
Set AccessTypes | Define data flow | Configure read/write permissions and scan rates |
Runtime Behavior
Communication Processing
The module maintains background connections to all configured devices. Write-enabled points subscribe to tag changes and update devices automatically. Read points update based on their configured scan rates.
Diagnostics and Monitoring
- *PropertyWatch*: Verify tag values are updating correctly
- *TraceWindow*: View raw protocol communication data
- *ModuleInformation*: Monitor connection status and statistics
Features Highlights
- Built-in MQTT Broker and OPC UA Server included
- MQTT Sparkplug B simulator for testing
- No middleware required - direct protocol implementation
- Supports edge, on-premise, and cloud deployments
- Driver Toolkit for custom protocol development
- Automatic failover and redundancy support
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|
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.