PG-101-103-XX

PG-101-103-XX

by sales.aus@protoconvert.com
Download Datasheet

PG-101-103-XX 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.

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

When configured as a BACnet IP client, our gateway can read data from your BACnet IP devices  and publish it as Modbus TCP data. Also,  it can write commands sent from the Modbus TCP side to the BACnet IP devices.

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

The PG-101-103-XX can be configured to behave as a client on both Modbus TCP and BACnet IP interfaces.

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

Key Features

  • Ability to interface up to 1000 points of common BAS protocols
  • 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 Variable frequency drives which can provide data output on Modbus TCP on the site.
  • The site has a building management system on BACnet IP that needs the energy data from the Variable frequency drives.
  • A direct exchange of data between the Variable frequency drives and a Building management system is not possible as the Variable frequency drives provide data output on Modbus TCP and the Building management system understands BACnet IP only.

Solution

  • The devices can only connect directly to each other if they are on the same protocol. Modbus TCP and BACnet IP are Ethernet protocols and hence a converter is needed that can convert the data from the BACnet IP device to Modbus TCP and vice versa.
  • PG-101-103-XX Modbus TCP to BACnet IP converter is an excellent solution for this requirement. It helps the gateway to read the data from the Variable frequency drives on Modbus TCP and it will cache this data internally and then will provide it on BACnet IP when requested from the Building Management system.

Scenario 2

  • We have Thermostats on the site which can provide data output on BACnet IP.
  • The site has a SCADA on Modbus TCP that needs the temperature data from thermostat on BACnet IP.
  • A direct exchange of data between Thermostat and the SCADA is not possible as Thermostat provide data output on BACnet IP and the SCADA understands Modbus TCP only.

Solution

  • The devices can only connect directly to each other if they are on the same protocol. Modbus TCP and BACnet IP are Ethernet protocols and hence a converter is needed that can convert the data from the BACnet IP device to Modbus TCP and vice versa.
  • PG-101-103-XX Modbus TCP to BACnet IP converter is an excellent solution for this requirement. It helps the gateway to read the data from the Thermostat on BACnet IP and it will caches this data internally and then will provide it on Modbus TCP when requested from SCADA.

Outline of Modbus TCP and BACnet IP

Modbus TCP

Modbus TCP 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.

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.

How to configure the PG-101-103-XX 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-101-103-XX 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-101-103-XX 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-101-103-XX. 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.