ProSoft MVI56E-MNETCR User Manual page 114

Reference
User Manual
Word Offset
5
6
7
8
9
10
11
Status information transferred in the Client Status block can be viewed in the
MNETCR.STATUS controller tag in the ladder logic. For more information, see
the Status Data Definition (page 97).
Controller Tags
To issue a Client Status block request, enter the appropriate values in the
following members of the MNETCR.STATUS controller tag in the ladder logic.
Controller Tag
ClientIDReq
ClientStatsTrigger
Command Control Blocks (5001 to 5016)
Note: Command Control is not needed for normal Modbus command list polling operations and is
needed only occasionally for special circumstances.
During routine operation, the module continuously cycles through the user-
defined MNET Client x Command List (page 49) for each Client, examining
commands in the order they are listed, and sending enabled commands on the
network. However, the module also has a special command priority queue, which
is an internal buffer that holds commands from special function blocks until they
can be sent on the network.
When one or more commands appear in the command priority queue:
1 The routine polling process is temporarily interrupted.
2 The commands in the command priority queue are executed until the queue
is empty.
3 Then the module goes back to where it left off on the MNET Client x
Command List and continues routine polling.
Page 114 of 161
Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis
Client Status
Not used
Not used
Not used
Not used
Configuration Error Word
Current Error
Last Error
Data Type Description
Enter the Client (0-29) to request status data for.
INT
Set the value of this tag to 1 to trigger the Client
BOOL
Status block request.
MVI56E-MNETCR ♦ ControlLogix Platform
ProSoft Technology, Inc.