Overview
When the solution is running, and the Designer is connected with the runtime, the Devices Monitor page will show the basic status of its communication NodesThe Devices Monitor functions as a real-time diagnostics center for device communication within the software platform. It displays module health information, current tag and property values, and helps detect communication issues. Users employ the monitor to analyze the performance of connected devices, troubleshoot potential problems, and proactively optimize the interaction between the solution and field equipment.
On this page:
Table of Contents maxLevel 3 style none
Overview
This page introduces three essential diagnostic tools for device monitoring:
- Module Information: Provides insights into module operation.
- Property Watch: Allows access to Tags and internal properties.
- Trace Window: Displays vital system messages.
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
| Code Block |
|---|
@Device.Node.<NodeName>.<PropertyName> |
Devices Nodes Monitor Table | |
|---|---|
Property | Description |
ActivityCounter | Counter up on any activity on the node. |
Disable | Status of the node Disable Property |
LastErrorCode | 0 means no errors. Code for Last Error. Negative numbers means no connective, positive numbers are protocol specific errors. |
LastErrorDateTime | Timestamp of the error on previous column |
InvalidAddresses | In the case the node and addresses not resolved by the Device, they are available in the property. |
| Info | ||
|---|---|---|
| ||
For Module Information and Property Watch, there are negative error codes that represents specific |
Runtime Diagnostic
The Runtime Diagnostic provides additional from the Module Information, Property Watch, and the Trace Window.
To access the Diagnostic tolls, access Runtime → Runtime Diagnostics.
You can also access the mentioned feature after you start the solution. In this case, select the desired diagnostic feature in the Startup window.
| Info |
|---|
You can also start the diagnostic tools on the Runtime → Diagnostics and Runtime → Startup pages by left-clicking the desired tool's icon. You can also access the tools menu if menus are enabled for the display. |
Module Information
The Module Information tool provides details about the operation of the modules. By selecting the devices module and a specific channel, you can access information regarding the function of the communication channel. The "Read Groups Information" section is essential as it provides data about the virtual reading groups, including the runtime of each item, the quantity of readings, and any failed readings. It also reports the code and date/time of the last error.
To use the Module Information Tool:
- Go to Read Groups Information to look at the number of successful and failed communication events and quickly identify the communication blocks.
- Suppose you have systematic errors in all blocks or status codes with negative values. In that case, it typically means you cannot access the remote device. Check if the node address is correct.
- If you have specific blocks with systematic errors, verify the Tags and addresses that are connected to the blocks. Use the TraceWindow with the Device information to collect information about the communication errors.
- For some protocols, like OPC, the discarded items will show as the wrong address in the configuration.
Remember that you can only READ from a field device when an enterprise application is running in test mode. Running the application with ONLINE CONFIGURATION enabled is beneficial because it allows you to modify the configuration without starting and stopping the driver. You can change PLC addresses, AccessTypes, and most application settings and see the results in real-time on your running application.
To manage modules efficiently, you can use the Startup window or the PropertyWatch tool to start and stop individual modules instead of restarting the entire runtime system.
Property Watch
Property Watch is a diagnostic tool used to access the Tags and internal properties of the system for reading or writing. Type the property's name in the Object column, and you will find its value in the Value column.
For example, the value becomes available in the screen shown below after selecting Device.Channel. Other properties are also displayed for the selected object on the right side.
Trace Window
The Trace Window tool displays system messages in a data grid interface. If you enable the module devices in the settings, information will be available about the status of reads, writes, unsolicited input, TX frames (sent), and RX frames (received).
For ControlLogix devices, using this tool is essential as it highlights invalid addresses in the configuration. You can view the data directly in the data grid or save it to a file for further analysis. Additionally, you can configure a Tag in the Object Name field and click the Add button to display a menu, select that object, and include it in the monitoring.
If you click the Settings button in the configuration dialog, you can select which message types and modules to display.
| Info |
|---|
When checking the Devices Checkbox in the Settings, enable only the Error, Info, and Warning information. Do not enable the Debug information, as it will result in creating too much data. |
Error Codes
For the Module Information and Property Watch tools, there are negative error codes that represent specificmessages that can help to find the root cause of the error. |
In the Module Information, refer to the |
LastErrorCode column. |
On Property Watch, refer to @Device.Channel.ChannelName.Status. |
The following table lists all Error codes with their descriptions:
See below the list of negative error codes:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|