EasyManua.ls Logo

Prevac MG15 - Interface Configuration

Prevac MG15
122 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
COMMUNICATION MULTI GAUGE CONTROLLER
The data link layer includes the following properties/behaviours:
identiication of the Slave device address,
detection of beginning/end of a frame,
generation of CRC-16 checksum (Modbus RTU),
transmission/reception of ”time-out” messages,
detection of buffer thrashing,
detection of frame errors,
detection of line idleness.
6.4.2 INTERFACE CONFIGURATION
There are four communication interfaces - RS232, RS485, Ethernet and ProiNet (option).
For standard MG15 devices with a display, selection of interface, preview and change of its param-
eters is available in the menu, and their complete coniguration is described in subchapter 3.6.11.1.
In case of a device without a display ( BlackBox) communication over Modbus RTU protocol is exe-
cuted always with the same parameters (baudrate 57600bps, 8 data bits, 1 stop bit, no parity), and
the transmission channel (RS232, RS485, ProiNet(option)) is selected by means of jumpers on the
device rear panel. The description is in point 2 of subchapter 2.5.6.
Communication over Modbus TCP protocol is conigured using relevant commands of the Modbus
RTU protocol.
Communication in the ProiNet(option) network is available through the interface described in
chapter 6.5. Transmission is executed as encapsulation of the Modbus RTU protocol frame in the
ProiNet frame. This means that the MG15 is visible in the network as a standard device compatible
with the ProiNet standard and an IP address is assigned to it. Communication, however is executed
by formulating appropriate queries compatible with the Modbus RTU protocol and sending them
in a frame of the ProiNet protocol to the Slave device. In the sent frame user should to include the
address setted up on the jumpers of the device rear panel (according to the Modbus RTU proto-
col). This is a difference in relation to communication via the Ethernet interface, where the device
is unequivocally identiied only through an IP address.
It is recommended to make all the settings of the communication interface be-
fore connecting device to the Ethernet or EIAxxx network.
It is not necessary, however, the MG15 default settings may cause conlicts with
the devices already connected to the network.
In the Modbus RTU protocol there is only one parameter - device address. In
case of the Ethernet network there are several other parameters: IP address,
subnet mask, network, default gate address and DHCP.
Page 88 User manual rev. 03

Table of Contents