PG-102-106-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-102-106-AA Gateway model supports BACnet MS/TP and JCI Metasys N2 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 JCI Metasys N2 client, the PG-102-106-AA can read data from your JCI Metasys N2 devices and publish it as BACnet MS/TP data. Also, it can write commands sent from the BACnet MS/TP side to the JCI Metasys N2 devices.

When configured as a BACnet MS/TP client, the PG-102-106-AA can read data from your BACnet MS/TP devices and publish it as JCI Metasys N2 data. Also, it can write commands sent from the JCI Metasys N2 side to the BACnet MS/TP devices.

The PG-102-106-AA can be configured to behave as a server on both JCI Metasys N2 and BACnet MS/TP interfaces. This mode is useful when data exchange is required between a JCI Metasys N2 client (for eg. SCADA) and a BACnet IP client (for eg. a Building Management System).

The PG-102-106-AA can be configured to behave as a client on both JCI Metasys N2 and BACnet MS/TP interfaces.

PG-102-106-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-102-106-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-102-106-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 Metays N2 Controllers on the site which provide data output on Metasys N2.
• The site has SCADA on BACnet MS/TP which needs the data from the Metasys N2 Controllers.
• A direct exchange of data between Metasys N2 Controllers and SCADA is not possible as the Metasys N2 Controllers provide data output on Metasys N2 and SCADA understands BACnet MS/TP only.

Solution

• The devices can directly communicate with each other only if they are on the same protocol. Metasys N2 and BACnet MS/TP are Serial based Protocol. Hence, a converter is needed which converts the data from BACnet MS/TP device to Metasys N2 and vice versa.
• PG-102-106-AA Metasys N2 to BACnet MS/TP converter is an excellent solution for this requirement. This helps the gateway in reading data from the Energy meters on Metasys N2 and it caches this data internally and then provides it on BACnet MS/TP when requested from the SCADA system.

Scenario 2

• There are several variable frequency drives on the site which provide data output on BACnet MS/TP.
• The site has a NAE Controller on Metasys N2 that needs data from Variable frequency drives on BACnet MS/TP.
• A direct exchange of data between the Variable frequency drives and NAE Controller is not possible as the Variable frequency drives provide data output on BACnet MS/TP and the NAE Controller understands Metasys N2 only.

Solution

• The devices can directly communicate with each other only if they are on the same protocol. Metasys N2 and BACnet MS/TP are Serial based Protocol. Hence, a converter is needed which converts the data from BACnet MS/TP device to Metasys N2 and vice versa.
• PG-102-106-AA Metasys N2 to BACnet MS/TP converter is an excellent solution for this requirement. This helps the gateway in reading data from the Variable frequency drives on BACnet MS/TP and it caches this data internally and then provides it on Metasys N2 when requested from the NAE Controller.

Metasys N2

Metasys N2 was developed by Johnson Controls as a network to interface their various devices and controllers. It is on the physical layer RS-485 set of data communications standards and supports 9600 baud, 8 data bits, and no parity and in half-duplex mode only. This network supports communications with a huge range of devices manufactured by Johnson Controls and some other companies. Metasys N2 by Johnson Controls is a master/slave protocol with one master only so it is not possible to have two devices performing this function on the same network.

BACnet MSTP

BACnet MS/TP is exclusive to BACnet and can be implemented using the EIA-485 signaling standard. This is a shielded twisted-pair (STP) LAN operating at speeds from 9.6Kbit/s to 76.0Kbit/s. This LAN type is particularly suitable for single controller and low cost communications.

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-102-106-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-102-106-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-102-106-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.