ProtoConvert recommends the FieldServer gateway for your Modbus RTU protocol conversion requirements. We configure and sell FieldServer gateways. We will help you find the right solution for your requirement and support you with the configuration and commissioning.
This gateway can accept Modbus RTU data and publish it as OPC data.
In summary, this gateway can act as:
Client/Master on the OPC network: Hence it is capable of reading data from the various OPC slave devices and writing data to them if required.
Server/Slave on the OPC network: You can use the gateway in this mode if you have an OPC master on the network which would be reading data from the gateway.
Server on the Modbus RTU network: The gateway has a Modbus RTU server interface. Hence your Modbus RTU client can write data to the gateway's Modbus RTU server interface.
|
Protocol Datasheets
OPC
Hardware Datasheets
QuickServer
FS-3510
Configuration Manuals
Modbus RTU
OPC Server
|
Question/Purchase
FieldServer Gateways for Modbus RTU - OPC
This table lists the different FieldServer had ware platforms which support Modbus RTU - OPC conversion. You can make a choice depending on the number of serial/Ethernet /lonworks ports you require and the point count capacity being considered.
We will help choose the right gateway model for you. Please contact us with your detailed requirement.
Device Type
|
Serial Ports
|
Lonworks Ports
|
Ethernet Ports
|
Base Point Count Capacity
|
Extended Point Count Capacity
|
Enhanced Quick Server
|
2
|
0
|
1
|
500
|
1000
|
FS-B3510
|
2xRS-485
2xRS-232
1xRS-232 System Port
|
1
|
2
|
1000
|
10000
|
How to configure the FieldServer gateway?
-We will configure the gateway for you based on your requirement and support you during commissioning of the gateway, so you do not have to worry about configuring the FieldServer gateway.
-However, it is very helpful to know how to configure the devices. All the required tools and supporting product manuals with be provided completely free of cost with your purchase.
-Configuration of the FieldServer is done using a '.csv' file. This file can be edited using any text editor (example Microsoft excel).
-In this file we need to enter information for the Client and Server side interfaces of the FieldServer. This includes but is not limited to:
Node ids of the slave devices
IP addresses/device address of the slave devices
Baud rate, parity, stop bits for serial communication
Scan rates
- And finally we need to create an internal mapping that would map each data value read on the client side to a data value on the server side.
-For detailed information on configuration please get in touch with us and review the configuration manual on top of this page