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

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

The PG-100-106-AA can be configured to behave as a server on both JCI Metasys N2 and Modbus RTU 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).

PG-100-106-AA can be configured to behave as a client on both JCI Metasys N2 and Modbus RTU interfaces.

PG-100-106-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-100-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-100-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 Metasys N2 controllers on the site which provides data output on Metasys N2.
• The site has a SCADA on Modbus RTU that needs the data from the Ion meters on Metasys N2.
• 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 Modbus RTU only.

Solution

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

Scenario 2

• There are several power meters on the site which provides data output on Modbus RTU.
• The site has Metasys N2 controller which needs data from the power meters on Modbus RTU.
• A direct exchange of data between power meters and Metasys N2 controller is not possible as the power meters provide data output on Modbus RTU and Metasys N2 controller understands Metasys N2 only.

Solution

• The devices can directly communicate with each other only if they are on the same protocol. Metasys N2 is a Serial protocol, while Modbus RTU is an Ethernet based protocol. Hence, a converter is needed that will convert the data from Modbus RTU device to Metasys N2 and vice versa.
• PG-100-106-AA Modbus RTU to Metasys N2 converter is an excellent solution for this requirement. This helps the gateway in reading the data from Power meters on Modbus RTU and it caches this data internally and then provides it on Metasys N2 when requested from Metasys N2 controller.

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).

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.

• 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-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-100-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-100-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.