Page History

Devices → Tutorial | Concept | How-to Guide | Reference

Creating Nodes

1. Navigate to Devices → Nodes

Configuring Device Nodes

To create a new node, follow these steps:

1. Access Devices → Nodes.
Click the
2. Click
3. Plus icon to add
a new
4. node
.
6. Configure:
   • Channel - Select
a channel to associate the node, and fill in its name and description.
7. Click Ok.

Image Removed

After completing the above steps, the Node is created. 

You can configure and existing node by double-clicking the property you want to edit on the corresponding row.

DeviceNode Table Columns

The following table describes each available property you can configure when editing a Node:

Column

Description

Name

Name of the Node.

Channel

The Device Channel for this Node. For more information about the configuration for common protocols, click Help at the top of the tab.

PrimaryStation

BackupStation

The required information to access the backup Node. When the backup station is defined, and a communication failure occurs on the primary station, the system automatically attempts to establish communication with the backup station.

SyncDate

The date that the import was done. 

SyncStation

Information about the station where the import was done Station IP, Port and Slot.

SyncSettings

Information about the settings used by the system to import the file. 

Description

Description for this Node.

Importing Nodes from PLC Addresses

Additionally, you can simplify the creation of communication Nodes with various methods for automatic data configuration import.

→ Read more about Importing PLC Addresses.

1. • parent channel
   • Name - Unique node identifier
   • Description - Documentation
2. Click OK

Node Properties

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

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

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

Best Practices Checklist

•  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

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...

In this section: