PG-101-104-XX

PG-101-104-XX

by sales.aus@protoconvert.com
Download Datasheet

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

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

The PG-101-104-XX can be configured to behave as a server on both SNMP and Modbus TCP 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-101-104-XX can be configured to behave as a client on both SNMP and Modbus TCP interfaces.

PG-101-104-XX gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-101-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 from PG-101-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 Systems on the site which provides data output on Modbus TCP.
  • The site has a network management system on SNMP that needs the status information for the UPS systems.
  • A direct exchange of data between UPS systems and Network management systems is not possible as the UPS systems provide data output on Modbus TCP and the Network management systems understands SNMP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. Modbus TCP and SNMP are Ethernet based protocols. Hence, a converter is needed that converts the data from SNMP device to Modbus TCP and vice versa.
  • PG-101-104-XX Modbus TCP to SNMP converter is an excellent solution for this requirement. This helps the gateway in reading the data from the UPS systems on Modbus TCP and it caches this data internally and then provides it on SNMP when requested from the Network management system.

Scenario 2

  • There are UPS and PAC units on the other site which provide data output on SNMP.
  • The site has a SCADA on Modbus TCP that needs the status information from the PAC units and SCADA.
  • A direct exchange of data between UPS and PAC units and SCADA is not possible as the UPS and PAC units provide data output on SNMP 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 and SNMP are Ethernet based protocols. Hence, a converter is needed that converts the data from SNMP device to Modbus TCP and vice versa.
  • PG-101-104-XX Modbus TCP to SNMP converter is an excellent solution for this requirement. This helps the gateway in reading the data from SNMP devices and it caches this data internally and then provides it on Modbus TCP when requested from the SCADA.

Outline of SNMP and Modbus TCP

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.

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.

How to configure the PG-101-104-XX 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-101-104-XX 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-104-XX 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-104-XX. 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.