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

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

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

PG-101-106-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-101-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-101-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 provide data output on Metasys N2.
• The site has a power meters on Modbus TCP which needs to be monitored by controllers on Metasys N2.
• A direct exchange of data between Metasys N2 Controllers and Power meters is not possible as the Metasys N2 Controllers provide data output on Metasys N2 and Power meters understands Modbus TCP 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 TCP is an Ethernet based protocol. Hence, a converter is needed which converts the data output from Modbus TCP device to Metasys N2 and vice versa.
• PG-101-106-AA Modbus TCP to Metasys N2 converter is an excellent solution to this requirement. This helps the gateway in reading data from the Power meters on Modbus TCP and it caches this data internally and then provides it on Metasys N2 when requested from Controllers system.

Scenario 2

• There are several Thermostats on the site which provide data output on Metasys N2.
• The site has a SCADA on Modbus TCP that needs data from Thermostats which are on Metasys N2.
• A direct exchange of data between Thermostats and SCADA is not possible as the Thermostats provide data output on Metasys N2 and the SCADA understands Modbus TCP 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 TCP is an Ethernet based protocol. Hence, a converter is needed which converts the data output from Modbus TCP device to Metasys N2 and vice versa.
• PG-101-106-AA Modbus TCP to Metasys N2 converter is an excellent solution to this requirement. This helps the gateway in reading data from the Thermostats on Metasys N2 and it caches this data internally and then provides it on Modbus TCP when requested from SCADA system.

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.

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