Page History

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

Monitor Properties

Runtime Node Properties

Accessing Properties

In Scripts

csharp

// Check node status
int errorCode = @Device.Node.PLC1.LastErrorCode;
if (errorCode != 0)
{
    DateTime errorTime = @Device.Node.PLC1.LastErrorDateTime;
    @Info.Trace($"Node error {errorCode} at {errorTime}");
}

// Monitor activity
int activity = @Device.Node.PLC1.ActivityCounter;
bool isActive = activity > 0;

In Displays

xml

<!-- Show node status -->
<TextBlock Text="{Device.Node.PLC1.LastErrorCode}" />
<TextBlock Text="{Device.Node.PLC1.LastErrorDateTime}" />

<!-- Activity indicator -->
<Ellipse Fill="{Binding Device.Node.PLC1.ActivityCounter, 
    Converter=ActivityToColorConverter}" />

Error Codes

Success

• 0 - No errors, normal operation

Negative Codes (Connection Issues)

Network Errors (-100 to -115)

Protocol Errors (-200 to -208)

Positive Codes

Protocol-specific errors - consult driver documentation

Channel Status Monitoring

Access channel status for additional diagnostics:

csharp

// Channel status
int channelStatus = @Device.Channel.ChannelName.Status;

// Interpret status using error code table
string statusMessage = GetStatusMessage(channelStatus);

Invalid Addresses

Monitor and handle unresolved addresses:

csharp

// Get invalid addresses
string[] invalid = @Device.Node.PLC1.InvalidAddresses;

if (invalid.Length > 0)
{
    foreach(string address in invalid)
    {
        @Info.Trace($"Invalid address: {address}");
    }
}

Diagnostic Patterns

Connection Health Check

csharp

public bool IsNodeHealthy(string nodeName)
{
    var node = @Device.Node[nodeName];
    
    return node.LastErrorCode == 0 && 
           node.ActivityCounter > 0 &&
           !node.Disable;
}

Error Recovery

csharp

public void HandleNodeError(string nodeName)
{
    var node = @Device.Node[nodeName];
    int error = node.LastErrorCode;
    
    switch(error)
    {
        case -111: // Not connected
            RestartChannel();
            break;
        case -115: // Timeout
            IncreaseTimeout();
            break;
        default:
            LogError(error);
            break;
    }
}

Best Practices

1. Monitor Critical Nodes - Set up alarms for errors
2. Log Error Patterns - Track recurring issues
3. Handle Timeouts - Implement retry logic
4. Check Invalid Addresses - Validate during startup
5. Track Activity - Detect stalled communications
6. Document Error Codes - Map to troubleshooting steps
7. Set Up Notifications - Alert on critical failures

Troubleshooting Guide

No Activity

• Check channel enabled
• Verify network connectivity
• Review node configuration
• Check polling settings

Frequent Errors

• Analyze error patterns
• Check network stability
• Review timeout settings
• Verify device status

Invalid Addresses

• Check address format
• Verify device mapping
• Review import results
• Test individual points

Connection Timeouts

• Increase timeout values
• Check network latency
• Verify device response
• Review firewall settings

In this section...

Image Removed

Monitoring Device Nodes Status

You can access the monitor by navigating to Devices → Devices Monitor.

When the solution is running, the monitor will display a table of properties with real-time information about the Device Module Nodes.

Devices Monitor Table Columns

The information in this table is constructed from the runtime properties of the object: Device.Node.<NodeName>.  

Additionally of showing in the monitor table, the properties can be accessed on Displays or Scripts, using the following syntax

@Device.Node.<NodeName>.<PropertyName>

In this section: