Devices Nodes (Reference) represent physical devices or PLCs in the communication network, with each node containing one or more communication points mapped to device addresses.
Device Nodes provide:
- Device representation in channels
- Primary/backup station configuration
- Point organization
- Import capabilities
- Synchronization tracking
- Communication routing
Each node maps to a specific device (PLC, RTU, controller) accessible through its parent channel.
On this page:
Creating Nodes
- Navigate to Devices → Nodes
- Click Plus icon to add node
- Configure:
- Channel - Select parent channel
- Name - Unique node identifier
- Description - Documentation
- Click OK
Node Properties
Property | Description | Example |
---|---|---|
Name | Node identifier | PLC_Line1 |
Channel | Parent communication channel | ModbusTCP_Channel |
PrimaryStation | Main device address | 192.168.1.10:502 |
BackupStation | Redundant device address | 192.168.1.11:502 |
SyncDate | Last import timestamp | 2024-03-15 14:30:00 |
SyncStation | Import source details | IP:Port:Slot |
SyncSettings | Import configuration used | Auto-detect, L5K file |
Description | Node documentation | Line 1 Main PLC |
Station Configuration
Primary Station
Protocol-specific addressing:
- Modbus TCP: IP:Port (192.168.1.10:502)
- OPC UA: opc.tcp://server:4840
- Serial: COM1;19200;8;N;1
- ControlLogix: 192.168.1.20;1;0
Backup Station
Automatic failover configuration:
- Same format as primary
- Activated on primary failure
- Automatic switchback option
- Independent timeout settings
Importing Nodes
Automatic Import Methods
Source | Description | Supported Protocols |
---|---|---|
PLC Programs | Import from PLC files | ControlLogix, Siemens |
OPC Browse | Discover OPC servers | OPC DA/UA |
Online Discovery | Scan network devices | Modbus, BACnet |
CSV Import | Bulk configuration | All protocols |
Import Process
- Select channel and protocol
- Choose import method
- Configure connection settings
- Browse/select items
- Map to local tags
See → Importing PLC Addresses for detailed instructions
Node Organization
Hierarchical Structure
Channel
??? Node (Device)
??? Point 1
??? Point 2
??? Point Group
??? Point 3
??? Point 4
Naming Conventions
- Use descriptive names
- Include location/function
- Maintain consistency
- Avoid special characters
Runtime Behavior
Connection Management
- Nodes inherit channel settings
- Independent connection per node
- Automatic reconnection
- Failover to backup station
Communication Flow
- Channel establishes connection
- Node routes to device address
- Points read/write through node
- Backup activates on failure
Best Practices
- Group Related Devices - One node per PLC/device
- Configure Backup Stations - For critical devices
- Document Thoroughly - Use description fields
- Test Import Results - Verify addressing
- Use Consistent Naming - Establish standards
- Monitor Sync Status - Track configuration changes
- Plan IP Addressing - Organize network topology
Common Configurations
Modbus TCP Node
Channel: ModbusTCP_Main
Name: PLC_Tank_Farm
PrimaryStation: 192.168.1.100:502
BackupStation: 192.168.1.101:502
Description: Tank farm controller
ControlLogix Node
Channel: EthernetIP_Channel
Name: CLX_Line1
PrimaryStation: 192.168.1.50;1;0
SyncSettings: L5K Import
Description: Line 1 ControlLogix
OPC UA Node
Channel: OPCUA_Channel
Name: OPC_Server1
PrimaryStation: opc.tcp://server:4840
SyncDate: 2024-03-15
Description: Main OPC UA Server
Synchronization
Import Tracking
Monitor configuration imports:
- SyncDate - When imported
- SyncStation - Source details
- SyncSettings - Method used
Refresh Options
- Manual re-import
- Scheduled sync
- Change detection
- Version control
Troubleshooting
Node offline:
- Check channel status
- Verify primary station address
- Test network connectivity
- Review backup station
Import failures:
- Verify device accessibility
- Check authentication
- Review protocol version
- Test with simple import
Communication errors:
- Confirm addressing format
- Check firewall rules
- Verify protocol settings
- Test backup failover
Points not updating:
- Check node status
- Verify point configuration
- Review scan groups
- Monitor diagnostics
Diagnostics
Monitor node health:
csharp
// Node status
bool isOnline = @Device.Node.NodeName.IsOnline;
// Station active
string activeStation = @Device.Node.NodeName.ActiveStation;
// Communication stats
int successCount = @Device.Node.NodeName.SuccessCount;
int errorCount = @Device.Node.NodeName.ErrorCount;
// Last sync
DateTime syncTime = @Device.Node.NodeName.LastSync;
In this section...
The root page @parent could not be found in space 93Draft.