Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
 

Overview

This document provides an overview of using diagnostic tools with devices, focusing on three primary tools: page introduces three essential diagnostic tools Module Information, Property Watch, and Trace Window for device management.

The Module Information tool offers provides insights into the module operation of the modules, while Property Watch is used for accessing allows access to tags and internal properties for reading or writing. Lastly, the , and Trace Window tool displays vital system messages in a data grid interface, providing essential information about the status of various communication events.This document also highlights . Emphasizing the importance of negative error codes in diagnosing issues and , the document offers guidance on how to use leveraging these tools effectively for troubleshooting and device management and troubleshooting.The overview is a little redundant. Fix.


On this page:

Table of Contents
maxLevel3



Using Diagnostic Tools on Devices

After Once you start the project in the Startup window, select one of the diagnostic tools. These are: PropertyWatch

  • Property Watch (Watch)
, TraceWindow
  • .
  • Trace Window (Trace)
, and ModuleInformation
  • .
  • Module Information (Info). 

Image Added 

You can also start the diagnostic tools on the Runtime → Diagnostics and Runtime → Startup pages by left-clicking the desired tool's icon. If menus are enabled for the display, you can also access the tools menu. Image Removed 

Module Information

The Module Information tool provides information about the operation of the modules. If you choose Choose the devices module and a specific channel, you . You will see information regarding the function of the communication channel.   The "Read Groups Information" is important essential because it provides information about the virtual reading groups, the run time of each item, the quantity of the readings, and the readings that have failed. It also reports on the code and date/time of the last error. 

Image RemovedImage Added

These are the typical steps to use the Module Information tool:

  1. Go to Read Groups Information to look at the number of successful and failed communication events and
in order
  1. to
quickly
  1. identify the communication blocks quickly.
If
  1. Suppose you have systematic errors in all of the 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
right
  1. correct.
  2. 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.
  3. For some protocols, like OPC, the discarded items will show as
a
  1. the wrong
addresses
  1. address in the configuration.

Keep in mind that you can only READ from a field device when an Enterprise application is running in test mode. This makes it useful worthwhile to run the application with ONLINE CONFIGURATION enabled because you do not need to start and stop the driver when modifying the configuration. You can modify PLC addresses, AccessTypes, and most of the applicationapplications, and you can see the results in real-time on your running application. You can use the Startup window or the PropertyWatch tool to start and stop only one module , 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 name of the property in the Object column, and its value will be found in the Value column.Image Removed

For example, in the screen shown abovebelow, select Tag.Coils or  Device.Channel.modbus.Status . The and the value of these objects will be shown. To the right side, additional properties are displayed for the selected object. 

This content should be a section, and the list should be a table.

Info
titleDevices negative error code
For

Image Added


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

Image Added

For ControlLogix devices, it is very important to use this tool, as the system will present here the invalid addresses on the configuration. If you click the settings button in the configuration dialog, you can select which message types and modules to display. You can see the data in the data grid or save it to a file. It is also possible to configure a tag in ObjectName, and click the Add button to display a menu to select that object and include it in the monitoring.


Image Added

Info

When checking the devices CheckBox in the Settings, enable only the Error, Info, and Warning information. Do not enable the Debug information, or you will create too much data.

Error Codes

For the Module Information and Property Watch tools, there are negative error codes that represents specific messages that can help to find the root cause of the error.

In the

  • On Module Information, refer to the LastErrorCode column.
  • On Property Watch, refer to @Device.Channel.ChannelName.Status.

See below the list of negative error codes:

0

The following table lists all Error codes with their descriptions:

CodeDescription
0Success
-1BuildCommandException
-2 ParseCommandUnsolicitedException

-3

ParseReplyException
-4BuildReplyUnsolicitedException
-5ChannelException
-6NodeException
-100Base Send Error
-101 Base SendAndWait Error
-102TCP Create Error 1
-103TCP Create Error 2
-104TCP Create SocketError
-105TCP Connect Callback Error
-106TCP Receive Error
-107UDP Create Error
-108UDP Receive Error
-109Serial Create Error
-110Serial Receive Error
-111TCP NotConnected
-112Start message timeout
-113Receiving bytes timeout
-114End message timeout
-115Connect timeout
-200ProtocolError
-201InvalidProtocol
-202InvalidStation
-203 InvalidCommand
-204InvalidMsgSequence
-205 InvalidCheckSum
-206 InvalidAddress
-207
InvalidModifiers

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

Image Removed

When checking the devices CheckBox in the Settings, enable only the ERROR, INFO, and Warning information. Do not enable the Debug information, or you will create too much data. For ControlLogix devices, it is very important to use this tool, as the system will present here the invalid addresses on the configuration.

If you click the settings button in the configuration dialog, you can select which message types and modules to display. You can see the data in the data grid or save it to a file. It is also possible to configure a tag in ObjectName, and click the Add button to display a menu to select that object and include it in the monitoring.

Image Removed
InvalidModifiers



In this section:

Page Tree
root@parent
spacesV10