Reference MVI69E-MBTCP ♦ CompactLogix Platform
User Manual Modbus TCP/IP Enhanced Communication Module
Page 132 of 150 ProSoft Technology, Inc.
June 28, 2017
7.4.5 Get Queue and Event Sequence Block Counts Block (4200)
This block requests the command queue count and the number of pending event
sequence commands for all module clients.
Block 4200: Request from Processor to Module
Where n = 60, 120, or 240 depending on the Block Transfer Size parameter.
Block 4200: Response from Module to Processor
Client 0 command queue count (MSB Most Significant Byte) and event sequence
messages waiting (LSB Least Significant Bit)
Client 1 command queue count (MSB Most Significant Byte) and event sequence
messages waiting (LSB Least Significant Bit)
Client 2 command queue count (MSB Most Significant Byte) and event sequence
messages waiting (LSB Least Significant Bit)
Client 18 command queue count (MSB Most Significant Byte) and event sequence
messages waiting (LSB Least Significant Bit)
Client 19 command queue count (MSB Most Significant Byte) and event sequence
messages waiting (LSB Least Significant Bit)
7.4.6 Command Control Blocks (5001 to 5016)
Command Control blocks place commands into the module’s command priority
queue. Unlike Event Command blocks, which contain all the values needed for
one command, Command Control is used with commands already defined in the
MNET Client x Command List in ProSoft Configuration Builder.
Block 5001 to 5016: Request from Processor to Module
Command queue block identification code of 5001 to 5016
Client index (0 to 19) to be used
Command Index in the command list for the first command to be entered into the
command queue
Command indexes of the next commands to be placed in the command queue
To Next Page
Loading...
Need help?
General
