PG-103-104-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.
PG-103-104-XX Gateway model supports BACnet IP and SNMP 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 SNMP client, the PG-103-104-XX can read data from your SNMP devices and publish it as BACnet IP data. Also, it can write commands sent from the BACnet IP side to the SNMP devices.
When configured as a BACnet IP client, the PG-103-104-XX can read data from your BACnet IP devices and publish it as SNMP data. Also, it can write commands sent from the SNMP side to the BACnet IP devices.
The PG-103-104-XX can be configured to behave as a server on both SNMP and BACnet IP interfaces. This mode is useful when data exchange is required between a SNMP client (for eg. SCADA) and a BACnet IP client (for eg. a Building Management System).
PG-103-104-XX can be configured to behave as a client on both SNMP and BACnet IP interfaces.
PG-103-104-XX gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-104-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 PG-103-104-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 UPS and PAC units on the site which provides data output on SNMP.
- The site has a Building Management System on BACnet IP which needs the energy data from the Variable frequency drives.
- A direct exchange of data between Variable frequency drives and Building Management System is not possible as Variable frequency drives provides data output on SNMP and Building Management System understands BACnet IP only.
Solution
- The devices can directly communicate with each other only if they are on the same protocol. BACnet IP and SNMP both are Ethernet based protocols and hence, a converter is needed which will convert the data from SNMP device to BACnet IP and vice versa.
- PG-103-104-XX BACnet IP to SNMP converter is an excellent solution to this requirement. This helps the gateway in reading the data from the Variable frequency drives on BACnet IP and it caches this data internally and then provides it on SNMP when requested from the Building Management System.
Scenario 2
- There are BTU meters on the other site which provides data output on BACnet IP.
- The site has SCADA on SNMP which needs the data from BTU meters on BACnet IP.
- A direct exchange of data between BTU meters and SCADA is not possible as BTU meters provide data output on BACnet IP and SCADA understands SNMP only.
Solution
- The devices can directly communicate with each other only if they are on the same protocol. BACnet IP and SNMP both are Ethernet based protocols and hence, a converter is needed which will convert the data from SNMP device to BACnet IP and vice versa.
- PG-103-104-XX BACnet IP to SNMP converter is an excellent solution to this requirement. This helps the gateway in reading the data from the BTU meters on BACnet IP and it caches this data internally and then provides it on SNMP when requested from SCADA.
Outline of SNMP and BACnet IP
SNMP
Simple Network Management Protocol (SNMP) was originally made for the management of devices such as switches and routers, its usage has grown so much nowadays that it is used for monitoring of nearly any electronic device one can think of. It is a protocol which is majorly designed to manage networked devices from a single-central location. SNMP is now used to monitor and manage television broadcast studios, airborne military platforms, automated fare collection systems, emergency radio networks, energy distribution systems, and much more. Microsoft Windows Server 2003 provides SNMP agent software that works with third-party SNMP management software to monitor the status of managed devices and applications.
BACnet IP
BACnet (Building Automation and Control Network) is a communications protocol that helps the communication between building automation end-devices and building management systems. The BACnet protocol specification like every other protocol specification defines both how data is represented on the network and the services that are used to move data from one BACnet node to another. The specification also tells us about messages that identify data and network nodes such as Who-Has, I-Have, Who-Is, and I-Am.
To meet the requirement of the widest possible set of applications BACnet was designed to support several different physical and link layers.
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.
How to configure the PG-103-105-AC 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-103-105-AC 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-105-AC 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-105-AC. 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.