PG-103-100-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-103-100-AA Gateway model supports BACnet IP 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-103-100-AA can read data from your Modbus RTU devices and publish it as BACnet IP data. Also, it can write commands sent from the BACnet IP side to the Modbus RTU devices.

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

The PG-103-100-AA can be configured to behave as a server on both Modbus RTU and BACnet IP 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).

The PG-103-100-AA can be configured to behave as a client on both Modbus RTU and BACnet IP interfaces.

PG-103-100-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-100-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-103-100-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

Scenario 1

• There are several Schneider Ion meters on site which can provide data output on Modbus RTU.
• The site has a building management system on BACnet IP that needs the energy data from the Schneider Ion meters.
• A direct exchange of data is not possible between Schneider Ion meters and a Building management system as the Schneider Ion meters provide data output on Modbus RTU and the Building management system understands BACnet IP only.

Solution

• The devices can directly communicate with other only if they are on the same protocol. Modbus RTU is a Serial protocol and BACnet IP is an Ethernet based Protocol. Hence, a converter is needed which can convert the data from BACnet IP device to Modbus RTU and vice versa.
• PG-103-100-AA Modbus RTU to BACnet IP converter is an excellent solution for this requirement. This helps the gateway in reading the data from the Energy meters on Modbus RTU and it caches the data internally and then provides it on BACnet IP when requested from Building Management System.

Scenario 2

• Modbus RTU PLC needs to read data from BACnet IP based Thermostats.
• There are Thermostats on the site which can provide data output on BACnet IP.
• A PLC on Modbus RTU on the site needs the temperature data from Thermostat on BACnet IP.
• A direct exchange of data between a Thermostat and a PLC is not possible as the Thermostat provide data output on BACnet IP and the PLC understands Modbus RTU only.

Solution

• The devices can directly communicate with other only if they are on the same protocol. Modbus RTU is a Serial protocol and BACnet IP is an Ethernet based Protocol. Hence, a converter is needed which can convert the data from BACnet IP device to Modbus RTU and vice versa.
• PG-103-100-AA Modbus RTU to BACnet IP converter is an excellent solution for this requirement. This helps the gateway in reading the data from the Thermostats on BACnet IP and it caches the data internally and then provides it on Modbus RTU when requested from the PLC.

Modbus RTU

Modbus RTU 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 connection 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).

BACnet IP

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

Like the Control and Information Protocol (CIP) used in industrial application, BACnet uses objects to represent data on a network. Objects defined by the BACnet specification include Analog Input, Analog Output, Analog Value, Binary Input, Binary Output, Binary Value, Multi-State Input, Multi-State Output, Calendar, Event-Enrollment Program, Schedule, Command, and Device.

The BACnet protocol is a completely non-proprietary open communication software standard. The standard is now controlled by the ANSI (American National Standards Institute) and ASHRAE (American Society of Heating Refrigeration and Air-Conditioning Engineers) Standard 135- 1995. In June of 1995, ASHRAE adopted BACnet as a standard for the Building Automation industry.

• 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-103-100-AA 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 PG-103-100-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-103-100-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.