MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference
Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual
ProSoft Technology, Inc. Page 119 of 172
September 20, 2018
Event Sequence Command Error Report (4100 to 4129)
This block displays the result of each command sent to the Client. The request
includes the Client identification and the command sequence number. The
response is the event count and error code for each event. A value of 0 in the
error code means there was no error detected.
Block Request from Processor to Module
4100 to 4129 (last digits indicate which Client to utilize)
Block Response from Module to Processor
Number of Event Sequence Commands executed by the
specified Client for which status has not yet been retrieved
Sequence number and error code for each Event Sequence
Command (up to the 15 most recent commands)
Read Block ID: 4100 to 4129
Notes:
The module stores command status data in a queue for the last 15 event
sequence commands it has sent out on the Modbus TCP/IP network. The
Event Command Sequence Number identifies the status data for an Event
Sequence Command.
When you retrieve event status data for a Client using Block 4100 to 4129,
the Client's event status data queue is deleted. If more than 15 commands
have been issued since the last retrieval, the early commands are deleted
and only the last 15 are saved in the queue.
Controller Tags
To retrieve status data for one client at a time, enter the appropriate values in the
following members of the MNETC.STATUS.EventSeqCmd controller tag in the
ladder logic.
Enter the Client (0-29) to request status data for.
Set the value of this tag to 1 to trigger the Event
Sequence Command block request.
To Next Page
Loading...
Need help?
General