Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform
User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server
Page 116 of 172 ProSoft Technology, Inc.
September 20, 2018
Server Status Data
Total number of MNET command list requests
Total number of MNET command list responses
Total number of MNET command list errors sent
Total number of MNET command list errors received
Total number of MBAP command list requests
Total number of MBAP command list responses
Total number of MBAP command list errors sent
Total number of MBAP command list errors received
Status information transferred in the Server Status block can be viewed in the
MNETC.STATUS controller tag in the ladder logic. For more information, see
Status Data Definition (page 93).
Controller Tags
To issue a Server Status block request, enter the appropriate values in the
following members of the MNETC.STATUS controller tag in the ladder logic.
Set the value of this tag to 1 to trigger the Server
Status block request.
Event Command Blocks with Sequence Number (4000 to 4029, 4100 to 4129,
4200)
Event Command Block with Sequence Number (4000 to 4029)
Note: To use the Event Command Blocks with Sequence Number for polling operations, you must
configure at least one command in the Client even if the command is disabled.
During routine operation, the module continuously cycles through the user-
defined MNET Client x Commands (page 44) for each Client, examining
commands in the order they are listed, and sending enabled commands on the
network. However, the module also has a special command priority queue, which
is an internal buffer that holds commands from special function blocks until they
can be sent on the network.
When one or more commands appear in the command priority queue: