ProSoft MVI56E-MNETCR, Руководство пользователя

Страница: 97 / 161

MVI56E-MNETCR ♦ ControlLogix Platform Diagnostics and Troubleshooting
Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual
ProSoft Technology, Inc. Page 97 of 161
4.3 Reading Status Data from the Module
Module status information is useful for troubleshooting and can be accessed in
several different ways.
In the ladder logic's MNETCR.STATUS controller tag structure.
The MVI56E-MNETCR module returns status data in the input image that can be
used to determine the module’s operating status. This data is transferred from
the module to the ControlLogix processor continuously as part of the normal data
transfer block sequence (page 108). You can view this data in the
MNETCR.STATUS controller tag structure in the ladder logic.
Client status data can also be requested and returned in a special Client Status
block (page 113), outside of the normal data transfer block sequence. The status
data contained in the Client Status block is different from the status data in the
normal data transfer blocks. It can also be viewed in the
MNETCR.STATUS
controller tag structure.
For more information about status data in MNETCR.STATUS , see the Status
Data Definition (page 97).
In ProSoft Configuration Builder's Diagnostics screens.
For more information, see the section on PCB Diagnostics (page 93).
In database locations specified by Error/Status Pointers (optional).
If optional Error/Status Pointers are enabled, status data can also be found in the
Read Data area of the module’s database at the locations specified by the
pointer configuration parameters. For more information, see Backplane
Error/Status Pointer (page 44), Client Error/Status Pointer (page 46) and
Command Error Pointer (page 46).
4.3.1 Status Data Definition
This section contains a description of the controller tags in the
MNETCR.STATUS structure, which contains module and Client status data.

The first eight controller tags contain status data routinely transferred from
the module to the processor in the normal data transfer block sequence
(page 108).

The remaining controller tags are used to request and receive Client status
data via the Client Status block functionality (page 113).
Note: In order to access up-to-date status data from these remaining controller tags, you must
ensure that a Client Status block was recently received from the module. Client Status blocks are
not routinely sent from the module; they are returned on a once-per-request basis as a response to
a Client Status block request from the processor.