ProSoft Technology MVI69L-MBTCP - Manual (Page 129)

MVI69L-MBTCP ♦ CompactLogix Platform Reference
Communication Module User Manual
ProSoft Technology, Inc. Page 129 of 152
January 6, 2014
7.4.3 Event Sequence Request Blocks
Block 4000 to 4019: Event Sequence Request
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 PCB.
Block 4000 to 4019: Request from Processor to Module
Offset Description
0 Block ID 4000 to 4019 indicates this block will trigger the event sequence of
MVI69L-MBTCP client. The last two digits indicate which Client to utilize.
Example: ‘4008’ will utilize Client 8
1 to 4 IP address for the server the message is intended. Each digit (0 to 255) of the IP
address is placed in one of the four registers
5 TCP service port the message will be use
6 Modbus node address to use with the message
7 Internal Modbus address in the module to be used
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 to be associated with the command
12 Sequence Number
13 to 239 Spare
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 239 Spare