ProSoft Technology MVI69E-MBTCP - Manual (Page 130)

Reference MVI69E-MBTCP ♦ CompactLogix Platform
User Manual Modbus TCP/IP Enhanced Communication Module
Page 130 of 150 ProSoft Technology, Inc.
May 20, 2015
7.4.3 Event Sequence Request Blocks (4000 to 4019)
These blocks send Modbus TCP/IP commands directly from controller tags by
ladder logic to the Client Command Priority queue on the module. Event
Commands are not placed in the module's internal database and are not part of
the MNET Client x Command List in ProSoft Configuration Builder.
Block 4000 to 4019: Request from Processor to Module
Offset Description
0 Block ID 4000 to 4019 indicates this block triggers the event sequence of the
MVI69E-MBTCP client. The last two digits indicate which client to use.
Example: 4015 uses client 15
1 to 4 IP address for the intended server for the message. Each digit (0 to 255) of the IP
address is placed in one of the four registers
5 TCP service port for message
6 Modbus node address for the message
7 Internal Modbus address in the module
8 Count parameter that determines the number of digital points or registers to
associate with the command
9 Swap type for integer data only
10 Modbus function code
11 Modbus address in the slave device for the command
12 Sequence number
13 to (n-1) Spare
Where n = 60, 120, or 240 depending on the Block Transfer Size parameter.
Block 4000 to 4019: Response from Module to Processor
Offset Description
0 Block ID 4000 to 4019 requested by the processor
1 Write Block ID
2 0=Fail
1=Success
-1=Client is not enabled and active
3 Number of commands in queue
4 to (n-1) Spare