VEGAMET 624/625

Problem Solution Overview

We performed testing between the subject device and the following ProSoft Technology products:

• MVI46-MNET
• MVI56-MNET
• MVI71-MNET
• MNET driver for ProLinx Communication Gateways products
• RadioLinx RLX-FHE (Frequency Hopping Ethernet Switch) and RLX-IH (802.11b Industrial Hotspot)

VEGAMET 624/625 provides Vega level sensors connectivity to interface with a Modbus/TCP master or controller.

Solution Brief

Our testing generated the following results:

• We were easily able to successfully communicate with all devices. (see below for configuration parameters used during the testing)
• The product documentation stated supported for Modbus functions 1, 2, 3 & 4. All function codes ran as expected and were easily implemented.

The purpose of our testing is to assure a level of compatibility in the communications between the two products. Through this testing, we attempt to identify problem areas that may arise when implementing the interface in the field.

Configuration and Diagnostics

The configuration of the VEGAMET Ethernet Interface is accomplished by accessing the built-in keypad/display. Other tools such as basic diagnostic information, indicating network statistics, are also available through the embedded display.

Integration and Operation

The VEGAMET is din-rail mountable, allowing an easy upgrade path.

Modbus/TCP specifications

VEGAMET operates as Modbus-TCP server and holds the existing PC/DCS values and relay switching conditions in temporary storage, read for pickup via Modbus-TCP.

Apart from the PC/DCS values, the switching conditions of the relay outputs of VEGAMET can be enquired.
The enquiry of the PC/DCS values and relay values is made via the appropriate function code (see also Modbus specification).

• Function code 04: Read Input Registers (enquiry of the PC/DCS values)
• Function code 01: Read Coil Status (enquiry of the relay values)
• Function code 02: Read Input Status (enquiry of the relay values)