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

When configured as a Modbus TCP client, the PG-101-105-AC can read data from your Modbus TCP devices and publish it as LonWorks data. Also, it can write commands sent from the LonWorks side to the Modbus TCP devices.

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

PG-101-105-AC can be configured to behave as a client on both LonWorks and Modbus TCP interfaces.

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

Key Features

• Ability to interface up to 1000 points of common BAS protocols
• 1xLonWorks FTT10 port, 1xRS485 Port, 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
• Capacity of 1000 LonWorks network variables – almost 5 times more than competition – PG-10XX Series
• 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 on the site which provides data output on Modbus TCP.
• The site has a PLC on LonWorks control the Variable frequency drives.
• A direct exchange of data between Variable frequency drives and PLC is not possible as the Variable frequency drives provides data output on Modbus TCP and PLC understands LonWorks only.

Solution

• The devices can directly communicate with each other only if they are on the same protocol. Modbus TCP is Ethernet based protocol, and LonWorks is a Serial protocol. Hence, a converter is needed which converts the data from LonWorks device to Modbus TCP and vice versa.
• PG-101-105-AC Modbus TCP to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from Variable frequency drives on Modbus TCP and it caches this data internally and then provides it on LonWorks when requested from the PLC.

Scenario 2

• There are Thermostats on the other site which provides data output on LonWorks.
• The site has a SCADA on Modbus TCP which needs the temperature data from thermostats on LonWorks.
• A direct exchange of data between Thermostats and SCADA is not possible as thermostats provide data output on LonWorks and SCADA understands Modbus TCP only.

Solution

• The devices can directly communicate with each other only if they are on the same protocol. Modbus TCP is Ethernet based protocol, and LonWorks is a Serial protocol. Hence, a converter is needed which converts the data from LonWorks device to Modbus TCP and vice versa.
• PG-101-105-AC Modbus TCP to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from Thermostat on LonWorks and it caches this data internally and then provides it on Modbus TCP when requested from the 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.

LonWorks

LonWorks (local operation network) is a networking platform specifically created to address the needs of control applications. This platform is created for networking devices over media such as twisted pair, power lines, fiber optics, and RF. It is used for the automation of various functions within buildings such as lighting and HVAC see building automation.

There are two physical-layer signaling technologies, twisted pair “free topology” and power line carrier, are typically included in each of the standards created around the LonWorks technology. The two-wire layer operates at 78 Kbit/s using differential Manchester encoding, while the power line achieves either 5.4 or 3.6 Kbit/s, depending on frequency.

Additionally, the LonWorks platform uses an affiliated Internet protocol (IP) tunneling standard in use by a number of manufacturers to connect the devices on previously deployed and new LonWorks platform-based networks to IP-aware applications or remote network-management tools. Many LonWorks platform-based control applications are being implemented with some sort of IP integration, either at the UI/application level or in the controls infrastructure.

• 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-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-101-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-101-105-AC. 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.