ProSoft Technology MVI69L-MBTCP - Manual (Page 127)

MVI69L-MBTCP ♦ CompactLogix Platform Reference
Communication Module User Manual
ProSoft Technology, Inc. Page 127 of 152
January 6, 2014
7.4.1 Event Command Blocks
Blocks 2000 to 2019: Event Command
Event Command blocks send Modbus commands directly from the ladder logic to
the specified MBTCP Client x. The Event Command will be added to the high-
priority queue and will interrupt normal polling so this special command can be
sent as soon as possible.
Note: Overuse of 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 utilize.
Example: ‘2008’ 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 to 239 Spare
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. If a value of ‘1’ is present, the command was placed in
the command queue. If a value of ‘0’ is present, no room was found in the command
queue. If a value of ‘-1’ is present, the client is not enabled and active.
3 Number of commands in queue
4 to 239 Spare