Reference
User Manual
2
When configured, the Client driver begins transmitting read and/or write
commands to servers on the network. The data for write commands is
obtained from the module's internal database.
3
Assuming successful processing by the server specified in the command, a
response message is received into the Client driver for processing.
4
Data received from the server is passed into the module's internal database,
if the command was a read command. General module status information is
routinely returned to the processor in the input images.
5
Status data for a specific Client can be requested by the processor and
returned in a special Client Status block.
6
Special functions, such as Event Commands and Command Control options,
can be generated by the processor and sent to the Client driver for action.
5.3.2 Client Command List
In order for the Client to function, the module's Client Command List must be
defined in the MNET Client x Commands section of the configuration. This list
contains up to 16 individual entries, with each entry containing the information
required to construct a valid command. This includes the following:
Command enable mode: (0) disabled or (1) continuous
IP address and service port to connect to on the remote server
Slave Node Address
Command Type - Read or Write up to 100 words per command
Database Source and Destination Register Address - Determines where data
will be placed and/or obtained
Count - Select the number of words to be transferred - 1 to 100
Poll Delay - 1/10
For information on troubleshooting commands, see Client Command Errors
(page 99).
Page 122 of 161
Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis
th
seconds
MVI56E-MNETCR ♦ ControlLogix Platform
ProSoft Technology, Inc.
Need help?
Do you have a question about the MVI56E-MNETCR and is the answer not in the manual?
Questions and answers