MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference
Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual
ProSoft Technology, Inc. Page 113 of 172
September 20, 2018
This word contains the next read request block identification code.
This word contains the result of the event request. If a value of one is
present, the command was issued. If a value of zero is present, no room was
found in the command priority queue.
This word contains the block identification code 2000 to 2029 requested by
the processor.
Word 2 of the block can be used by the ladder logic to determine if the command
was successfully added to the command priority queue. The command will fail if
the queue for the Client is already full at the time when the Event Command
block is received by the module.
Controller Tags
The elements of the MNETC.CONTROL.EventCmd.Cmd[x] controller tag array
contain all the values needed to build one Modbus TCP/IP command, have it
sent to a specific Client on the module, and control the processing of the returned
response block.
Enter the first octet of the IP address of the target Modbus server.
Enter the second octet of the IP address of the target Modbus server.
Enter the third octet of the IP address of the target Modbus server.
Enter the fourth octet of the IP address of the target Modbus server.
Enter 502 for a MBAP message or 2000 for a MNET message.
Enter the Modbus slave node address. Enter 1 to 247. Enter 0 if not
needed.
Enter the module internal database address to associate with the
command.
Enter the number of words or bits to be transferred by the Client.
Enter the swap code for the data. This function is only valid for
function codes 3 and 4.
Enter the Modbus function code for the command.
Enter the database address for the server.
When these values have been entered, set the bit in
MNETC.CONTROL.EventCmd.Trigger to one (1) to trigger the execution of the
Event Command.
To Next Page
Loading...
Need help?
General