MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting
Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual
ProSoft Technology, Inc. Page 95 of 172
September 20, 2018
Set the value of this tag to 1 to trigger the Event
Sequence Command block request.
Specifies Client (0 to 29) to request status data from.
EventSeqCmd.Client[x].Cou
nt
Number of Event Sequence Commands executed by
the specified Client for which status has not yet been
retrieved
EventSeqCmd.Client[x].Cmd
[x].Sequence
Sequence number for each Event Sequence
command
EventSeqCmd.Client[x].Cmd
[x].Error
Error code for each Event Sequence command:
0=success, 1=failure
One bit for each Client, indicating which Clients have
Event Sequence commands with unretrieved status
data: 0=no status data available, 1=status data
available for retrieval
Set to 1 to trigger the Server Status block request.
ServerStatus.MNET.Reques
ts
This counter increments each time an MNet (port
2000) request is received.
ServerStatus.MNET.Respon
ses
This counter increments each time an MNet (port
2000) response message is sent.
ServerStatus.MNET.ErrSent
This counter increments each time an MNet (port
2000) sends an exception response to Client.
Example: Client sent illegal Modbus Data location
address.
This counter increments each time an MNet (port
2000) receives a bad command. Example: Client sent
illegal function command.
ServerStatus.MBAP.Reques
ts
This counter increments each time an MBAP (port
502) request is received.
ServerStatus.MBAP.Respon
ses
This counter increments each time an MBAP (port
502) response message is sent.
ServerStatus.MBAP.ErrSent
This counter increments each time an MBAP (port
502) sends an exception response to Client. Example:
Client sent illegal Modbus Data location address.
This counter increments each time an MBAP (port
502) receives a bad command. Example: Client sent
illegal function command.