|
|
RE:mvi156-MNET
The on-line manual for the Bently Nevada 3500/92 comm module says it is capable of Modbus communication via serial port or Modbus TCP communication via Ethernet. It does not specify what Service port to use for Modbus TCP.
The ProSoft MVI56-MNET Client is capable of creating Modbus TCP commands to access data from either Service 502 (standard Modbus TCP) or Service Port 2000 (Encapsulated Modbus Serial RTU over Ethernet.) You will need to contact Bently Nevada Tech Support to find out which service port to use for their equipment; but it will probably be 502 for straight Modbus TCP.
As for the ABB DCS, I assume you mean that it also talks Modbus TCP, since you have it connected through the Ethernet hub. As a Modbus TCP Server to the ABB DCS Client, the MVI56-MNET will respond to commands sent to the module's IP address using Service Port 502, not 500. To read or write internal module memory address 0 as a 16-bit register value, use FC 3, address 40001 in your DCS poll command.
In our MVI56-MNET module, internal memory addresses 0-3999 are made available by our Modbus TCP Server driver as virtual Modbus bit addresses 00001-63999 for bit Function Codes (FCs) 1, 5, or 15 [note: addressing for bit commands is done by bit number, not register address]; as Input Register addresses 30001-34000 for Input Register FC 4; and as Holding Register addresses 40001-44000 for Holding Register FC 3, 6 or 16; assuming you leave all the Offset values set to zero in your MNET configuration file. In other words, data for bit addresses 00001-00016, register 30001, and register 40001 will all come from the same internal module memory address of 0, unless you use Offset values to change the default starting points of the different register address ranges (default is 0.)
If you need a more detailed explanation, you may want to call Prosoft Tech Support at: (661) 716-5100.
|
