Introduction

The Control Expert DTM provides diagnostics information that is collected at configured polling intervals. Use this information to diagnose the operation of the embedded Ethernet scanner service in the CPU.

Connect the DTM

Before you can open the diagnostics page, make the connection between the DTM for the CPU’s embedded scanner service:

Step

Action

1

Open a Control Expert project.

2

Open the Control Expert DTM Browser (Tools > DTM Browser).

3

Right-click the name that is assigned to your CPU in the DTM Browser.

4

Select Connect.

Open the Page

Access the Diagnosis information:

Step

Action

1

Right-click the name that is assigned to your CPU in the DTM Browser.

2

Select Device Menu > Diagnosis to view the available diagnostics pages.

Diagnostics Information

The diagnostics window has two distinct areas:

  • left pane: LED icons indicate the operating status of modules, devices, and connections.

  • right pane: These pages show diagnostics data for these items:

    • CPU’s embedded scanner service

    • local slave nodes that are activated for the CPU’s embedded scanner service

    • EtherNet/IP connections between the CPU’s embedded scanner service and a remote EtherNet/IP device

When the appropriate DTM is connected to the CPU, Control Expert sends an explicit message request once per second to detect the state of the CPU’s embedded scanner service and of all the remote devices and EtherNet/IP connections linked to the CPU.

Control Expert places one of these status icons over the module, device, or connection in the left pane of the Diagnostic window to indicate its current status:

Icon

Communication module

Connection to a remote device

Run state is indicated.

The health bit for every EtherNet/IP connection and Modbus TCP request (to a remote device, sub-device, or module) is set to active (1).

One of these states is indicated:

  • unknown

  • stopped

  • not connected

The health bit for at least one EtherNet/IP connection or Modbus TCP request (to a remote device, sub-device, or module) is set to inactive (0).