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

  1. Navigate to Devices → Nodes
  2. Click Plus icon to add node
  3. Configure:
    • Channel - Select parent channel
    • Name - Unique node identifier
    • Description - Documentation
  4. Click OK

Node Properties

PropertyDescriptionExample
NameNode identifierPLC_Line1
ChannelParent communication channelModbusTCP_Channel
PrimaryStationMain device address192.168.1.10:502
BackupStationRedundant device address192.168.1.11:502
SyncDateLast import timestamp2024-03-15 14:30:00
SyncStationImport source detailsIP:Port:Slot
SyncSettingsImport configuration usedAuto-detect, L5K file
DescriptionNode documentationLine 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

SourceDescriptionSupported Protocols
PLC ProgramsImport from PLC filesControlLogix, Siemens
OPC BrowseDiscover OPC serversOPC DA/UA
Online DiscoveryScan network devicesModbus, BACnet
CSV ImportBulk configurationAll protocols

Import Process

  1. Select channel and protocol
  2. Choose import method
  3. Configure connection settings
  4. Browse/select items
  5. 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

  1. Channel establishes connection
  2. Node routes to device address
  3. Points read/write through node
  4. Backup activates on failure

Best Practices

  1. Group Related Devices - One node per PLC/device
  2. Configure Backup Stations - For critical devices
  3. Document Thoroughly - Use description fields
  4. Test Import Results - Verify addressing
  5. Use Consistent Naming - Establish standards
  6. Monitor Sync Status - Track configuration changes
  7. 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...