DeltaV Diagnostics

Use DeltaV Diagnostics as a starting point to diagnose nodes (controllers and workstations) and subsystems in your DeltaV System. You can view diagnostic information any time after configuring nodes and placing devices on the control network and downloading the workstation. You can access DeltaV Diagnostics locally from your workstation or remotely using a dial-in modem and standard, off-the-shelf, remote access software. Click StartDeltaV OperatorDiagnostics to launch the Diagnostics program.

With DeltaV Diagnostics, you can perform the following tasks:

DeltaV Diagnostics has the same look and feel as the DeltaV Explorer. The left pane shows the hierarchy of nodes and subsystems in the control network. Typically, workstations have communications, assigned modules, alarms and events, Continuous Historian, OPC, and remote network subsystems and controllers have communications, I/O, and assigned modules subsystems. Devices are below the I/O subsystem.

To explore the contents of a node or subsystem, click the plus sign next to it to expand the contents. To see diagnostic information for a node or subsystem, select the node or subsystem, and view the diagnostic information for the selection in the right pane. To change how the diagnostic information is presented, experiment with the different views: List, Details, Comparison, and Verbose. In this figure, diagnostic information for the Primary communications subsystem of the workstation node USAUST-DOVETAIL is displayed.

Four indicators are used to show the status of nodes and subsystems. These indicators appear at the top level in the hierarchy as well as at the specific node or subsystem:

Indicates the node is not communicating. Typically this indicator occurs when there is a bad connection or if the node is not powered up or is decommissioned.

Indicates that Diagnostics does not have all the information on the node. For example if an unconfigured I/O card is pulled, this indicator appears.

Indicates the node is communicating but has an integrity problem. Integrity problems can occur for a variety of conditions including hardware or connection problems, a mismatch between the I/O configuration and the installed I/O, or if the node is configured for redundancy but does not have the necessary connections to support redundancy.

Indicates the node has lost its configuration or the configuration is not downloaded. A node can lose its configuration if it loses power or is reset.

Refer to the online help for complete information about using DeltaV Diagnostics.