ProSoft Technology MVI69E-MBTCP - Manual (Page 128)

Reference MVI69E-MBTCP ♦ CompactLogix Platform
User Manual Modbus TCP/IP Enhanced Communication Module
Page 128 of 150 ProSoft Technology, Inc.
May 20, 2015
7.4.1 Event Command Blocks (2000 to 2019)
Event Command blocks send Modbus commands directly from the ladder logic to
the specified MBTCP Client x. The Event Command is added to the high-priority
queue and interrupts normal polling so this special command can be sent as
soon as possible.
Note: Overusing Event Commands may substantially slow or totally disrupt normal polling. Use
Event Commands sparingly. Event Commands are meant to be used as one-shot commands
triggered by special circumstances or uncommon events.
Blocks 2000 to 2019: Request from Processor to Module
Offset Description
0 Block ID 2000 to 2019 indicates this block contains a command to execute by the
Client Driver. The last two digits indicate which client to use.
Example: ‘2015’ utilizes 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 to use with the message
6 Modbus node address to use with the message
7 Internal Modbus address in the module to use
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 associated with the command
12 to (n-1) Spare
Where n = 60, 120, or 240 depending on the Block Transfer Size parameter.
Blocks 2000 to 2019: Response from Module to Processor
Offset Description
0 Block ID 2000 to 2019 requested by the processor
1 The next read request block identification code
2 Result of the event request.
1=the command was placed in the command queue.
0= No room was found in the command queue.
-1=The client is not enabled and active.
3 Number of commands in queue
4 to (n-1) Spare