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
Configuration Workflow
Device Module Configuration Workflow | ||
---|---|---|
Step | Action | Description |
Create Channels | Select 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