7.2.2 MODBUS-TCP with Ethernet connection
MODBUS data are available through a MODBUS TCP protocol, which is constantly
active over the network.
IMPORTANT - Rules for the use of Ethernet ports:
It is recommended to use preferably the port B. This port can handle the
communication with the software OneProd (XPR, CAST, MSC, VIO) and PLC
via Modbus TCP.
If the Modbus devices are on a different network then connect them on port A
Conventions:
Data in MODBUS-TCP format are available through the standard 502 port.
The MODBUS slave address must be set to 255 in requests (in this case, the
IP address is used to select each MVX).
CAUTION
The slave address had to be fixed at 1 (instead of 255) in the previous versions of
MVX.
This change can result in malfunction after upgrading MVX firmware to V5.0
Adress #255 allows for a better compatibility vs MODBUS-TCP standard..
7.3 Data format
The MODBUS interface is used to read values, statuses, units and thresholds of
indicators computed by MVX.
7.3.1 Available indicators
Using software programs XPR or CSM, one can program up to 255 different
indicators in MVX.
Each indicator is assigned a number (ranging from 1 to 255), which is part of the
indicator’s parameters and is entered upon programming.
For more details, refer to the user manuals of XPR or CSM.
It is to be noted that MVX channels do not correspond to the indicator numbers. As
an example, a single channel can result in the computation of about 10 different
indicators, whereas another channel, which remains unused, will not issue any
indicator and will therefore no longer exist in the MODBUS dialogue.
To Next Page
Loading...
