PG-100-101-AA

PG-100-101-AA

by sales.aus@protoconvert.com
Download Datasheet

PG-100-101-AA is highly powerful, superior, completely configurable and productive Building & Industrial Automation gateway for integrators to effortlessly interface devices to networks in commercial buildings and industrial plants.

PG-100-101-AA Gateway model supports Modbus TCP and Modbus RTU protocols. It is a Bi-directional Converter that can be configured as a Client and/or a Server on either protocol interface.

When configured as a Modbus RTU client, the PG-100-101-AA can read data from your Modbus RTU devices and publish it as Modbus TCP data. Also, it can write commands sent from the Modbus TCP side to the Modbus RTU devices.

When configured as a Modbus TCP client, the PG-100-101-AA can read data from your Modbus TCP devices and publish it as Modbus RTU data. Also,  it can write commands sent from the Modbus RTU side to the Modbus TCP devices.

The PG-100-101-AA can be configured to behave as a server on both Modbus RTU and Modbus TCP interfaces. This mode is useful when data exchange is required between a Modbus RTU client (for eg. SCADA) and a BACnet IP client (for eg. a Building Management System).

PG-100-101-AA can be configured to behave as a client on both Modbus RTU and Modbus TCP interfaces.

PG-100-101-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-100-101-AA gateway runs the same protocol conversion software on a productive and cost efficient platform backed by the experience, engineering expertise and technically proven support that integrators have come to expect from PG-100-101-AA.

Key Features

  • Ability to interface up to 1000 points of common BAS protocols
  • 2xRS 485 Ports, 1xEthernet Port
  • BTL Mark – PG-10XX Series
  • LonMark Certified – PG-10XX Series
  • BACnet COV support for fast data communication while reducing traffic over a BACnet network
  • Multi-configuration capability; specific configurations selectable via DIP switches or software
  • Flat panel mount standard, DIN rail mount option
  • DIP switches to select baud rate or node ID on the fly

PG-100-101-AA Modbus TCP to Modbus RTU Gateway

Scenario 1

  • There are several Schneider Ion energy meters on the site which provides data output on Modbus RTU.
  • The site has a SCADA on Modbus TCP which needs the data from the Ion meters on Modbus RTU.
  • A direct exchange of data between Energy meters and SCADA is not possible as the Energy meters provide data output on Modbus RTU and SCADA understands Modbus TCP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. Modbus RTU is a Serial protocol, while Modbus TCP is an Ethernet protocol. Hence, a converter is needed that converts the data from Modbus TCP device to Modbus RTU and vice versa.
  • PG-100-101-AA Modbus TCP to Modbus RTU converter is an excellent solution to this requirement. This helps the gateway in reading the data from the Energy meters on Modbus RTU and it caches this data internally and then provides it on Modbus TCP when requested from the SCADA system.

Scenario 2

  • There are several Variable frequency drives on the site which provide data output on Modbus TCP.
  • The site has a PLC on Modbus RTU that needs data from Variable frequency drives on Modbus TCP.
  • A direct exchange of data between Variable frequency drives and PLC is not possible as Variable frequency drives provide data output on Modbus TCP and PLC understands Modbus RTU only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. Modbus RTU is a Serial protocol, while Modbus TCP is an Ethernet protocol. Hence, a converter is needed that converts the data from Modbus TCP device to Modbus RTU and vice versa.
  • PG-100-101-AA Modbus TCP to Modbus RTU converter is an excellent solution to this requirement. This helps the gateway in reading the data from the Variable frequency drives on Modbus TCP and it caches this data internally and then provides it on Modbus RTU when requested from the PLC.

Outline of Modbus RTU and Modbus TCP

Modbus RTU

ModbusRTU is a serial communication protocol that connects different devices on the same network and would make the communication between them possible.

Modbus is transmitted over serial lines between devices. The cables used for the conecction are either RS-485 or RS-232 cables. The simplest setup would be a single serial cable connecting the serial ports on two devices, a Master and a Slave.

The data is sent as series of ones and zeroes called bits. Each bit is sent as a voltage. Zeroes are sent as positive voltages and ones as negative. The bits are sent very quickly. A typical transmission speed is 9600 baud (bits per second).

Modbus TCP

ModbusTCP covers the use of Modbus communication via an ‘Intranet’ or ‘Internet’ environment using the TCP/IP protocols. The most common use of the protocols at this time is for Ethernet attachment of PLC’s, I/O modules, and Gateways to other simple field buses or I/O networks.

There will always be this question why the connection-oriented TCP/IP protocol is used rather than the datagram-oriented UDP. The Primary reason is to keep control of an individual ‘communication’ by isolating it in a connection which can be identified, cancelled , and supervised without the need of specific action on the client and server applications. This gives the mechanism a tolerance to network performance changes, and also gives a scope to add security features such as firewalls and proxies.

MODBUS/TCP/IP handles two different situations. A connection can be recognized too easily at the protocol level. A single connection can be used to carry out multiple independent communications. To add to it, TCP/IP allows a huge number of concurrent connections, so the user decides to re-use an old connection or reconnect to a frequently used connection.

The Modbus device can be connected using an Ethernet port on the gateway. We can make a query using any standard Modbus Scanner to extract the value from a Modbus device. All requests are sent via TCP/IP on registered port 502.

How to configure the PG-100-101-AA 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 PG-100-101-AA gateway.
  • However, it is very helpful to know how to configure the devices. All the required tools and supporting product manuals will be provided completely free of cost with your purchase.
  • Configuration of the PG-100-101-AA 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 PG-100-101-AA. This includes but is not limited to
  1. Node ids of the slave devices
  2. IP addresses/device address of the slave devices
  3. Baud rate, parity, stop bits for serial communication
  4. 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.