Archives

Share

PG-104-142

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

SNMP – Agilent Gateway Solutions (PG-104-142) is a very powerful and outstanding processor that is totally adjustable and productive Building & Industrial Automation gateway that allows integrators to easily interface devices to networks in commercial buildings and industrial facilities.

 

PG-104-142 SNMP and Agilent protocols are supported by the gateway. On each protocol interface, it can be configured as a Client or a Server.

The Gateway can read data from Agilent devices and provide it via SNMP when configured as an Agilent client. It can also write commands to Agilent devices from the SNMP side.

 

The Gateway may read data from your SNMP devices and provide it as Agilent data when setup as an SNMP client. It can also send commands to SNMP devices from the Agilent side.

On both Agilent and SNMP interfaces, the Gateway can be set to act as a client.

 

With its strong set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering knowledge, and technically proven support that integrators have come to expect from this Gateway.

SNMP-Agilent-Proto

Features

  • Up to 1000 points can be interfaced
  • DIN rail attachment
  • One-wire serial port built-in

PG-101-142

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

Modbus TCP – Agilent Gateway Solutions (PG-101-142) is a very powerful and outstanding processor that is totally flexible and productive Building & Industrial Automation gateway enabling integrators to easily connect devices to networks in commercial buildings and industrial facilities.

 

PG-101-142 The Agilent and Modbus TCP protocols are supported by the gateway. On each protocol interface, it can be configured as a Client or a Server.

The Gateway can read data from your Modbus TCP devices and deliver it on Agilent when setup as a Modbus TCP client. It can also write commands to the Modbus TCP devices from the Agilent side.

 

The Gateway can read data from Agilent devices and provide it as Modbus TCP data when configured as an Agilent client. It can also write commands to Agilent devices from the Modbus TCP side.

 

On both Modbus TCP and Agilent interfaces, the Gateway may be set to act as a server. When data transmission between a Modbus TCP client (for example, SCADA) and an Agilent client is necessary, this mode is beneficial (for e.g. a Building Management System).

 

On both Modbus TCP and Agilent interfaces, the Gateway may be set to act as a client.

With its strong set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering knowledge, and technically proven support that integrators have come to expect from this Gateway.

Modbus-TCP_IP-Agilent-Proto

Features

  • Up to 1000 points can be interfaced
  • DIN rail attachment
  • One-wire serial port built-in

PG-100-142

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

Modbus RTU – Agilent Gateway Solutions (PG-100-142) is a very powerful and outstanding processor that is totally flexible and productive Building & Industrial Automation gateway enabling integrators to easily connect devices to networks in commercial buildings and industrial facilities.

 

PG-100-142 The Agilent and Modbus RTU protocols are supported by the gateway. On each protocol interface, it can be configured as a Client or a Server.

The Gateway can read data from your Modbus RTU devices and deliver it on Agilent when setup as a Modbus RTU client. It can also write commands to the Modbus RTU devices from the Agilent side.

 

The Gateway can read data from Agilent devices and provide it as Modbus RTU data when configured as an Agilent client. It can also write commands to Agilent devices from the Modbus RTU side.

 

On both Modbus RTU and Agilent interfaces, the Gateway may be set to act as a server. When data transmission between a Modbus RTU client (for example, SCADA) and an Agilent client is necessary, this mode is beneficial (for e.g. a Building Management System).

 

On both Modbus RTU and Agilent interfaces, the Gateway may be set to act as a client.

With its strong set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering knowledge, and technically proven support that integrators have come to expect from this Gateway.

Modbus-RTU-Agilent-Proto

Features

  • Up to 1000 points can be interfaced
  • DIN rail attachment
  • One-wire serial port built-in

PG-103-142

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

BACnet IP – Agilent Gateway Solutions (PG-103-142) is a very powerful and outstanding processor that is totally flexible and productive Building & Industrial Automation gateway enabling integrators to easily connect devices to networks in commercial buildings and industrial facilities.

 

PG-103-142 The Agilent and BACnet IP protocols are supported by the gateway. On each protocol interface, it can be configured as a Client or a Server.

The Gateway can read data from your BACnet IP devices and deliver it on Agilent when setup as a BACnet IP client. It can also write commands to the BACnet IP devices from the Agilent side.

 

The Gateway can read data from Agilent devices and provide it as BACnet IP data when configured as an Agilent client. It can also write commands to Agilent devices from the BACnet IP side.

 

On both BACnet IP and Agilent interfaces, the Gateway may be set to act as a server. When data transmission between a BACnet IP client (for example, SCADA) and an Agilent client is necessary, this mode is beneficial (for e.g. a Building Management System).

 

On both BACnet IP and Agilent interfaces, the Gateway may be set to act as a client.

With its strong set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering knowledge, and technically proven support that integrators have come to expect from this Gateway.

BACnet-IP-Agilent

Features

  • Up to 1000 points can be interfaced
  • DIN rail attachment
  • One-wire serial port built-in
  • Support for BACnet COV for rapid data transmission while minimizing BACnet network load.

PG-102-142

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

BACnet MSTP – Agilent Gateway Solutions (PG-102-142) is a very powerful and outstanding processor that is totally flexible and productive Building & Industrial Automation gateway enabling integrators to easily connect devices to networks in commercial buildings and industrial facilities.

 

PG-102-142 The Agilent and BACnet MSTP protocols are supported by the gateway. On each protocol interface, it can be configured as a Client or a Server.

The Gateway can read data from your BACnet MSTP devices and deliver it on Agilent when setup as a BACnet MSTP client. It can also write commands to the BACnet MSTP devices from the Agilent side.

 

The Gateway can read data from Agilent devices and provide it as BACnet MSTP data when configured as an Agilent client. It can also write commands to Agilent devices from the BACnet MSTP side.

 

On both BACnet MSTP and Agilent interfaces, the Gateway may be set to act as a server. When data transmission between a BACnet MSTP client (for example, SCADA) and an Agilent client is necessary, this mode is beneficial (for e.g. a Building Management System).

 

On both BACnet MSTP and Agilent interfaces, the Gateway may be set to act as a client.

With its strong set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering knowledge, and technically proven support that integrators have come to expect from this Gateway.

BACnet-MSTP-Agilent

Features

  • Up to 1000 points can be interfaced
  • DIN rail attachment
  • One-wire serial port built-in
  • Support for BACnet COV for rapid data transmission while minimizing BACnet network load.

PG-106-125

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC DA – JCI Metasys N2 (PG-106-125) Gateway Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

JCI Metasys N2 and OPC DA (client only) protocols are supported by the PG-106-125 gateway.

 

This gateway may be set up to do the following:

OPC DA Client and JCI Metasys N2 Client : This gateway will connect to a third-party OPC DA server and read or write tags. It will, however, be a JCI Metasys N2 client that can receive and write data from a JCI Metasys N2 server.

When you have JCI Metasys N2 -based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC DA tags on a regular basis and write the values to a JCI Metasys N2 server device.

 

OPC DA Client and JCI Metasys N2 Server: The most frequent form of operation is using an OPC DA client and a JCI Metasys N2 server. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on JCI Metasys N2.

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on JCI Metasys N2.

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this JCI Metasys N2 data (and hence have access to the OPC DA data via the gateway). OPC DA tags may also be written from the JCI Metasys N2 side. As a result, the BAS/BMS system can use the gateway to set values on the OPC DA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

 

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.

 

PG-105-125

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC DA – Lonworks Gateway (PG-105-125) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

Lonworks and OPC DA (client only) protocols are supported by the PG-105-125 gateway.

 

This gateway may be set up to do the following:

OPC DA Client and Lonworks Client : This gateway will connect to a third-party OPC DA server and read or write tags. It will, however, be a Lonworks client that can receive and write data from a Lonworks server.

When you have Lonworks -based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC DA tags on a regular basis and write the values to a Lonworks server device.

 

OPC DA Client and Lonworks Server: The most frequent form of operation is using an OPC DA client and a Lonworks server. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on Lonworks.

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on Lonworks.

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this Lonworks data (and hence have access to the OPC DA data via the gateway). OPC DA tags may also be written from the Lonworks side. As a result, the BAS/BMS system can use the gateway to set values on the OPC DA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

 

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.

 

PG-106-119

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC UA – JCI Metasys N2 (PG-106-119) Gateway Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

JCI Metasys N2 and OPC UA (client only) protocols are supported by the PG-106-119 gateway.

 

This gateway may be set up to do the following:

OPC UA Client and JCI Metasys N2 Client : This gateway will connect to a third-party OPC UA server and read or write tags. It will, however, be a JCI Metasys N2 client that can receive and write data from a JCI Metasys N2 server.

When you have JCI Metasys N2 -based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC UA tags on a regular basis and write the values to a JCI Metasys N2 server device.

 

OPC UA Client and JCI Metasys N2 Server: The most frequent form of operation is using an OPC UA client and a JCI Metasys N2 server. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on JCI Metasys N2.

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on JCI Metasys N2.

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this JCI Metasys N2 data (and hence have access to the OPC UA data via the gateway). OPC UA tags may also be written from the JCI Metasys N2 side. As a result, the BAS/BMS system can use the gateway to set values on the OPC UA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

 

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.

 

PG-105-119

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC UA – Lonworks Gateway (PG-105-119) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

Lonworks and OPC UA (client only) protocols are supported by the PG-105-119 gateway.

 

This gateway may be set up to do the following:

OPC UA Client and Lonworks Client : This gateway will connect to a third-party OPC UA server and read or write tags. It will, however, be a Lonworks client that can receive and write data from a Lonworks server.

When you have Lonworks -based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC UA tags on a regular basis and write the values to a Lonworks server device.

 

OPC UA Client and Lonworks Server: The most frequent form of operation is using an OPC UA client and a Lonworks server. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on Lonworks.

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on Lonworks.

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this Lonworks data (and hence have access to the OPC UA data via the gateway). OPC UA tags may also be written from the Lonworks side. As a result, the BAS/BMS system can use the gateway to set values on the OPC UA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

 

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.

 

PG-104-125

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC DA – SNMP Gateway (PG-104-125) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

SNMP and OPC DA (client only) protocols are supported by the PG-104-125 gateway.

 

This gateway may be set up to do the following:

OPC DA Client and SNMP Client : This gateway will connect to a third-party OPC DA server and read or write tags. It will, however, be a SNMP client that can receive and write data from a SNMP server.

When you have SNMP -based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC DA tags on a regular basis and write the values to a SNMP server device.

 

OPC DA Client and SNMP Server: The most frequent form of operation is using an OPC DA client and a SNMP server. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on SNMP .

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on SNMP .

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this SNMP data (and hence have access to the OPC DA data via the gateway). OPC DA tags may also be written from the SNMP side. As a result, the BAS/BMS system can use the gateway to set values on the OPC DA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

 

SNMP-OPC-DA

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.
  • In-built one wire Serial Port

 

Application Scenarios:

  • This gateway is frequently used to connect OPC DA-enabled lift/elevator/escalator systems to a BMS/BAS system running on SNMP .
  • An OPC DA interface is available on some fire alarm systems. You may also use this gateway to monitor your fire system from your SNMP -based BMS/BAS.

PG-103-125

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC DA – BACnet IP Gateway (PG-103-125) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

BACnet IP and OPC DA (client only) protocols are supported by the PG-103-125 gateway.

 

This gateway may be set up to do the following:

OPC DA Client and BACnet IP Client : This gateway will connect to a third-party OPC DA server and read or write tags. It will, however, be a BACnet client that can receive and write data from a BACnet server.

When you have BACnet IP -based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC DA tags on a regular basis and write the values to a BACnet server device.

 

OPC DA Client and BACnet IP Server: The most frequent form of operation is using an OPC DA client and a BACnet IP server. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on BACnet IP .

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on BACnet IP .

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this Modbus data (and hence have access to the OPC DA data via the gateway). OPC DA tags may also be written from the BACnet side. As a result, the BAS/BMS system can use the gateway to set values on the OPC DA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

BACnet-IP-OPC-DA

 

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.
  • BACnet COV support for fast data communication while reducing the traffic over a BACnet network

 

Application Scenarios:

  • This gateway is frequently used to connect OPC DA-enabled lift/elevator/escalator systems to a BMS/BAS system running on BACnet IP .
  • An OPC DA interface is available on some fire alarm systems. You may also use this gateway to monitor your fire system from your BACnet-based BMS/BAS.

PG-102-125

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC DA – BACnet MSTP Gateway (PG-102-125) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

BACnet MSTP and OPC DA (client only) protocols are supported by the PG-102-125 gateway.

 

This gateway may be set up to do the following:

OPC DA Client and BACnet MSTP Client : This gateway will connect to a third-party OPC DA server and read or write tags. It will, however, be a BACnet client that can receive and write data from a BACnet server.

When you have BACnet MSTP-based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC DA tags on a regular basis and write the values to a BACnet server device.

 

OPC DA Client and BACnet MSTP Server: The most frequent form of operation is using an OPC DA client and a BACnet MSTP server. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on BACnet MSTP.

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on BACnet MSTP.

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this Modbus data (and hence have access to the OPC DA data via the gateway). OPC DA tags may also be written from the BACnet side. As a result, the BAS/BMS system can use the gateway to set values on the OPC DA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

 

BACnet-MSTP-OPC-DA

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.
  • BACnet COV support for fast data communication while reducing the traffic over a BACnet network

 

Application Scenarios:

  • This gateway is frequently used to connect OPC DA-enabled lift/elevator/escalator systems to a BMS/BAS system running on BACnet MSTP.
  • An OPC DA interface is available on some fire alarm systems. You may also use this gateway to monitor your fire system from your BACnet-based BMS/BAS.

PG-101-125

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC DA – Modbus TCP Gateway (PG-101-125) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

Modbus TCP and OPC DA (client only) protocols are supported by the PG-101-125 gateway.

 

This gateway may be set up to do the following:

OPC DA Client and Modbus TCP Client : This gateway will connect to a third-party OPC DA server and read or write tags. It will, however, be a Modbus client that can receive and write data from a Modbus server.

When you have Modbus TCP-based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC DA tags on a regular basis and write the values to a Modbus server device.

 

OPC DA Client and Modbus TCP Server: The most frequent form of operation is using an OPC DA client and a Modbus TCP server. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on Modbus TCP.

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on Modbus TCP.

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this Modbus data (and hence have access to the OPC DA data via the gateway). OPC DA tags may also be written from the Modbus side. As a result, the BAS/BMS system can use the gateway to set values on the OPC DA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

Modbus-TCP_IP-OPC-DA

 

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.

 

Application Scenarios:

  • This gateway is frequently used to connect OPC DA-enabled lift/elevator/escalator systems to a BMS/BAS system running on Modbus TCP.
  • An OPC DA interface is available on some fire alarm systems. You may also use this gateway to monitor your fire system from your Modbus-based BMS/BAS.

PG-100-125

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC DA – Modbus RTU Gateway (PG-100-125) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

Modbus RTU and OPC DA (client only) protocols are supported by the PG-100-125 gateway.

 

This gateway may be set up to do the following:

OPC DA Client and Modbus RTU Client : This gateway will connect to a third-party OPC DA server and read or write tags. It will, however, be a Modbus client that can receive and write data from a Modbus server.

When you have Modbus MSTP-based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC DA tags on a regular basis and write the values to a Modbus server device.

 

OPC DA Client and Modbus RTU Server: The most frequent form of operation is using an OPC DA client and a Modbus RTU server. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on Modbus RTU.

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC DA tags and broadcast them as a server on Modbus RTU.

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this Modbus data (and hence have access to the OPC DA data via the gateway). OPC DA tags may also be written from the Modbus side. As a result, the BAS/BMS system can use the gateway to set values on the OPC DA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

Modbus-RTU-OPC-DA

 

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.

 

Application Scenarios:

  • This gateway is frequently used to connect OPC DA-enabled lift/elevator/escalator systems to a BMS/BAS system running on Modbus RTU.
  • An OPC DA interface is available on some fire alarm systems. You may also use this gateway to monitor your fire system from your Modbus-based BMS/BAS.

PG-104-119

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC UA – SNMP Gateway (PG-104-119) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

SNMP and OPC UA (client only) protocols are supported by the PG-104-119 gateway.

 

This gateway may be set up to do the following:

OPC UA Client and SNMP Client : This gateway will connect to a third-party OPC UA server and read or write tags. It will, however, be a SNMP client that can receive and write data from a SNMP server.

When you have SNMP -based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC UA tags on a regular basis and write the values to a SNMP server device.

 

OPC UA Client and SNMP Server: The most frequent form of operation is using an OPC UA client and a SNMP server. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on SNMP .

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on SNMP .

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this SNMP data (and hence have access to the OPC UA data via the gateway). OPC UA tags may also be written from the SNMP side. As a result, the BAS/BMS system can use the gateway to set values on the OPC UA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

SNMP-OPC-UA

 

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.

 

PG-103-119

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC UA – BACnet IP Gateway (PG-103-119) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

BACnet IP and OPC UA (client only) protocols are supported by the PG-102-119 gateway.

 

This gateway may be set up to do the following:

OPC UA Client and BACnet IP Client : This gateway will connect to a third-party OPC UA server and read or write tags. It will, however, be a BACnet client that can receive and write data from a BACnet server.

When you have BACnet IP -based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC UA tags on a regular basis and write the values to a BACnet server device.

 

OPC UA Client and BACnet IP Server: The most frequent form of operation is using an OPC UA client and a BACnet IP server. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on BACnet IP .

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on BACnet IP .

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this BACnet data (and hence have access to the OPC UA data via the gateway). OPC UA tags may also be written from the BACnet side. As a result, the BAS/BMS system can use the gateway to set values on the OPC UA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

BACnet-IP-OPC-UA

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.
  • Support for BACnet COV for quick data transfer while lowering BACnet network load.

PG-102-119

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC UA – BACnet MSTP Gateway (PG-102-119) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

BACnet MSTP and OPC UA (client only) protocols are supported by the PG-102-119 gateway.

 

This gateway may be set up to do the following:

OPC UA Client and BACnet MSTP Client : This gateway will connect to a third-party OPC UA server and read or write tags. It will, however, be a BACnet client that can receive and write data from a BACnet server.

When you have BACnet MSTP-based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC UA tags on a regular basis and write the values to a BACnet server device.

 

OPC UA Client and BACnet MSTP Server: The most frequent form of operation is using an OPC UA client and a BACnet MSTP server. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on BACnet MSTP.

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on BACnet MSTP.

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this BACnet data (and hence have access to the OPC UA data via the gateway). OPC UA tags may also be written from the BACnet side. As a result, the BAS/BMS system can use the gateway to set values on the OPC UA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

BACnet-MSTP-OPC-UA

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.
  • Support for BACnet COV for quick data transfer while lowering BACnet network load.

 

PG-101-119

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC UA – Modbus TCP Gateway (PG-101-119) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

Modbus TCP and OPC UA (client only) protocols are supported by the PG-101-119 gateway.

 

This gateway may be set up to do the following:

OPC UA Client and Modbus TCP Client: This gateway will connect to an OPC UA server hosted by a third party and read or write tags. It will, however, be a Modbus client that can receive and write data from a Modbus server.

When you have Modbus TCP-based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC UA tags on a regular basis and write the values to a Modbus server device.

 

OPC UA Client and Modbus TCP server: This is most likely the most popular operating mode. In this mode, the gateway is set up to read OPC UA tags and broadcast them as a server over Modbus TCP.

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this Modbus data (and hence have access to the OPC UA data via the gateway). OPC UA tags may also be written from the Modbus side. As a result, the BAS/BMS system can use the gateway to set values on the OPC UA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

Modbus-TCP_IP-OPC-UA Proto

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.

 

PG-100-119

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

OPC UA – Modbus RTU Gateway (PG-100-119) Solutions is a powerful, excellent, fully flexible, and productive Building & Industrial Automation gateway that allows integrators to easily connect devices to networks in commercial buildings and industrial facilities.

Modbus RTU and OPC UA (client only) protocols are supported by the PG-100-119 gateway.

 

This gateway may be set up to do the following:

OPC UA Client and Modbus RTU Client : This gateway will connect to a third-party OPC UA server and read or write tags. It will, however, be a Modbus client that can receive and write data from a Modbus server.

When you have Modbus RTU-based server devices and require a way to read and write values to your OPC server, this mode comes in handy. Alternatively, you may wish to read OPC UA tags on a regular basis and write the values to a Modbus server device.

 

OPC UA Client and Modbus RTU Server: The most frequent form of operation is using an OPC UA client and a Modbus RTU server. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on Modbus RTU.

This is most likely the most popular operating mode. In this mode, the gateway is set to read OPC UA tags and broadcast them as a server on Modbus RTU.

As a result, a third-party building automation/management system (BAS/BMS) may now read all of this Modbus data (and hence have access to the OPC UA data via the gateway). OPC UA tags may also be written from the Modbus side. As a result, the BAS/BMS system can use the gateway to set values on the OPC UA server.

With its robust set of features, the Gateway has benefited system integrators all around the world. The gateway also runs the same protocol conversion software on a productive and cost-effective platform, backed by the same experience, engineering skill, and technically proven support that integrators have come to expect from this Gateway.

 

Modbus-RTU-OPC-UA

Features:

  • In the standard version, you may interface up to 1000 points (upgrades to higher points can be purchased).
  • DIN rail attachment.

 

 

 

FM-232-FO-P2M

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

232-FO-P2S

Product Description

The RS-232 fiber optic modems use the most advanced digital technologies to provide excellent repeatable performance for today’s data systems. It supports transmission of one bi-directional data channel over one multimode or single mode optical fiber. RS232, RS422 and RS485 standards are fully supported. The plug-and-play design ensures ease of installation with no electrical or optical adjustment needed. LED indicators are provided to show the operational status of the unit clearly. The series is available in compact wall mount or 2U chassis card. The RS-232 Series converter is equipped with a multiple interface circuit that can handle RS-232 serial interfaces and multi-mode or single mode fiber. RS-232 converters are used to extend serial transmission distance up to 2 km (multi-mode fiber) or up to 20-100km (single mode fiber)..Auto Baud Rate Detection The RS-232 Series incorporates a method for automatically detecting the serial signal baud rate by hardware. This is an extremely convenient feature for the user. Even if a device’s baud rate is changed, the signal will still be transmitted through the RS-232 to fiber converter without any problem.

Product Features

  • Single or dual redundant power supply
  • Multimode and single mode solutions
  • Switchable 120Ω termination and biasing
  • LED indicators provide quick diagnosis of all important system parameters
  • Up to 14 units in a 2U chassis
  • Compact and 2U chassis card configuration

Specification

RS-232
Data Formats RS232,RS422,RS485
RS232 Data Rate 115.2kbps
RS422/485 Data Rate 512kbps or 1Mkbps
Bit Error Rate <1 x10-12
Connectors
Data DB9
Fiber ST, SC or FC (ST fitted as standard)
Environmental
Operating Temperature -30C—+70C
Storage Temperature -40C—+90C
Operating Humidity 0-95%
MTBF >100,000 Hours
Optical
Fiber Multi mode or Single mode
Wavelength MM:850nm,SM:1310nm
Number of fibers 2 or 1(WDM,Bi-Di)
Power
Power Input AC 220V 110v or DC+110V,+5V,+12V,+24V,+48V Option
Mechanical
Dimensions 43(W)×88.5(D)×124.5(H) DIN Rail

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-232-FO-P2M Point to point Link,Dual Fiber, 2km 2 Multi mode ST/SC/FC
FM-232-FO-P2S Point to point Link,Dual Fiber, 20km 2 Single mode ST/SC/FC

FM-232-FO-P2S

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

232-FO-P2S

Product Description

The RS-232 fiber optic modems use the most advanced digital technologies to provide excellent repeatable performance for today’s data systems. It supports transmission of one bi-directional data channel over one multimode or single mode optical fiber. RS232, RS422 and RS485 standards are fully supported. The plug-and-play design ensures ease of installation with no electrical or optical adjustment needed. LED indicators are provided to show the operational status of the unit clearly. The series is available in compact wall mount or 2U chassis card. The RS-232 Series converter is equipped with a multiple interface circuit that can handle RS-232 serial interfaces and multi-mode or single mode fiber. RS-232 converters are used to extend serial transmission distance up to 2 km (multi-mode fiber) or up to 20-100km (single mode fiber)..Auto Baud Rate Detection The RS-232 Series incorporates a method for automatically detecting the serial signal baud rate by hardware. This is an extremely convenient feature for the user. Even if a device’s baud rate is changed, the signal will still be transmitted through the RS-232 to fiber converter without any problem.

Product Features

  • Single or dual redundant power supply
  • Multimode and single mode solutions
  • Switchable 120Ω termination and biasing
  • LED indicators provide quick diagnosis of all important system parameters
  • Up to 14 units in a 2U chassis
  • Compact and 2U chassis card configuration

Specification

RS-232
Data Formats RS232,RS422,RS485
RS232 Data Rate 115.2kbps
RS422/485 Data Rate 512kbps or 1Mkbps
Bit Error Rate <1 x10-12
Connectors
Data DB9
Fiber ST, SC or FC (ST fitted as standard)
Environmental
Operating Temperature -30C—+70C
Storage Temperature -40C—+90C
Operating Humidity 0-95%
MTBF >100,000 Hours
Optical
Fiber Multi mode or Single mode
Wavelength MM:850nm,SM:1310nm
Number of fibers 2 or 1(WDM,Bi-Di)
Power
Power Input AC 220V 110v or DC+110V,+5V,+12V,+24V,+48V Option
Mechanical
Dimensions 43(W)×88.5(D)×124.5(H) DIN Rail

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-232-FO-P2M Point to point Link,Dual Fiber, 2km 2 Multi mode ST/SC/FC
FM-232-FO-P2S Point to point Link,Dual Fiber, 20km 2 Single mode ST/SC/FC

FM-232-FO-M4M

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

FM-232-FO-M4M

Product Description

The RS-232 Multi-Drop Bus Fiber Optic Modem series products provide an optical bus network for RS-232, RS-422 or RS-485 data interfaces over a pair of multi mode or single mode optical fibers. The Terminal module units operate as the end or terminal points and provide an electrical connection and a two fiber optical connection. The Repeater module units act as in-line repeater stations and provide a single electrical connection and two optical connections, one upstream and one down stream . This series is available in either wall mount, DIN rail or 2U chassis card configurations.

Product Features

  • Multi protocol data interface
  • Switchable termination and biasing
  • Multi mode and Single mode
  • Single or dual redundant power supply
  • 5 years warranty

Specification

RS-232
Data Formats RS232,RS422,RS485
RS232 Data Rate 115.2kbps
RS422/485 Data Rate 512kbps
Bit Error Rate <1 x10-12
Connectors
Data DB9
Fiber ST, SC or FC (ST fitted as standard)
Environmental
Operating Temperature -30C—+70C
Storage Temperature -40C—+90C
Operating Humidity 0-95%
MTBF >100,000 Hours
Optical
Fiber Multi mode or single mode
Wavelength MM:850nm,SM:1310nm
Number of fibers 4 or 2(WDM,Bi-Di)
Power
Power Input AC 220V 110v or DC+110V ,+5V ,+12V ,+24V, +48V Option
Mechanical
Dimensions 43(W)×88.5(D)×124.5(H)mm DIN Rail

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-232-FO-M4M Multi Drop Link,4 Fiber, 2km 4 Multi mode ST/SC/FC
FM-232-FO-M4S Multi Drop Link,4 Fiber, 20km 4 Single mode ST/SC/FC

FM-232-FO-M4S

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

232-FO-M4S

Product Description

The RS-232 Multi-Drop Bus Fiber Optic Modem series products provide an optical bus network for RS-232, RS-422 or RS-485 data interfaces over a pair of multi mode or single mode optical fibers. The Terminal module units operate as the end or terminal points and provide an electrical connection and a two fiber optical connection. The Repeater module units act as in-line repeater stations and provide a single electrical connection and two optical connections, one upstream and one down stream . This series is available in either wall mount, DIN rail or 2U chassis card configurations.

Product Features

  • Multi protocol data interface
  • Switchable termination and biasing
  • Multi mode and Single mode
  • Single or dual redundant power supply
  • 5 years warranty

Specification

RS-232
Data Formats RS232,RS422,RS485
RS232 Data Rate 115.2kbps
RS422/485 Data Rate 512kbps
Bit Error Rate <1 x10-12
Connectors
Data DB9
Fiber ST, SC or FC (ST fitted as standard)
Environmental
Operating Temperature -30C—+70C
Storage Temperature -40C—+90C
Operating Humidity 0-95%
MTBF >100,000 Hours
Optical
Fiber Multi mode or single mode
Wavelength MM:850nm,SM:1310nm
Number of fibers 4 or 2(WDM,Bi-Di)
Power
Power Input AC 220V 110v or DC+110V ,+5V ,+12V ,+24V, +48V Option
Mechanical
Dimensions 43(W)×88.5(D)×124.5(H)mm DIN Rail

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-232-FO-M4M Multi Drop Link,4 Fiber, 2km 4 Multi mode ST/SC/FC
FM-232-FO-M4S Multi Drop Link,4 Fiber, 20km 4 Single mode ST/SC/FC

FM-485-FO-P2M

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

485-FO-P2M

Product Description

The RS-485 fiber optic modem(Point to point) use the most advanced digital technologies to provide excellent repeatable performance for today’s data systems. It supports transmission of one bi-directional data channel over one multimode or single mode optical fiber. RS232, RS422 and RS485 standards are fully supported. The plug-and-play design ensures ease of installation with no electrical or optical adjustment needed. LED indicators are provided to show the operational status of the unit clearly. The series is available in compact wall mount or 2U chassis card. The RS-485 Series converter is equipped with a multiple interface circuit that can handle RS-485 serial interfaces and multi-mode or single mode fiber. RS-485 fiber converters are used to extend serial transmission distance up to 2 km (multi-mode fiber) or up to 20-100km (single mode fiber). .Auto Baud Rate Detection The RS-485 Series incorporates a method for automatically detecting the serial signal baud rate by hardware. This is an extremely convenient feature for the user. Even if a device’s baud rate is changed, the signal will still be transmitted through the RS-485 to fiber converter without any problem.

Product Features

  • Single or dual redundant power supply
  • Multimode and single mode solutions
  • Switchable 120Ω termination and biasing
  • LED indicators provide quick diagnosis of all important system parameters
  • Up to 14 units in a 2U chassis
  • Compact and 2U chassis card configuration

Specification

RS-485
Data Formats RS232,RS422,RS485
RS232 Data Rate 115.2kbps
RS422/485 Data Rate 512kbps
Bit Error Rate <1 x 10-12
Connectors
Data Screw Block Terminal
Fiber ST, SC or FC (ST fitted as standard)
Environmental
Operating Temperature -30C—+70C
Storage Temperature -40C—+90C
Operating Humidity 0-95%
MTBF >100,000 Hours
Optical
Fiber Multi mode or single mode
Wavelength MM:850nm,SM:1310nm
Number of fibers 2 or 1(WDM, Bi-Di)
Power
Power Input AC 220V 110v or DC+110V ,+5V ,+12V ,+24V, +48V Option
Mechanical
Dimensions 43(W)×88.5(D)×124.5(H)mm DIN Rail

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-485-FO-P2M Point to point Link,Dual Fiber, 2km 2 Multi mode ST/SC/FC
FM-485-FO-P2S Point to point Link,Dual Fiber, 20km 2 Single mode ST/SC/FC

Enclosure

LED Indicators:

POW: Power Supply                          On if Power input is OK

TXD: The Transmit Fibre Link          Flashing if there is activity

RXD: The Receive Fibre Link           Flashing if there is activity

Data Input
D+: Connect RS-485+ or Line A
D-: Connect RS-485+ or Line B
GND: GND of RS-485

V-: DC24V+

V+: DC24V-

GND: GND of DC

Fibre Optic Connectors

FTX: Transmitter (Fibre Optic ST)

FRX: Receiver (Fibre Optic ST)

Install Methods

  • Switch off all power supply before installation.
  • Connect the local “FTX” Fiber Optic to the remote “FRX” Fiber Optic, the local “FRX” to the remote “FTX”. And ensure that fiber is properly aligned to the receiving connector.
  • Connect the “D+” Data of the Profibus+ and the “T–” Data to the Profibus-. Then screw down the bolt.
  • On the bottom of the converter, there is a DIP Switch., When the D2 is “ON”,it’s connected to 120 Ohm terminal resistance.

 

DIP Switch setup table:

DIP Switch pin name D1 D2 D3
Setup State OFF OFF OFF

120 ohm Terminal Resistance

DIP Switch pin name D1 D2 D3
Setup State OFF ON OFF

Install Applications

Dimensions (mm)

FM-485-FO-P2S

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

485-FO-P2S

Product Description

The RS-485 fiber optic modem(Point to point) use the most advanced digital technologies to provide excellent repeatable performance for today’s data systems. It supports transmission of one bi-directional data channel over one multimode or single mode optical fiber. RS232, RS422 and RS485 standards are fully supported. The plug-and-play design ensures ease of installation with no electrical or optical adjustment needed. LED indicators are provided to show the operational status of the unit clearly. The series is available in compact wall mount or 2U chassis card. The RS-485 Series converter is equipped with a multiple interface circuit that can handle RS-485 serial interfaces and multi-mode or single mode fiber. RS-485 fiber converters are used to extend serial transmission distance up to 2 km (multi-mode fiber) or up to 20-100km (single mode fiber). .Auto Baud Rate Detection The RS-485 Series incorporates a method for automatically detecting the serial signal baud rate by hardware. This is an extremely convenient feature for the user. Even if a device’s baud rate is changed, the signal will still be transmitted through the RS-485 to fiber converter without any problem.

Product Features

  • Single or dual redundant power supply
  • Multimode and single mode solutions
  • Switchable 120Ω termination and biasing
  • LED indicators provide quick diagnosis of all important system parameters
  • Up to 14 units in a 2U chassis
  • Compact and 2U chassis card configuration

Specification

RS-485
Data Formats RS232,RS422,RS485
RS232 Data Rate 115.2kbps
RS422/485 Data Rate 512kbps
Bit Error Rate <1 x 10-12
Connectors
Data Screw Block Terminal
Fiber ST, SC or FC (ST fitted as standard)
Environmental
Operating Temperature -30C—+70C
Storage Temperature -40C—+90C
Operating Humidity 0-95%
MTBF >100,000 Hours
Optical
Fiber Multi mode or single mode
Wavelength MM:850nm,SM:1310nm
Number of fibers 2 or 1(WDM, Bi-Di)
Power
Power Input AC 220V 110v or DC+110V ,+5V ,+12V ,+24V, +48V Option
Mechanical
Dimensions 43(W)×88.5(D)×124.5(H)mm DIN Rail

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-485-FO-P2M Point to point Link,Dual Fiber, 2km 2 Multi mode ST/SC/FC
FM-485-FO-P2S Point to point Link,Dual Fiber, 20km 2 Single mode ST/SC/FC

Enclosure

LED Indicators:

POW: Power Supply                          On if Power input is OK

TXD: The Transmit Fibre Link          Flashing if there is activity

RXD: The Receive Fibre Link           Flashing if there is activity

Data Input
D+: Connect RS-485+ or Line A
D-: Connect RS-485+ or Line B
GND: GND of RS-485

V-: DC24V+

V+: DC24V-

GND: GND of DC

Fibre Optic Connectors

FTX: Transmitter (Fibre Optic ST)

FRX: Receiver (Fibre Optic ST)

Install Methods

  • Switch off all power supply before installation.
  • Connect the local “FTX” Fiber Optic to the remote “FRX” Fiber Optic, the local “FRX” to the remote “FTX”. And ensure that fiber is properly aligned to the receiving connector.
  • Connect the “D+” Data of the Profibus+ and the “T–” Data to the Profibus-. Then screw down the bolt.
  • On the bottom of the converter, there is a DIP Switch., When the D2 is “ON”,it’s connected to 120 Ohm terminal resistance.

DIP Switch setup table:

DIP Switch pin name D1 D2 D3
Setup State OFF OFF OFF

120 ohm Terminal Resistance

DIP Switch pin name D1 D2 D3
Setup State OFF ON OFF

Install Applications

Dimensions (mm)

FM-485-FO-M4M

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

485-FO-M4M

Product Description

The Multi-Drop Bus Fiber Optic Modem series products provide an optical bus network for RS-232, RS-422 or RS-485 data interfaces over a pair of multi mode or single mode optical fibers. The Terminal module units operate as the end or terminal points and provide an electrical connection and a two fiber optical connection. The Repeater module units act as in-line repeater stations and provide a single electrical connection and two optical connections, one upstream and one downstream . This series is available in either wall mount, DIN rail or 2U chassis card configurations.

Product Features

  • Multi protocol data interface
  • Switchable termination and biasing
  • Multi mode and single mode
  • Single or dual redundant power supply
  • 5 years warranty

Specification

RS-485
Data Formats RS232,RS422,RS485
RS232 Data Rate 115.2kbps
RS422/485 Data Rate 512kbps
Bit Error Rate <1 x 10-12
Connectors
Data Screw Block Terminal
Fiber ST, SC or FC (ST fitted as standard)
Environmental
Operating Temperature -30C—+70C
Storage Temperature -40C—+90C
Operating Humidity 0-95%
MTBF >100,000 Hours
Optical
Fiber Multi mode or single mode
Wavelength MM:850nm,SM:1310nm
Number of fibers 4 or 2(WDM,Bi-Di)
Power
Power Input AC 220V 110v or DC+110V ,+5V ,+12V ,+24V, +48V Option
Mechanical
Dimensions 43(W)×88.5(D)×124.5(H)mm DIN Rail

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-485-FO-M4M Multi Drop Link,4 Fiber, 2km 4 Multi mode ST/SC/FC
FM-485-FO-M4S Multi Drop Link,4 Fiber, 20km 4 Single mode ST/SC/FC

Enclosure

LED Indicators:POW:

Power Supply                                               On if Power input is OK

ACT: RS-485 Data transmit/receive          Flashing if there is activity

TX1: The 1 Channel Transmit Fibre Link     Flashing if there is activity

RX1: The 1 Channel Receive Fibre Link      Flashing if there is activity

TX2: The 2 Channel Transmit Fibre Link    Flashing if there is activity

RX2: The 2 Channel Transmit Fibre Link    Flashing if there is activity

Data Input
D+: Connect RS-485+ or Line A
D-: Connect RS-485+ or Line B
GND: GND of RS-485

V-: DC24V+

V+: DC24V-

GND: No Connection

Fiber Connectors

FTX1:         Fiber Optical ST of the 1 channel ( transmit & receive )

FRX1:         NONE

FTX2:         Fiber Optical ST of the 2 channel ( transmit & receive)

FRX2:         NONE

Caution

  • Switch off all power supply before installation
  • Ensure fiber is properly aligned to the receiving connector
  • Do NOT stare at the fiber core
  • On the bottom of the product, there is a DIP Switch, the users should setup the DIP Switch according to the selecting mode.

DIP Switch setup table

DIP D1 D2 D3
STATE OFF Terminal

Resistance

(120Ω)

 OFF

Install Applications

Figure 1 Multi-Drop Bus

Figure 2 Point to Point (Trunk Line)

Dimensions (mm)

FM-485-FO-M4S

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

485-FO-M4S

Product Description

The Multi-Drop Bus Fiber Optic Modem series products provide an optical bus network for RS-232, RS-422 or RS-485 data interfaces over a pair of multi mode or single mode optical fibers. The Terminal module units operate as the end or terminal points and provide an electrical connection and a two fiber optical connection. The Repeater module units act as in-line repeater stations and provide a single electrical connection and two optical connections, one upstream and one downstream . This series is available in either wall mount, DIN rail or 2U chassis card configurations.

Specification

RS-485
Data Formats RS232,RS422,RS485
RS232 Data Rate 115.2kbps
RS422/485 Data Rate 512kbps
Bit Error Rate <1 x 10-12
Connectors
Data Screw Block Terminal
Fiber ST, SC or FC (ST fitted as standard)
Environmental
Operating Temperature -30C—+70C
Storage Temperature -40C—+90C
Operating Humidity 0-95%
MTBF >100,000 Hours
Optical
Fiber Multi mode or single mode
Wavelength MM:850nm,SM:1310nm
Number of fibers 4 or 2(WDM,Bi-Di)
Power
Power Input AC 220V 110v or DC+110V ,+5V ,+12V ,+24V, +48V Option
Mechanical
Dimensions 43(W)×88.5(D)×124.5(H)mm DIN Rail

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-485-FO-M4M Multi Drop Link,4 Fiber, 2km 4 Multi mode ST/SC/FC
FM-485-FO-M4S Multi Drop Link,4 Fiber, 20km 4 Single mode ST/SC/FC

Enclosure

LED Indicators:POW:

Power Supply                                               On if Power input is OK

ACT: RS-485 Data transmit/receive          Flashing if there is activity

TX1: The 1 Channel Transmit Fibre Link     Flashing if there is activity

RX1: The 1 Channel Receive Fibre Link      Flashing if there is activity

TX2: The 2 Channel Transmit Fibre Link    Flashing if there is activity

RX2: The 2 Channel Transmit Fibre Link    Flashing if there is activity

Data Input
D+: Connect RS-485+ or Line A
D-: Connect RS-485+ or Line B
GND: GND of RS-485

V-: DC24V+

V+: DC24V-

GND: No Connection

Fiber Connectors

FTX1:         Fiber Optical ST of the 1 channel ( transmit & receive )

FRX1:         NONE

FTX2:         Fiber Optical ST of the 2 channel ( transmit & receive)

FRX2:         NONE

Caution

  • Switch off all power supply before installation
  • Ensure fiber is properly aligned to the receiving connector
  • Do NOT stare at the fiber core
  • On the bottom of the product, there is a DIP Switch, the users should setup the DIP Switch according to the selecting mode.

DIP Switch setup table

DIP D1 D2 D3
STATE OFF Terminal

Resistance

(120Ω)

 OFF

Install Applications

Figure 1 Multi-Drop Bus

Figure 2 Point to Point (Trunk Line)

Dimensions (mm)

CAN-FO-P2M

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

Product Description

The CAN bus to fiber optic switch provide an optical point-to-point or bus network connection for CAN bus data interfaces on one or two, multimode or single mode optical fibers. The CAN bus fiber optic converter has 1 CAN port and 1 fiber optic port, CAN port is configurable via software.The Can bus series units support both CAN 1.0 and CAN 2.0B CAN standards and are transparent to all high level protocols.It can solve the problem of CAN bus’s cascading problems,it can transmit 1MB data to 20km and the maximum is 6500 frames when it’s up to 20km distance,so it the most advanced CAN bus fiber optic converter.

Product Features

  • Up to 1Mbps data rate (20km when it’s 1MB, New Technology)
  • Up to 6500 frames/second
  • Software Configurable
  • Multi mode and Single mode
  • Single fiber solution supported
  • 5 year warranty

Specification

CAN BUS
Data Formats CAN 1.0, CAN 2.0, Device Net
CAN Data Rate 0-1 Mbps
Bit Error Rate <1 x 10-12
Connectors
Data Screw Block Terminal
Fiber ST, SC or FC (ST fitted as standard)
Environmental
Operating Temperature -30C—+70C
Storage Temperature -40C—+85C
Operating Humidity 0-95%
MTBF >100,000 Hours
Optical
Fiber Multi mode or Single mode
Wavelength MM:850/1310nm, SM:1310/1550nm
Number of fibers 2 or 1
Power
Power Input +9 to +40V DC
Mechanical
Dimensions 156(W)x108(D)x33.6(H)mm Wall Mount & DIN Rail

Model Selection

Model Number Description Port No. Fiber Mode Fiber Connector
HFB-CAN-FO-P2S Fiber Optic Converter,Point to Point Link,Dual Fiber, 2km,DIN Rail Mount 1CAN+2 FO Single mode ST/SC/FC
HFB-CAN-FO-P2M Fiber Optic Converter,Point to Point Link,Dual Fiber, 20km 1CAN+2 FO Multi mode ST/SC/FC

Enclosure

Panel 1

LED

LED No LED For LED Name LED Function
1 CAN0 TX Transmitting
2 RX Receiving
3 Error Failure
1 Fiber0 TX Transmitting
2 RX Receiving
3 Error Failure

Others

Name Relevant Function Remarks
Baudrate CAN0 Rotary button Configure baud rate by button,fast configuration
RS232 CAN0 Console port Configure baud rate by software on computer
VCC V+ Power input DC 9~40V, With SPD,RCP,OCP
GND V- Power input DC 9~40V,With SPD,RCP,OCP

Panel 2

Port Name Relevant Function Remarks
SYS System LED
TX Fiber0 Transmit Fiber optic connector TX
RX Fiber0 Receive Fiber optic connector RX
CANH CAN0 CANH CAN copper port
CANL CAN0 CANL CAN copper port
R+ CAN0 R+ Terminal resistance Not necessary in normal condition
FG CAN0 Grounding Not necessary
R- CAN0 R- Terminal resistance Not necessary in normal condition
SW0-SW2  DIP Switch button Button 1 on for 120Ohm resistance

Installation Methods

  • Switch off all power supply before installation.
  • Connect the local “FTX” Fiber Optic to the remote “FRX” Fiber Optic, the local “FRX” to the remote “FTX”. And ensure that fiber is properly aligned to the receiving connector.
  • Connect the “D+” Data of the Profibus+ and the “T–” Data to the Profibus-. Then screw down the bolt.
  • On the bottom of the converter, there is a DIP Switch., When the D2 is “ON”,it’s connected to 120 Ohm terminal resistance.

 

DIP Switch setup table

DIP Switch pin name D1 D2 D3
Setup State OFF OFF OFF

120 ohm Terminal Resistance

DIP Switch pin name D1 D2 D3
Setup State OFF ON OFF

Baud rate rotary switch button setup table

B0 Button Position 9 8 7 6 5 4 3 2 1 0
CAN Baud Rate 80Kbps 100Kbps 125Kbps 200Kbps 250Kbps 400Kbps 500Kbps 666Kbps 800Kbps 1000Kbps
A B C D E F
50Kbps 40Kbps 20Kbps 10Kbps 5Kbps configuration

Note: When the B0 is switched to F position, you can configure the baud rate through the serial DB9 port.

Configure the baud rate by software

Switch the “B0” button to F position and connect the straight line(NOT cross line) to the console port(DB9) and the other end of the line to the computer.

1.Open CANConfig and click“CAN FIB-100PT”,you will see 3 options: Basic Info,Baudrate and

Filter.

2. Software Configuration

  1. Open RS232：Communicate with the serial RS232.
  2. Read Parameter：Read all parameters of the device and display them.
  3. Write Parameter：Write all parameters into the device.These parameters will be stored to the flash and read them automatically when powers on.

3. Device Parameters

3.1 Basic Info

Click the “Open RS232” and read out all information by clicking “Read Parameter” button.The “Basic info” option contains the vendor ID,device type,device code,hardware version,software version and serial numbers.

3.2 Baudrate

“Baudrate” is for setting up the baud rate of all channels of the device.When the rotary button is switched to”F” position,you can configure the baud rate on it.See the below figure and baud rate table:

Common standard baud rate’s BTR0 and BTR1 values

CAN Baud rate BTR0(Time0-SJA1000) BTR1(Time1-SJA1000)
5Kbps 0xBF 0xFF
10Kbps 0x31 0x1C
20Kbps 0x18 0x1C
40Kbps 0x87 0xFF
50Kbps 0x09 0x1C
80Kbps 0x83 0Xff
100Kbps 0x04 0x1C
125Kbps 0x03 0x1C
200Kbps 0x81 0xFA
250Kbps 0x01 0x1C
400Kbps 0x80 0xFA
500Kbps 0x00 0x1C
666Kbps 0x80 0xB6
800Kbps 0x00 0x16
1000Kbps 0x00 0x14

How to use the filter function：

  1. Select the channel that needs filter function from the sub list of“Port”.
  2. Select “Filter Enable”and you can revise the content of the filter.
  3. Select the frame type(Standard or extended frame types) from the “Frame Type” .
  4. On “Start ID”and“End ID” rows，please fill in the ID of the frame that you want to filter.The standard frame range is 0~2047（0x7FF）and the extended frame range is 0~536870911 (0x1FFFFFFF).
  5. After setting up the frame’s filter parameters,please click“Write Parameter” button and write the router parameters into the device,then it’s valid.

Installation Applications

Dimensions (mm)

FM-Lon-FO-P2M

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

Product Description

The LonWorks Fiber Optic Modem is a Field bus Control System (FCS). Our Fiber Optic Modem uses the fiber cable as its transmission medium and utilizes Optical Fiber modulation/demodulation technology to changes the electric medium into a light medium transmission. The LonWorks Fiber Optic Modem product eliminates many of the disadvantages of copper cable. Examples of these disadvantages are EMI/RFI, ground loops (electrical isolation with fiber), high attenuation (high signal loss), short transmission distance between nodes of a system, and potential lightning damage. The LonWorks Fiber Optic Modem can be widely used, such as Industrial Controls, Intelligent Transportation Systems (ITS), Industrial Networking, Supervisory Control and Data (SCADA) and so on.

Specification

LonWorks
Connectors Terminal
Standard LonWorks(LonTalk)
Data Rate 78.6Kbps
Extended Distance 2.7Km
Optical
Number of Fibers 2
Wavelength 850/1310nm
Fiber Type 62.5/125µm(MM), 9/125µm(SM)
Distance 0~3KM or 0-20 KM
Connector Type ST/PC
General
Operating Temperature -30~70˚C / -30 ~ +158ºF
Operating Humidity 0 ~ 95% non-condensing
Mean Time Between Failure (MTBF) > 70,000hrs
Power Supply Adaptor DC24V
Dimensions (W×H×D) 124.5×43×88.5mm

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-Lon-FO-P2M Point to point Link,Dual Fiber, 2Km 2 Multi mode ST/SC/FC
FM-Lon-FO-P2S Point to point Link, Dual Fiber, 20Km 2 Single mode ST/SC/FC

Enclosure

LED Indicators:

POW: Power Supply                      On if Power input is OK

TXD: The Transmit Fibre Link       Flashing if there is activity

RXD: The Receive Fibre Link        Flashing if there is activity

Data Input

D+: Connect       LON A

D-: Connect        LON B

GND: NONE

V-: Connect DC24V power supply “-“

V+: Connect DC24V power supply “+”

GND: Power Ground

Fibre Optic Connectors

FTX: Transmitter (Fibre Optic ST)

FRX: Receiver (Fibre Optic ST)

Installation Methods

  • Switch off all power supply before installation.
  • Connect the local “FTX” Fiber Optic to the remote “FRX” Fiber Optic, the local “FRX” to the remote “FTX”. And ensure that fiber is properly aligned to the receiving connector.
  • Connect the “D+” Data of the Profibus+ and the “T–” Data to the Profibus-. Then screw down the bolt.
  • On the bottom of the converter, there is a DIP Switch., When the D2 is “ON”,it’s connected to 120 Ohm terminal resistance.

 

DIP Switch setup table:

DIP Switch pin name D1 D2 D3
Setup State OFF OFF OFF

120 ohm Terminal Resistance

DIP Switch pin name D1 D2 D3
Setup State OFF ON OFF

Installation Applications

Dimensions (mm)

FM-Lon-FO-P2S

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

Product Description

The LonWorks Fiber Optic Modem is a Field bus Control System (FCS). Our Fiber Optic Modem uses the fiber cable as its transmission medium and utilizes Optical Fiber modulation/demodulation technology to changes the electric medium into a light medium transmission. The LonWorks Fiber Optic Modem product eliminates many of the disadvantages of copper cable. Examples of these disadvantages are EMI/RFI, ground loops (electrical isolation with fiber), high attenuation (high signal loss), short transmission distance between nodes of a system, and potential lightning damage. The LonWorks Fiber Optic Modem can be widely used, such as Industrial Controls, Intelligent Transportation Systems (ITS), Industrial Networking, Supervisory Control and Data (SCADA) and so on.

Specification

LonWorks
Connectors Terminal
Standard LonWorks(LonTalk)
Data Rate 78.6Kbps
Extended Distance 2.7Km
Optical
Number of Fibers 2
Wavelength 850/1310nm
Fiber Type 62.5/125µm(MM), 9/125µm(SM)
Distance 0~3KM or 0-20 KM
Connector Type ST/PC
General
Operating Temperature -30~70˚C / -30 ~ +158ºF
Operating Humidity 0 ~ 95% non-condensing
Mean Time Between Failure (MTBF) > 70,000hrs
Power Supply Adaptor DC24V
Dimensions (W×H×D) 124.5×43×88.5mm

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-Lon-FO-P2M Point to point Link,Dual Fiber, 2Km 2 Multi mode ST/SC/FC
FM-Lon-FO-P2S Point to point Link, Dual Fiber, 20Km 2 Single mode ST/SC/FC

Enclosure

LED Indicators:

POW: Power Supply                             On if Power input is OK

TXD: The Transmit Fibre Link              Flashing if there is activity

RXD: The Receive Fibre Link               Flashing if there is activity

Data Input

D+: Connect       LON A

D-: Connect        LON B

GND: NONE

V-: Connect DC24V power supply “-“

V+: Connect DC24V power supply “+”

GND: Power Ground

Fibre Optic Connectors

FTX: Transmitter (Fibre Optic ST)

FRX: Receiver (Fibre Optic ST)

Installation Methods

  • Switch off all power supply before installation.
  • Connect the local “FTX” Fiber Optic to the remote “FRX” Fiber Optic, the local “FRX” to the remote “FTX”. And ensure that fiber is properly aligned to the receiving connector.
  • Connect the “D+” Data of the Profibus+ and the “T–” Data to the Profibus-. Then screw down the bolt.
  • On the bottom of the converter, there is a DIP Switch., When the D2 is “ON”,it’s connected to 120 Ohm terminal resistance.

 

DIP Switch setup table:

DIP Switch pin name D1 D2 D3
Setup State OFF OFF OFF

120 ohm Terminal Resistance

DIP Switch pin name D1 D2 D3
Setup State OFF ON OFF

Installation Applications

Dimensions (mm)

FM-Lon-FO-M4M

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

Product Description

The LonWorks Fiber Optic Modem is a Field bus Control System (FCS). Our Fiber Optic Modem uses the fiber cable as its transmission medium and utilizes Optical Fiber modulation/demodulation technology to changes the electric medium into a light medium transmission. The LonWorks Fiber Optic Modem product eliminates many of the disadvantages of copper cable. Examples of these disadvantages are EMI/RFI, ground loops (electrical isolation with fiber), high attenuation (high signal loss), short transmission distance between nodes of a system, and potential lightning damage. The LonWorks Fiber Optic Modem can be widely used, such as Industrial Controls, Intelligent Transportation Systems (ITS), Industrial Networking, Supervisory Control and Data (SCADA) and so on.

Specification

LonWorks
Connectors Terminal
Standard LonWorks(LonTalk)
Data Rate 78.6Kbps
Extended Distance 0~20Km
Optical
Number of Fibers 2 or 4
Wavelength 850/1310nm
Fiber Type 62.5/125µm(MM), 9/125µm(SM)
Distance 0 ~ 2Km OR 0-20 Km
Connector Type ST/PC or SC,FC
General
Operating Temperature -30~70˚C / -30 ~ +158ºF
Operating Humidity 0 ~ 95% non-condensing
Mean Time Between Failure (MTBF) > 70,000hrs
Power Supply Adaptor DC24V
Dimensions (W×H×D) 43(W)×124.5(H)×88.5(D)

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-Lon-FO-M4M Multi Drop Bus Link, 4 Fiber, 2 Km 4 Multi mode ST/SC/FC
FM-Lon-FO-M4S Multi Drop Bus Link,4 Fiber, 20 Km 4 Single mode ST/SC/FC

Enclosure

LED Indicators:

POW: Power Supply                                           On if Power input is OK

ACT: LON Data transmit/receive                      Flashing if there is activity

TX1: The 1 Channel Transmit Fibre Link           Flashing if there is activity

RX1: The 1 Channel Receive Fibre Link            Flashing if there is activity

TX2: The 2 Channel Transmit Fibre Link          Flashing if there is activity

RX2: The 2 Channel Transmit Fibre Link          Flashing if there is activity

Data Input

D+: Connect LON+ or Line A

D-: Connect LON- or Line B

V-: Connect DC24V+

V+: Connect DC24V-

GND: No Connection

Fibre Optic Connectors

FTX1:         Single Fiber: Fiber Optical ST of the 1 channel ( transmit & receive )

                    Dual Fiber: Fiber Optical Transmit 1

FRX1:         Single Fiber: NONE

                     Dual Fiber: Fiber Optical receive 1

FTX2:         Single Fiber: Fiber Optical ST of the 2 channel (transmit & receive)

                    Dual Fiber: Fiber Optical transmit 2

FRX2:         Single Fiber: NONE

                     Dual Fiber: Fiber Optical receive 2

Caution

  • Switch off all power supply before installation
  • Ensure fiber is properly aligned to the receiving connector
  • Do NOT stare at the fiber core
  • On the bottom of the product, there is a DIP Switch, the users should setup the DIP Switch according to the selecting mode.

DIP Switch setup table:

DIP D1 D2 D3
STATE OFF Terminal

Resistance

(120Ω)

 OFF

Installation Applications

Dimensions (mm)

CAN-FO-P2S

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

Product Description

The CAN bus to fiber optic switch provide an optical point-to-point or bus network connection for CAN bus data interfaces on one or two, multimode or single mode optical fibers. The CAN bus fiber optic converter has 1 CAN port and 1 fiber optic port, CAN port is configurable via software.The Can bus series units support both CAN 1.0 and CAN 2.0B CAN standards and are transparent to all high level protocols.It can solve the problem of CAN bus’s cascading problems,it can transmit 1MB data to 20km and the maximum is 6500 frames when it’s up to 20km distance,so it the most advanced CAN bus fiber optic converter.

Product Features

  • Up to 1Mbps data rate (20km when it’s 1MB, New Technology)
  • Up to 6500 frames/second
  • Software Configurable
  • Multi mode and Single mode
  • Single fiber solution supported
  • 5 year warranty

Specification

CAN BUS
Data Formats CAN 1.0, CAN 2.0, Device Net
CAN Data Rate 0-1 Mbps
Bit Error Rate <1 x 10-12
Connectors
Data Screw Block Terminal
Fiber ST, SC or FC (ST fitted as standard)
Environmental
Operating Temperature -30C—+70C
Storage Temperature -40C—+85C
Operating Humidity 0-95%
MTBF >100,000 Hours
Optical
Fiber Multi mode or Single mode
Wavelength MM:850/1310nm, SM:1310/1550nm
Number of fibers 2 or 1
Power
Power Input +9 to +40V DC
Mechanical
Dimensions 156(W)x108(D)x33.6(H)mm Wall Mount & DIN Rail

Model Selection

Model Number Description Port No. Fiber Mode Fiber Connector
HFB-CAN-FO-P2S Fiber Optic Converter,Point to Point Link,Dual Fiber, 2km,DIN Rail Mount 1CAN+2 FO Single mode ST/SC/FC
HFB-CAN-FO-P2M Fiber Optic Converter,Point to Point Link,Dual Fiber, 20km 1CAN+2 FO Multi mode ST/SC/FC

Enclosure

Panel 1

LED

LED No LED For LED Name LED Function
1 CAN0 TX Transmitting
2 RX Receiving
3 Error Failure
1 Fiber0 TX Transmitting
2 RX Receiving
3 Error Failure

Others

Name Relevant Function Remarks
Baudrate CAN0 Rotary button Configure baud rate by button,fast configuration
RS232 CAN0 Console port Configure baud rate by software on computer
VCC V+ Power input DC 9~40V, With SPD,RCP,OCP
GND V- Power input DC 9~40V,With SPD,RCP,OCP

Panel 2

Port Name Relevant Function Remarks
SYS System LED
TX Fiber0 Transmit Fiber optic connector TX
RX Fiber0 Receive Fiber optic connector RX
CANH CAN0 CANH CAN copper port
CANL CAN0 CANL CAN copper port
R+ CAN0 R+ Terminal resistance Not necessary in normal condition
FG CAN0 Grounding Not necessary
R- CAN0 R- Terminal resistance Not necessary in normal condition
SW0-SW2  DIP Switch button Button 1 on for 120Ohm resistance

Installation Methods

  • Switch off all power supply before installation.
  • Connect the local “FTX” Fiber Optic to the remote “FRX” Fiber Optic, the local “FRX” to the remote “FTX”. And ensure that fiber is properly aligned to the receiving connector.
  • Connect the “D+” Data of the Profibus+ and the “T–” Data to the Profibus-. Then screw down the bolt.
  • On the bottom of the converter, there is a DIP Switch., When the D2 is “ON”,it’s connected to 120 Ohm terminal resistance.

 

DIP Switch setup table

DIP Switch pin name D1 D2 D3
Setup State OFF OFF OFF

120 ohm Terminal Resistance

DIP Switch pin name D1 D2 D3
Setup State OFF ON OFF

Baud rate rotary switch button setup table

B0 Button Position 9 8 7 6 5 4 3 2 1 0
CAN Baud Rate 80Kbps 100Kbps 125Kbps 200Kbps 250Kbps 400Kbps 500Kbps 666Kbps 800Kbps 1000Kbps
A B C D E F
50Kbps 40Kbps 20Kbps 10Kbps 5Kbps configuration

Note: When the B0 is switched to F position, you can configure the baud rate through the serial DB9 port.

Configure the baud rate by software

Switch the “B0” button to F position and connect the straight line(NOT cross line) to the console port(DB9) and the other end of the line to the computer.

1.Open CANConfig and click“CAN FIB-100PT”,you will see 3 options: Basic Info,Baudrate and

Filter.

2. Software Configuration

  1. Open RS232：Communicate with the serial RS232.
  2. Read Parameter：Read all parameters of the device and display them.
  3. Write Parameter：Write all parameters into the device.These parameters will be stored to the flash and read them automatically when powers on.

3. Device Parameters

3.1 Basic InfoClick the “Open RS232” and read out all information by clicking “Read Parameter” button.The “Basic info” option contains the vendor ID,device type,device code,hardware version,software version and serial numbers.

3.2 Baudrate

“Baudrate” is for setting up the baud rate of all channels of the device.When the rotary button is switched to”F” position,you can configure the baud rate on it.See the below figure and baud rate table

Common standard baud rate’s BTR0 and BTR1 values

CAN Baud rate BTR0(Time0-SJA1000) BTR1(Time1-SJA1000)
5Kbps 0xBF 0xFF
10Kbps 0x31 0x1C
20Kbps 0x18 0x1C
40Kbps 0x87 0xFF
50Kbps 0x09 0x1C
80Kbps 0x83 0Xff
100Kbps 0x04 0x1C
125Kbps 0x03 0x1C
200Kbps 0x81 0xFA
250Kbps 0x01 0x1C
400Kbps 0x80 0xFA
500Kbps 0x00 0x1C
666Kbps 0x80 0xB6
800Kbps 0x00 0x16
1000Kbps 0x00 0x14

How to use the filter function：

  1. Select the channel that needs filter function from the sub list of“Port”.
  2. Select “Filter Enable”and you can revise the content of the filter.
  3. Select the frame type(Standard or extended frame types) from the “Frame Type” .
  4. On “Start ID”and“End ID” rows，please fill in the ID of the frame that you want to filter.The standard frame range is 0~2047（0x7FF）and the extended frame range is 0~536870911 (0x1FFFFFFF).
  5. After setting up the frame’s filter parameters,please click“Write Parameter” button and write the router parameters into the device,then it’s valid.

Installation Applications

Dimensions (mm)

FM-Lon-FO-M4S

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

Product Description

The LonWorks Fiber Optic Modem is a Field bus Control System (FCS). Our Fiber Optic Modem uses the fiber cable as its transmission medium and utilizes Optical Fiber modulation/demodulation technology to changes the electric medium into a light medium transmission. The LonWorks Fiber Optic Modem product eliminates many of the disadvantages of copper cable. Examples of these disadvantages are EMI/RFI, ground loops (electrical isolation with fiber), high attenuation (high signal loss), short transmission distance between nodes of a system, and potential lightning damage. The LonWorks Fiber Optic Modem can be widely used, such as Industrial Controls, Intelligent Transportation Systems (ITS), Industrial Networking, Supervisory Control and Data (SCADA) and so on.

Specification

LonWorks
Connectors Terminal
Standard LonWorks(LonTalk)
Data Rate 78.6Kbps
Extended Distance 0~20Km
Optical
Number of Fibers 2 or 4
Wavelength 850/1310nm
Fiber Type 62.5/125µm(MM), 9/125µm(SM)
Distance 0 ~ 2Km OR 0-20 Km
Connector Type ST/PC or SC,FC
General
Operating Temperature -30~70˚C / -30 ~ +158ºF
Operating Humidity 0 ~ 95% non-condensing
Mean Time Between Failure (MTBF) > 70,000hrs
Power Supply Adaptor DC24V
Dimensions (W×H×D) 43(W)×124.5(H)×88.5(D)

Model Selection

Model Number Description Fiber No. Fiber Mode Fiber Connector
FM-Lon-FO-M4M Multi Drop Bus Link, 4 Fiber, 2 Km 4 Multi mode ST/SC/FC
FM-Lon-FO-M4S Multi Drop Bus Link,4 Fiber, 20 Km 4 Single mode ST/SC/FC

Enclosure

LED Indicators:

POW: Power Supply                                                   On if Power input is OK

ACT: LON Data transmit/receive                              Flashing if there is activity

TX1: The 1 Channel Transmit Fibre Link                   Flashing if there is activity

RX1: The 1 Channel Receive Fibre Link                    Flashing if there is activity

TX2: The 2 Channel Transmit Fibre Link                  Flashing if there is activity

RX2: The 2 Channel Transmit Fibre Link                  Flashing if there is activity

Data Input

D+: Connect LON+ or Line A

D-: Connect LON- or Line B

V-: Connect DC24V+

V+: Connect DC24V-

GND: No Connection

Fibre Optic Connectors

FTX1:         Single Fiber: Fiber Optical ST of the 1 channel ( transmit & receive )

                    Dual Fiber: Fiber Optical Transmit 1

FRX1:         Single Fiber: NONE

                     Dual Fiber: Fiber Optical receive 1

FTX2:         Single Fiber: Fiber Optical ST of the 2 channel (transmit & receive)

                    Dual Fiber: Fiber Optical transmit 2

FRX2:         Single Fiber: NONE

                     Dual Fiber: Fiber Optical receive 2

Caution

  • Switch off all power supply before installation
  • Ensure fiber is properly aligned to the receiving connector
  • Do NOT stare at the fiber core
  • On the bottom of the product, there is a DIP Switch, the users should setup the DIP Switch according to the selecting mode.

DIP Switch setup table:

DIP D1 D2 D3
STATE OFF Terminal

Resistance

(120Ω)

 OFF

Installation Applications

Dimensions (mm)

PG-102-106-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

Outline of Metasys N2 and BACnet MS/TP

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.

Outline of Metasys N2 and BACnet IP

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.

How to configure the PG-102-106-AA 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-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.

PG-103-106-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-103-106-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-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-103-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 site which can provide data output on Metasys N2.
  • The site has a SCADA on BACnet IP that needs the data from Ion Meters on Metasys N2.
  • A direct exchange of data between SCADA and Metasys N2 Controllers is not possible as Metasys N2 Controllers provide data output on Metasys N2 and the SCADA understands BACnet IP 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 BACnet IP is an Ethernet Protocol and hence we need a converter that will help to convert the data from BACnet IP device to Metasys N2 and vice versa.
  • PG-103-106-AA Metasys N2 to BACnet IP 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 provide it on BACnet IP when requested from the SCADA system.

Scenario 2

  • There are several variable frequency drives on the site which provide data output on BACnet IP.
  • The site has a NAE controller on Metasys N2 which needs data from Variable Frequency Drives on BACnet IP.
  • A direct exchange of data between NAE controller and Variable Frequency Drives is not possible as Variable Frequency Drives provide data output on BACnet IP and 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 is a Serial Protocol while BACnet IP is an Ethernet Protocol and hence we need a converter that will help to convert the data from BACnet IP device to Metasys N2 and vice versa.
  • PG-103-106-AA Metasys N2 to BACnet IP converter is an excellent solution for this requirement. This helps the gateway in reading data from the Variable Frequency Drive on BACnet IP and it caches this data internally and then provides it on Metasys N2 when requested from the NAE Controller.

Outline of Metasys N2 and BACnet IP

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 IP

BACnet (Building Automation and Control Network) is a communications protocol that helps the communication between building automation end-devices and building management systems. The BACnet protocol specification like every other protocol specification defines both how data is represented on the network and the services that are used to move data from one BACnet node to another. The specification also tells us about messages that identify data and network nodes such as who-Has, I-Have, Who-Is, and I-Am.

To meet the requirement of the widest possible set of applications BACnet was designed to support several different physical and link layers.

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

How to configure the PG-103-106-AA 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-103-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-103-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-103-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.

PG-100-106-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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.

Outline of Modbus RTU and Metasys N2

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.

How to configure the PG-100-106-AA 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-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.

PG-101-106-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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.

Outline of Modbus TCP and Metasys N2

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.

How to configure the PG-101-106-AA 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-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.

PG-106-104-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-106-104-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-106-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-106-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 Cummins PCC controllers on various diesel Generators the site which provide data output on LonWorks.
  • The site has a Network Automation Engine on Metasys N2 that needs energy data from the Controller.
  • A direct exchange of data between Controllers and Engine is not possible as the Controllers provide data output on LonWorks and an Engine understands Metasys N2 only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and Metasys N2 are Serial based Protocol. Hence, a converter is needed that can convert the data from Metasys N2 device to LonWorks and vice versa.
  • PG-106-104-AA Metasys N2 to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from the PCC controller on LonWorks and it caches this data internally and then provides it on Metasys N2 when requested from the Network Automation Engine.

Scenario 2

  • There are controllers on the other site which provide data output on Metasys N2.
  • The site has a PLC on LonWorks that needs the temperature data from controllers on Metasys N2.
  • A direct exchange of data between controllers and PLC is not possible as the controllers provide data output on Metasys N2 and PLC understands LonWorks only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and Metasys N2 are Serial based Protocol. Hence, a converter is needed that can convert the data from Metasys N2 device to LonWorks and vice versa.
  • PG-106-104-AA Metasys N2 to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from controllers on Metasys N2 and it caches this data internally and then provides it on LonWorks when requested from the PLC.

Outline of Metasys N2 and LonWorks

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.

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, fibre 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.

How to configure the PG-106-105-AC 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-106-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-106-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-106-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.

PG-106-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-106-105-AC gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-106-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-106-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 Cummins PCC controllers on various diesel Generators the site which provide data output on LonWorks.
  • The site has a Network Automation Engine on Metasys N2 that needs energy data from the Controller.
  • A direct exchange of data between Controllers and Engine is not possible as the Controllers provide data output on LonWorks and an Engine understands Metasys N2 only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and Metasys N2 are Serial based Protocol. Hence, a converter is needed that can convert the data from Metasys N2 device to LonWorks and vice versa.
  • PG-106-105-AC Metasys N2 to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from the PCC controller on LonWorks and it caches this data internally and then provides it on Metasys N2 when requested from the Network Automation Engine.

Scenario 2

  • There are controllers on the other site which provide data output on Metasys N2.
  • The site has a PLC on LonWorks that needs the temperature data from controllers on Metasys N2.
  • A direct exchange of data between controllers and PLC is not possible as the controllers provide data output on Metasys N2 and PLC understands LonWorks only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and Metasys N2 are Serial based Protocol. Hence, a converter is needed that can convert the data from Metasys N2 device to LonWorks and vice versa.
  • PG-106-105-AC Metasys N2 to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from controllers on Metasys N2 and it caches this data internally and then provides it on LonWorks when requested from the PLC.

Outline of Metasys N2 and LonWorks

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.

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.

How to configure the PG-106-105-AC 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-106-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-106-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-106-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.

PG-102-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

When configured as a BACnet MS/TP client, the PG-102-105-AC can read data from your BACnet MS/TP devices and publish it as LonWorks data. Also, it can write commands sent from the LonWorks side to the BACnet MS/TP devices.

PG-102-105-AC can be configured to behave as a server on both LonWorks and BACnet MS/TP 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).

The PG-102-105-AC can be configured to behave as a client on both LonWorks and BACnet MS/TP interfaces.

PG-102-105-AC gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-102-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-102-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 Thermostats on the site which provide data output on LonWorks.
  • The site has a BACnet MS/TP based Controller that needs the temperature data from the Thermostats.
  • A direct exchange of data between Thermostats and Controller is not possible as the Thermostats provide the data output on LonWorks and Controller understands BACnet MS/TP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and BACnet MS/TP are Serial Protocols. Hence, a converter is needed that will convert the data from BACnet MS/TP device to LonWorks and vice versa.
  • PG-102-105-AC BACnet MS/TP to LonWorks is an excellent solution for this requirement. This helps the gateway in reading data from the Energy meters on LonWorks and it caches this data internally and then provides it on BACnet MS/TP when requested from the Controller.

Scenario 2

  • There is a Chiller on the site which provides data output on BACnet MS/TP.
  • The site has a PLC on LonWorks which needs the temperature, pressure, humidity etc. on BACnet MS/TP.
  • A direct exchange of data between a Chiller and PLC is not possible as a Chiller provide data output on BACnet MS/TP and PLC understands LonWorks only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and BACnet MS/TP are Serial Protocols. Hence, a converter is needed that will convert the data from BACnet MS/TP device to LonWorks and vice versa.
  • PG-102-105-AC BACnet MS/TP to LonWorks is an excellent solution for this requirement. This helps the gateway in reading data from the Chiller on BACnet MS/TP and it caches this data internally and then provides it on LonWorks when requested from the PLC.

Outline of LonWorks and BACnet MS/TP

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.

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.

How to configure the PG-102-105-AC 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-102-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-102-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-102-105-AC. This includes but is not limited to:
  • Node ids of the slave devices
  • IP addresses/device address of the slave devices
  • Baud rate, parity, stop bits for serial communication
  • 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.

PG-103-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

The PG-103-105-AC can be configured to behave as a server on both LonWorks and BACnet IP 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).

The PG-103-105-AC can be configured to behave as a client on both LonWorks and BACnet IP interfaces.

PG-103-105-AC gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-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-103-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 is a Controller on site which provides data output on LonWorks.
  • The site has a Building Management System on BACnet IP that needs the energy data from Controller.
  • A direct exchange of data between Controller and Building Management System is not possible as the LonWorks Controller provides data output on LonWorks and the Building Management System understands BACnet IP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks is a Serial Protocol while BACnet IP is an Ethernet based Protocol. Hence, a converter is needed which will convert the data from BACnet IP device to LonWorks and vice versa.
  • PG-103-105-AC BACnet IP to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from the Controller on LonWorks and it caches this data internally and then provides it on BACnet IP when requested from Building Management System.

Scenario 2

  • There are Thermostats on the site which provide data output on BACnet IP.
  • The site has a PLC on LonWorks which needs the temperature data from thermostat on BACnet IP.
  • A direct exchange of data between Thermostat and PLC is not possible as the thermostats provide data output on BACnet IP and PLC understands LonWorks only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks is a Serial Protocol while BACnet IP is an Ethernet based Protocol. Hence, a converter is needed which will convert the data from BACnet IP device to LonWorks and vice versa.
  • PG-103-105-AC BACnet IP to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from the Thermostats on BACnet IP and it caches this data internally and then provides it on LonWorks when requested from the PLC.

Outline of LonWorks and BACnet IP

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.

BACnet IP

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

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

How to configure the PG-103-105-AC 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-103-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-103-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-103-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.

PG-100-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

The PG-100-105-AC can be configured to behave as a server on both LonWorks and Modbus RTU 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-100-105-AC can be configured to behave as a client on both LonWorks and Modbus RTU interfaces.

PG-100-105-AC gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-100-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-100-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 Schneider Ion energy meters on the site which provides data output on Modbus RTU.
  • The site has a LonWorks based Controller that needs the energy data from the Schneider ion meters.
  • A direct exchange of data between Energy meters and Controller is not possible as the energy meters provide data output on Modbus RTU and Controller understands LonWorks only.

Solution

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

Scenario 2

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

Solution

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

Outline of Modbus RTU and LonWorks

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

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.

How to configure the PG-100-105-AC 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-100-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-100-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-100-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.

PG-101-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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.

Outline of Modbus TCP and LonWorks

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.

How to configure the PG-101-105-AC 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-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.

PG-104-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

The PG-104-105-AC can be configured to behave as a server on both LonWorks and JCI Metasys N2 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-104-105-AC can be configured to behave as a client on both LonWorks and JCI Metasys N2 interfaces.

PG-104-105-AC gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-104-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-104-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 Cummins PCC controllers on various diesel Generators the site which provide data output on LonWorks.
  • The site has a Network Automation Engine on Metasys N2 that needs energy data from the Controller.
  • A direct exchange of data between Controllers and Engine is not possible as the Controllers provide data output on LonWorks and an Engine understands Metasys N2 only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and Metasys N2 are Serial based Protocol. Hence, a converter is needed that can convert the data from Metasys N2 device to LonWorks and vice versa.
  • PG-104-105-AC Metasys N2 to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from the PCC controller on LonWorks and it caches this data internally and then provides it on Metasys N2 when requested from the Network Automation Engine.

Scenario 2

  • There are controllers on the other site which provide data output on Metasys N2.
  • The site has a PLC on LonWorks that needs the temperature data from controllers on Metasys N2.
  • A direct exchange of data between controllers and PLC is not possible as the controllers provide data output on Metasys N2 and PLC understands LonWorks only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and Metasys N2 are Serial based Protocol. Hence, a converter is needed that can convert the data from Metasys N2 device to LonWorks and vice versa.
  • PG-104-105-AC Metasys N2 to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from controllers on Metasys N2 and it caches this data internally and then provides it on LonWorks when requested from the PLC.

Outline of Metasys N2 and LonWorks

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.

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.

How to configure the PG-106-105-AC 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-106-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-106-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-106-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.

PG-106-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-106-105-AC gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-106-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-106-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 Cummins PCC controllers on various diesel Generators the site which provide data output on LonWorks.
  • The site has a Network Automation Engine on Metasys N2 that needs energy data from the Controller.
  • A direct exchange of data between Controllers and Engine is not possible as the Controllers provide data output on LonWorks and an Engine understands Metasys N2 only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and Metasys N2 are Serial based Protocol. Hence, a converter is needed that can convert the data from Metasys N2 device to LonWorks and vice versa.
  • PG-106-105-AC Metasys N2 to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from the PCC controller on LonWorks and it caches this data internally and then provides it on Metasys N2 when requested from the Network Automation Engine.

Scenario 2

  • There are controllers on the other site which provide data output on Metasys N2.
  • The site has a PLC on LonWorks that needs the temperature data from controllers on Metasys N2.
  • A direct exchange of data between controllers and PLC is not possible as the controllers provide data output on Metasys N2 and PLC understands LonWorks only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and Metasys N2 are Serial based Protocol. Hence, a converter is needed that can convert the data from Metasys N2 device to LonWorks and vice versa.
  • PG-106-105-AC Metasys N2 to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from controllers on Metasys N2 and it caches this data internally and then provides it on LonWorks when requested from the PLC.

Outline of Metasys N2 and LonWorks

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.

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, fibre 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.

How to configure the PG-106-105-AC 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-106-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-106-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-106-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.

PG-102-104-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

The PG-102-104-AA can be configured to behave as a server on both SNMP and BACnet MS/TP 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).

The PG-102-104-AA can be configured to behave as a client on both SNMP and BACnet MS/TP interfaces.

PG-102-104-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-102-104-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-104-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 Schneider Ion energy meters on the site which provide data output on BACnet MS/TP.
  • The site has a building management system on SNMP which needs the energy data from Schneider ion meters.
  • A direct exchange of data between Schneider Ion meters and Building management system is not possible as Schneider Ion meters provide data output on BACnet MS/TP and Building management system understands SNMP only.

Solution

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

Scenario 2

  • BACnet MS/TP PLC needs to read data from SNMP based UPS units.
  • There is PLC on the site on BACnet MS/TP which needs the data from UPS units on SNMP.
  • A direct exchange of data output between UPS units and PLC is not possible as UPS units provide data output on SNMP and the PLC understands BACnet MS/TP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. BACnet MS/TP is a Serial protocol, while SNMP is an Ethernet based protocol. Hence, a converter is needed which will convert the data from SNMP device to BACnet MS/TP and vice versa.
  • PG-102-104-AA BACnet MS/TP to SNMP converter is an excellent solution to this requirement. This helps the gateway in reading the data from UPS units on SNMP and it caches this data internally and then provides it on BACnet MS/TP when requested from the PLC.

Outline of BACnet MS/TP and SNMP

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.

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.

How to configure the PG-102-104-AA 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-102-104-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-104-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-104-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.

PG-103-104-XX

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-103-104-XX gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-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 PG-103-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

PG-103-104-XX BACnet IP to SNMP Gateway

Scenario 1

  • There are several UPS and PAC units on the site which provides data output on SNMP.
  • The site has a Building Management System on BACnet IP which needs the energy data from the Variable frequency drives.
  • A direct exchange of data between Variable frequency drives and Building Management System is not possible as Variable frequency drives provides data output on SNMP and Building Management System understands BACnet IP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. BACnet IP and SNMP both are Ethernet based protocols and hence, a converter is needed which will convert the data from SNMP device to BACnet IP and vice versa.
  • PG-103-104-XX BACnet IP to SNMP converter is an excellent solution to this requirement. This helps the gateway in reading the data from the Variable frequency drives on BACnet IP and it caches this data internally and then provides it on SNMP when requested from the Building Management System.

Scenario 2

  • There are BTU meters on the other site which provides data output on BACnet IP.
  • The site has SCADA on SNMP which needs the data from BTU meters on BACnet IP.
  • A direct exchange of data between BTU meters and SCADA is not possible as BTU meters provide data output on BACnet IP and SCADA understands SNMP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. BACnet IP and SNMP both are Ethernet based protocols and hence, a converter is needed which will convert the data from SNMP device to BACnet IP and vice versa.
  • PG-103-104-XX BACnet IP to SNMP converter is an excellent solution to this requirement. This helps the gateway in reading the data from the BTU meters on BACnet IP and it caches this data internally and then provides it on SNMP when requested from SCADA.

Outline of SNMP and BACnet IP

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.

BCAnet

BACnet (Building Automation and Control Network) is a communications protocol that helps the communication between building automation end-devices and building management systems. The BACnet protocol specification like every other protocol specification defines both how data is represented on the network and the services that are used to move data from one BACnet node to another. The specification also tells us about messages that identify data and network nodes such as Who-Has, I-Have, Who-Is, and I-Am.

To meet the requirement of the widest possible set of applications BACnet was designed to support several different physical and link layers.

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

How to configure the PG-103-105-AC 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-103-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-103-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-103-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.

PG-100-104-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-100-104-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-100-104-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-104-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 Schneider Ion meters on the site which provide data output on Modbus RTU.
  • The site has a building management system on SNMP that needs the energy data from Schneider ion meters.
  • A direct exchange of data between Schneider ion meters and building management system is not possible as the Schneider Ion meters provide data output on Modbus RTU and building management system understands SNMP only.

Solution

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

Scenario 2

  • There are PAC units on the other site which provide data output on SNMP.
  • The site has a PLC on Modbus RTU that needs the temperature data from PAC units on SNMP.
  • A direct exchange of data between PAC units and PLC is not possible as the PAC units provide data output on SNMP and the PLC understands Modbus RTU only.

Solution

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

Outline of Modbus RTU and SNMP

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

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.

How to configure the PG-100-104-AA 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-100-104-AA gateway.
  • However, it is very helpful to know how to configure the devices. All the required tools and supporting product manuals will be provided completely free of cost with your purchase.
  • Configuration of the PG-100-104-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-104-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.

PG-101-104-XX

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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.

PG-104-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

PG-104-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-104-105-AC Gateway model supports JCI Metasys N2 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-104-105-AC can read data from your SNMP devices and publish it as JCI Metasys N2 data. Also, it can write commands sent from the JCI Metasys N2 side to the SNMP devices.

When configured as a JCI Metasys N2 client, the PG-104-105-AC can read data from your JCI Metasys N2 devices and publish it as SNMP data. Also, it can write commands sent from the SNMP side to the JCI Metasys N2 devices.

The PG-104-105-AC can be configured to behave as a server on both SNMP and JCI Metasys N2 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-104-105-AC can be configured to behave as a client on both SNMP and JCI Metasys N2 interfaces.

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

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 SCADA on SNMP that needs the data from the Ion meters on Metasys N2.
  • The direct exchange of data between Controllers and SCADA is not possible as the Controllers provide data output on Metasys N2 and SCADA understands SNMP 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 SNMP is an Ethernet protocol. Hence, a converter is needed that converts the data from SNMP device to Metasys N2 and vice versa.
  • PG-104-105-AC Metasys N2 to SNMP converter is an excellent solution for this requirement. This helps the gateway in reading the data from the Energy meters on Metasys N2 and it caches this data internally and then provides it on SNMP when requested from the SCADA system.

Scenario 2

  • There are several UPS units on the site which provide data output on SNMP.
  • The site has a N2 based controller on Metasys N2 that needs data from UPS units on SNMP.
  • A direct exchange of data between UPS units and controller is not possible as the UPS units provide data output on SNMP and 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 SNMP is an Ethernet protocol. Hence, a converter is needed that converts the data from SNMP device to Metasys N2 and vice versa.
  • PG-104-105-AC Metasys N2 to SNMP converter is an excellent solution for this requirement. This helps the gateway in reading the data from UPS units on SNMP and it caches this data internally and then provides it on Metasys N2 when requested from the Controller.

Outline of Metasys N2 and SNMP

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.

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.

How to configure the PG-106-104-AA 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-106-104-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-106-104-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-106-104-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.

PG-106-104-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-106-104-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-106-104-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-106-104-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 SCADA on SNMP that needs the data from the Ion meters on Metasys N2.
  • The direct exchange of data between Controllers and SCADA is not possible as the Controllers provide data output on Metasys N2 and SCADA understands SNMP 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 SNMP is an Ethernet protocol. Hence, a converter is needed that converts the data from SNMP device to Metasys N2 and vice versa.
  • PG-106-104-AA Metasys N2 to SNMP converter is an excellent solution for this requirement. This helps the gateway in reading the data from the Energy meters on Metasys N2 and it caches this data internally and then provides it on SNMP when requested from the SCADA system.

Scenario 2

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

Outline of Metasys N2 and SNMP

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.

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.

How to configure the PG-106-104-AA 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-106-104-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-106-104-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-106-104-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.

PG-103-102-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

The PG-103-102-AA can be configured to behave as a client on both BACnet MS/TP and BACnet IP interfaces.

PG-103-102-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-102-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-103-102-AA.

Key Features

  • Ability to interface up to 1000 points of common BAS protocols
  • 2xRS 485, 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 thermostats on the site which can provide data output on BACnet IP.
  • There is a BACnet MSTP based Controller on the site which needs the temperature data from the Thermostats.
  • A direct exchange of data between the Thermostats and Controller is not possible as Thermostats provide data output on BACnet IP and the Controller understands BACnet MSTP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol and as they are on the different protocol they cannot directly communicate with each other.
  • BACnet IP is an Ethernet based protocol and BACnet MSTP is a Serial Protocol. Therefore, we need a converter that will convert data from BACnet MSTP device to BACnet IP and vice versa.
  • PG-103-102-AA BACnet IP to BACnet MSTP converter is an excellent solution for this requirement. This device will help the gateway to read the data from Thermostat on BACnet IP and it will cache the data internally and provide it on BACnet MSTP when requested from the Controller.

Scenario 2

  • We have Chiller on the other side that can provide data output on BACnet MSTP.
  • A building management system on BACnet IP on the site needs the data from the Chiller.
  • A direct exchange of the data is not possible between the Chiller and a Building management system as the Chiller provides data output on BACnet MSTP and the Building management system understands BACnet IP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol and as they are on the different protocol they cannot directly communicate with each other.
  • BACnet IP is an Ethernet based protocol and BACnet MSTP is a Serial Protocol. Therefore, we need a converter that will convert data from BACnet MSTP device to BACnet IP and vice versa.
  • PG-103-102-AA BACnet IP to BACnet MSTP converter is an excellent solution for this requirement. This device will help the gateway to read the data from Chiller on BACnet MSTP and it will cache the data internally and provide it on BACnet IP when requested from the Building Management System.

BACnet IP

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

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.

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

PG-103-102-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

The PG-103-102-AA can be configured to behave as a client on both BACnet MS/TP and BACnet IP interfaces.

PG-103-102-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-102-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-103-102-AA.

Key Features

  • Ability to interface up to 1000 points of common BAS protocols
  • 2xRS 485, 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 thermostats on the site which can provide data output on BACnet IP.
  • There is a BACnet MSTP based Controller on the site which needs the temperature data from the Thermostats.
  • A direct exchange of data between the Thermostats and Controller is not possible as Thermostats provide data output on BACnet IP and the Controller understands BACnet MSTP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol and as they are on the different protocol they cannot directly communicate with each other.
  • BACnet IP is an Ethernet based protocol and BACnet MSTP is a Serial Protocol. Therefore, we need a converter that will convert data from BACnet MSTP device to BACnet IP and vice versa.
  • PG-103-102-AA BACnet IP to BACnet MSTP converter is an excellent solution for this requirement. This device will help the gateway to read the data from Thermostat on BACnet IP and it will cache the data internally and provide it on BACnet MSTP when requested from the Controller.

Scenario 2

  • We have Chiller on the other side that can provide data output on BACnet MSTP.
  • A building management system on BACnet IP on the site needs the data from the Chiller.
  • A direct exchange of the data is not possible between the Chiller and a Building management system as the Chiller provides data output on BACnet MSTP and the Building management system understands BACnet IP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol and as they are on the different protocol they cannot directly communicate with each other.
  • BACnet IP is an Ethernet based protocol and BACnet MSTP is a Serial Protocol. Therefore, we need a converter that will convert data from BACnet MSTP device to BACnet IP and vice versa.
  • PG-103-102-AA BACnet IP to BACnet MSTP converter is an excellent solution for this requirement. This device will help the gateway to read the data from Chiller on BACnet MSTP and it will cache the data internally and provide it on BACnet IP when requested from the Building Management System.

BACnet IP

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

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.

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

PG-102-100-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

The PG-102-100-AA can be configured to behave as a client on both Modbus RTU and BACnet MS/TP interfaces.

PG-102-100-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-102-100-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-100-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 Schneider Ion energy meters on the site which provides data output on Modbus RTU.
  • The site has a BACnet MS/TP based Controller which needs the energy data from the Schneider ion meters.
  • A direct exchange of data between Energy meters and Controller is not possible as the energy meters provide data output on Modbus RTU and Controller understands BACnet MS/TP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. Modbus RTU and BACnet MS/TP are Serial Protocols and hence a converter is needed which will convert data from BACnet MS/TP device to Modbus RTU and vice versa.
  • PG-102-100-AA Modbus RTU to BACnet MSTP converter is an excellent solution to this requirement.This helps the gateway in reading the data from the Energy meters on Modbus RTU and it caches this data internally and then provides it on BACnet MS/TP when requested from the Controller.

Scenario 2

  • There are Chillers on the other site which provides data output on BACnet MS/TP.
  • The site has a PLC on Modbus RTU that needs the temperature data from thermostat on BACnet MS/TP.
  • A direct exchange of data between Chiller and PLC is not possible as the Chiller provides data output on BACnet MS/TP and PLC understands Modbus RTU only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. Modbus RTU and BACnet MS/TP are Serial Protocols and hence a converter is needed which will convert data from BACnet MS/TP device to Modbus RTU and vice versa.
  • PG-102-100-AA Modbus RTU to BACnet MSTP converter is an excellent solution to this requirement. This helps the gateway in reading the data from the Chiller on BACnet MS/TP and it caches this data internally and then provides it on Modbus RTU when requested from the PLC.

Outline of Modbus RTU and BACnet MS/TP

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

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.

How to configure the PG-102-100-AA 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-102-100-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-100-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-100-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.

PG-102-101-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

The PG-102-101-AA can be configured to behave as a client on both Modbus TCP and BACnet MS/TP interfaces.

PG-102-101-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-102-101-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-101-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 Variable frequency drives on the site which provides data output on Modbus TCP.
  • The site has a BACnet MS/TP based Controller which needs the energy data from the Variable frequency drives.
  • A direct exchange of data between Variable frequency drives and controller is not possible as the Variable frequency drives provide data output on Modbus TCP and Controller understands BACnet MS/TP only.

Solution

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

Scenario 2

  • There are Chillers on the other site which provides data output on BACnet MS/TP.
  • The site has a SCADA on Modbus TCP which needs the temperature data from chillers on BACnet MS/TP.
  • A direct exchange of data between Chillers and SCADA is not possible as the Chillers provide data output on BACnet MS/TP 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 an Ethernet based protocol and BACnet MS/TP is a Serial protocol. Hence, a converter is needed which converts the data from BACnet MS/TP device to Modbus TCP and vice versa.
  • PG-102-101-AA BACnet MS/TP to Modbus TCP converter is an excellent solution to this requirement. This helps the gateway in reading data from the Chillers on BACnet MS/TP and it caches this data internally and provides it on Modbus TCP when requested from the SCADA.

Outline of Modbus TCP and BACnet MS/TP

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.

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.

How to configure the PG-102-101-AA 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-102-101-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-101-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-101-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.

PG-102-104-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

The PG-102-104-AA can be configured to behave as a server on both SNMP and BACnet MS/TP 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).

The PG-102-104-AA can be configured to behave as a client on both SNMP and BACnet MS/TP interfaces.

PG-102-104-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-102-104-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-104-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 Schneider Ion energy meters on the site which provide data output on BACnet MS/TP.
  • The site has a building management system on SNMP which needs the energy data from Schneider ion meters.
  • A direct exchange of data between Schneider Ion meters and Building management system is not possible as Schneider Ion meters provide data output on BACnet MS/TP and Building management system understands SNMP only.

Solution

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

Scenario 2

  • BACnet MS/TP PLC needs to read data from SNMP based UPS units.
  • There is PLC on the site on BACnet MS/TP which needs the data from UPS units on SNMP.
  • A direct exchange of data output between UPS units and PLC is not possible as UPS units provide data output on SNMP and the PLC understands BACnet MS/TP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. BACnet MS/TP is a Serial protocol, while SNMP is an Ethernet based protocol. Hence, a converter is needed which will convert the data from SNMP device to BACnet MS/TP and vice versa.
  • PG-102-104-AA BACnet MS/TP to SNMP converter is an excellent solution to this requirement. This helps the gateway in reading the data from UPS units on SNMP and it caches this data internally and then provides it on BACnet MS/TP when requested from the PLC.

Outline of BACnet MS/TP and SNMP

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.

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.

How to configure the PG-102-104-AA 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-102-104-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-104-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-104-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.

PG-102-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

When configured as a BACnet MS/TP client, the PG-102-105-AC can read data from your BACnet MS/TP devices and publish it as LonWorks data. Also, it can write commands sent from the LonWorks side to the BACnet MS/TP devices.

PG-102-105-AC can be configured to behave as a server on both LonWorks and BACnet MS/TP 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).

The PG-102-105-AC can be configured to behave as a client on both LonWorks and BACnet MS/TP interfaces.

PG-102-105-AC gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-102-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-102-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 Thermostats on the site which provide data output on LonWorks.
  • The site has a BACnet MS/TP based Controller that needs the temperature data from the Thermostats.
  • A direct exchange of data between Thermostats and Controller is not possible as the Thermostats provide the data output on LonWorks and Controller understands BACnet MS/TP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and BACnet MS/TP are Serial Protocols. Hence, a converter is needed that will convert the data from BACnet MS/TP device to LonWorks and vice versa.
  • PG-102-105-AC BACnet MS/TP to LonWorks is an excellent solution for this requirement. This helps the gateway in reading data from the Energy meters on LonWorks and it caches this data internally and then provides it on BACnet MS/TP when requested from the Controller.

Scenario 2

  • There is a Chiller on the site which provides data output on BACnet MS/TP.
  • The site has a PLC on LonWorks which needs the temperature, pressure, humidity etc on BACnet MS/TP.
  • A direct exchange of data between a Chiller and PLC is not possible as a Chiller provide data output on BACnet MS/TP and PLC understands LonWorks only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks and BACnet MS/TP are Serial Protocols. Hence, a converter is needed that will convert the data from BACnet MS/TP device to LonWorks and vice versa.
  • PG-102-105-AC BACnet MS/TP to LonWorks is an excellent solution for this requirement. This helps the gateway in reading data from the Chiller on BACnet MS/TP and it caches this data internally and then provides it on LonWorks when requested from the PLC.

Outline of LonWorks and BACnet MS/TP

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.

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.

How to configure the PG-102-105-AC 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-102-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-102-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-102-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.

PG-102-106-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

Outline of Metasys N2 and BACnet MS/TP

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.

Outline of Metasys N2 and BACnet IP

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.

How to configure the PG-102-106-AA 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-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.

PG-103-102-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

The PG-103-102-AA can be configured to behave as a client on both BACnet MS/TP and BACnet IP interfaces.

PG-103-102-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-102-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-103-102-AA.

Key Features

  • Ability to interface up to 1000 points of common BAS protocols
  • 2xRS 485, 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 thermostats on the site which can provide data output on BACnet IP.
  • There is a BACnet MSTP based Controller on the site which needs the temperature data from the Thermostats.
  • A direct exchange of data between the Thermostats and Controller is not possible as Thermostats provide data output on BACnet IP and the Controller understands BACnet MSTP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol and as they are on the different protocol they cannot directly communicate with each other.
  • BACnet IP is an Ethernet based protocol and BACnet MSTP is a Serial Protocol. Therefore, we need a converter that will convert data from BACnet MSTP device to BACnet IP and vice versa.
  • PG-103-102-AA BACnet IP to BACnet MSTP converter is an excellent solution for this requirement. This device will help the gateway to read the data from Thermostat on BACnet IP and it will cache the data internally and provide it on BACnet MSTP when requested from the Controller.

Scenario 2

  • We have Chiller on the other side that can provide data output on BACnet MSTP.
  • A building management system on BACnet IP on the site needs the data from the Chiller.
  • A direct exchange of the data is not possible between the Chiller and a Building management system as the Chiller provides data output on BACnet MSTP and the Building management system understands BACnet IP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol and as they are on the different protocol they cannot directly communicate with each other.
  • BACnet IP is an Ethernet based protocol and BACnet MSTP is a Serial Protocol. Therefore, we need a converter that will convert data from BACnet MSTP device to BACnet IP and vice versa.
  • PG-103-102-AA BACnet IP to BACnet MSTP converter is an excellent solution for this requirement. This device will help the gateway to read the data from Chiller on BACnet MSTP and it will cache the data internally and provide it on BACnet IP when requested from the Building Management System.

BACnet IP

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

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.

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

PG-103-102-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

The PG-103-102-AA can be configured to behave as a client on both BACnet MS/TP and BACnet IP interfaces.

PG-103-102-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-102-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-103-102-AA.

Key Features

  • Ability to interface up to 1000 points of common BAS protocols
  • 2xRS 485, 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 thermostats on the site which can provide data output on BACnet IP.
  • There is a BACnet MSTP based Controller on the site which needs the temperature data from the Thermostats.
  • A direct exchange of data between the Thermostats and Controller is not possible as Thermostats provide data output on BACnet IP and the Controller understands BACnet MSTP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol and as they are on the different protocol they cannot directly communicate with each other.
  • BACnet IP is an Ethernet based protocol and BACnet MSTP is a Serial Protocol. Therefore, we need a converter that will convert data from BACnet MSTP device to BACnet IP and vice versa.
  • PG-103-102-AA BACnet IP to BACnet MSTP converter is an excellent solution for this requirement. This device will help the gateway to read the data from Thermostat on BACnet IP and it will cache the data internally and provide it on BACnet MSTP when requested from the Controller.

Scenario 2

  • We have Chiller on the other side that can provide data output on BACnet MSTP.
  • A building management system on BACnet IP on the site needs the data from the Chiller.
  • A direct exchange of the data is not possible between the Chiller and a Building management system as the Chiller provides data output on BACnet MSTP and the Building management system understands BACnet IP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol and as they are on the different protocol they cannot directly communicate with each other.
  • BACnet IP is an Ethernet based protocol and BACnet MSTP is a Serial Protocol. Therefore, we need a converter that will convert data from BACnet MSTP device to BACnet IP and vice versa.
  • PG-103-102-AA BACnet IP to BACnet MSTP converter is an excellent solution for this requirement. This device will help the gateway to read the data from Chiller on BACnet MSTP and it will cache the data internally and provide it on BACnet IP when requested from the Building Management System.

BACnet IP

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

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.

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

PG-103-100-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

The PG-103-100-AA can be configured to behave as a client on both Modbus RTU and BACnet IP interfaces.

PG-103-100-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-100-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-103-100-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 Schneider Ion meters on site which can provide data output on Modbus RTU.
  • The site has a building management system on BACnet IP that needs the energy data from the Schneider Ion meters.
  • A direct exchange of data is not possible between Schneider Ion meters and a Building management system as the Schneider Ion meters provide data output on Modbus RTU and the Building management system understands BACnet IP only.

Solution

  • The devices can directly communicate with other only if they are on the same protocol. Modbus RTU is a Serial protocol and BACnet IP is an Ethernet based Protocol. Hence, a converter is needed which can convert the data from BACnet IP device to Modbus RTU and vice versa.
  • PG-103-100-AA Modbus RTU to BACnet IP converter is an excellent solution for this requirement. This helps the gateway in reading the data from the Energy meters on Modbus RTU and it caches the data internally and then provides it on BACnet IP when requested from Building Management System.

Scenario 2

  • Modbus RTU PLC needs to read data from BACnet IP based Thermostats.
  • There are Thermostats on the site which can provide data output on BACnet IP.
  • A PLC on Modbus RTU on the site needs the temperature data from Thermostat on BACnet IP.
  • A direct exchange of data between a Thermostat and a PLC is not possible as the Thermostat provide data output on BACnet IP and the PLC understands Modbus RTU only.

Solution

  • The devices can directly communicate with other only if they are on the same protocol. Modbus RTU is a Serial protocol and BACnet IP is an Ethernet based Protocol. Hence, a converter is needed which can convert the data from BACnet IP device to Modbus RTU and vice versa.
  • PG-103-100-AA Modbus RTU to BACnet IP converter is an excellent solution for this requirement. This helps the gateway in reading the data from the Thermostats on BACnet IP and it caches the data internally and then provides it on Modbus RTU when requested from the PLC.

Outline of Modbus RTU and BACnet IP

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

BACnet IP

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

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.

How to configure the PG-103-100-AA 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-103-100-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-103-100-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-103-100-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.

PG-101-103-XX

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

The PG-101-103-XX can be configured to behave as a client on both Modbus TCP and BACnet IP interfaces.

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

Outline of BACnet IP and Modbus TCP Gateway

Scenario 1

  • There are several Variable frequency drives which can provide data output on Modbus TCP on the site.
  • The site has a building management system on BACnet IP that needs the energy data from the Variable frequency drives.
  • A direct exchange of data between the Variable frequency drives and a Building management system is not possible as the Variable frequency drives provide data output on Modbus TCP and the Building management system understands BACnet IP only.

Solution

  • The devices can only connect directly to each other if they are on the same protocol. Modbus TCP and BACnet IP are Ethernet protocols and hence a converter is needed that can convert the data from the BACnet IP device to Modbus TCP and vice versa.
  • PG-101-103-XX Modbus TCP to BACnet IP converter is an excellent solution for this requirement. It helps the gateway to read the data from the Variable frequency drives on Modbus TCP and it will cache this data internally and then will provide it on BACnet IP when requested from the Building Management system.

Scenario 2

  • We have Thermostats on the site which can provide data output on BACnet IP.
  • The site has a SCADA on Modbus TCP that needs the temperature data from thermostat on BACnet IP.
  • A direct exchange of data between Thermostat and the SCADA is not possible as Thermostat provide data output on BACnet IP and the SCADA understands Modbus TCP only.

Solution

  • The devices can only connect directly to each other if they are on the same protocol. Modbus TCP and BACnet IP are Ethernet protocols and hence a converter is needed that can convert the data from the BACnet IP device to Modbus TCP and vice versa.
  • PG-101-103-XX Modbus TCP to BACnet IP converter is an excellent solution for this requirement. It helps the gateway to read the data from the Thermostat on BACnet IP and it will caches this data internally and then will provide it on Modbus TCP when requested from SCADA.

Outline of Modbus TCP and BACnet IP

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.

BACnet IP

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

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.

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

PG-103-104-XX

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-103-104-XX gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-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 PG-103-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 and PAC units on the site which provides data output on SNMP.
  • The site has a Building Management System on BACnet IP which needs the energy data from the Variable frequency drives.
  • A direct exchange of data between Variable frequency drives and Building Management System is not possible as Variable frequency drives provides data output on SNMP and Building Management System understands BACnet IP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. BACnet IP and SNMP both are Ethernet based protocols and hence, a converter is needed which will convert the data from SNMP device to BACnet IP and vice versa.
  • PG-103-104-XX BACnet IP to SNMP converter is an excellent solution to this requirement. This helps the gateway in reading the data from the Variable frequency drives on BACnet IP and it caches this data internally and then provides it on SNMP when requested from the Building Management System.

Scenario 2

  • There are BTU meters on the other site which provides data output on BACnet IP.
  • The site has SCADA on SNMP which needs the data from BTU meters on BACnet IP.
  • A direct exchange of data between BTU meters and SCADA is not possible as BTU meters provide data output on BACnet IP and SCADA understands SNMP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. BACnet IP and SNMP both are Ethernet based protocols and hence, a converter is needed which will convert the data from SNMP device to BACnet IP and vice versa.
  • PG-103-104-XX BACnet IP to SNMP converter is an excellent solution to this requirement. This helps the gateway in reading the data from the BTU meters on BACnet IP and it caches this data internally and then provides it on SNMP when requested from SCADA.

Outline of SNMP and BACnet IP

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.

BACnet IP

BACnet (Building Automation and Control Network) is a communications protocol that helps the communication between building automation end-devices and building management systems. The BACnet protocol specification like every other protocol specification defines both how data is represented on the network and the services that are used to move data from one BACnet node to another. The specification also tells us about messages that identify data and network nodes such as Who-Has, I-Have, Who-Is, and I-Am.

To meet the requirement of the widest possible set of applications BACnet was designed to support several different physical and link layers.

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

How to configure the PG-103-105-AC 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-103-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-103-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-103-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.

PG-103-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

The PG-103-105-AC can be configured to behave as a server on both LonWorks and BACnet IP 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).

The PG-103-105-AC can be configured to behave as a client on both LonWorks and BACnet IP interfaces.

PG-103-105-AC gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-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-103-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 is a Controller on site which provides data output on LonWorks.
  • The site has a Building Management System on BACnet IP that needs the energy data from Controller.
  • A direct exchange of data between Controller and Building Management System is not possible as the LonWorks Controller provides data output on LonWorks and the Building Management System understands BACnet IP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks is a Serial Protocol while BACnet IP is an Ethernet based Protocol. Hence, a converter is needed which will convert the data from BACnet IP device to LonWorks and vice versa.
  • PG-103-105-AC BACnet IP to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from the Controller on LonWorks and it caches this data internally and then provides it on BACnet IP when requested from Building Management System.

Scenario 2

  • There are Thermostats on the site which provide data output on BACnet IP.
  • The site has a PLC on LonWorks which needs the temperature data from thermostat on BACnet IP.
  • A direct exchange of data between Thermostat and PLC is not possible as the thermostats provide data output on BACnet IP and PLC understands LonWorks only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. LonWorks is a Serial Protocol while BACnet IP is an Ethernet based Protocol. Hence, a converter is needed which will convert the data from BACnet IP device to LonWorks and vice versa.
  • PG-103-105-AC BACnet IP to LonWorks converter is an excellent solution to this requirement. This helps the gateway in reading the data from the Thermostats on BACnet IP and it caches this data internally and then provides it on LonWorks when requested from the PLC.

Outline of LonWorks and BACnet IP

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.

BACnet IP

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

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

How to configure the PG-103-105-AC 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-103-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-103-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-103-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.

PG-100-101-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-100-101-AA can be configured to behave as a client on both Modbus RTU and Modbus TCP interfaces.

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

PG-100-101-AA Modbus TCP to Modbus RTU Gateway

Scenario 1

  • There are several Schneider Ion energy meters on the site which provides data output on Modbus RTU.
  • The site has a SCADA on Modbus TCP which needs the data from the Ion meters on Modbus RTU.
  • A direct exchange of data between Energy meters and SCADA is not possible as the Energy meters provide data output on Modbus RTU and SCADA understands Modbus TCP only.

Solution

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

Scenario 2

  • There are several Variable frequency drives on the site which provide data output on Modbus TCP.
  • The site has a PLC on Modbus RTU that needs data from Variable frequency drives on Modbus TCP.
  • A direct exchange of data between Variable frequency drives and PLC is not possible as Variable frequency drives provide data output on Modbus TCP and PLC understands Modbus RTU only.

Solution

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

Outline of Modbus RTU and Modbus TCP

Modbus RTU

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

Modbus TCP

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

How to configure the PG-100-101-AA 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-100-101-AA gateway.
  • However, it is very helpful to know how to configure the devices. All the required tools and supporting product manuals will be provided completely free of cost with your purchase.
  • Configuration of the PG-100-101-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-101-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.

PG-100-101-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-100-101-AA can be configured to behave as a client on both Modbus RTU and Modbus TCP interfaces.

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

PG-100-101-AA Modbus TCP to Modbus RTU Gateway

Scenario 1

  • There are several Schneider Ion energy meters on the site which provides data output on Modbus RTU.
  • The site has a SCADA on Modbus TCP which needs the data from the Ion meters on Modbus RTU.
  • A direct exchange of data between Energy meters and SCADA is not possible as the Energy meters provide data output on Modbus RTU and SCADA understands Modbus TCP only.

Solution

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

Scenario 2

  • There are several Variable frequency drives on the site which provide data output on Modbus TCP.
  • The site has a PLC on Modbus RTU that needs data from Variable frequency drives on Modbus TCP.
  • A direct exchange of data between Variable frequency drives and PLC is not possible as Variable frequency drives provide data output on Modbus TCP and PLC understands Modbus RTU only.

Solution

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

Outline of Modbus RTU and Modbus TCP

Modbus RTU

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

Modbus TCP

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

How to configure the PG-100-101-AA 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-100-101-AA gateway.
  • However, it is very helpful to know how to configure the devices. All the required tools and supporting product manuals will be provided completely free of cost with your purchase.
  • Configuration of the PG-100-101-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-101-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.

PG-102-100-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

The PG-102-100-AA can be configured to behave as a client on both Modbus RTU and BACnet MS/TP interfaces.

PG-102-100-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-102-100-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-100-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 Schneider Ion energy meters on the site which provides data output on Modbus RTU.
  • The site has a BACnet MS/TP based Controller which needs the energy data from the Schneider ion meters.
  • A direct exchange of data between Energy meters and Controller is not possible as the energy meters provide data output on Modbus RTU and Controller understands BACnet MS/TP only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. Modbus RTU and BACnet MS/TP are Serial Protocols and hence a converter is needed which will convert data from BACnet MS/TP device to Modbus RTU and vice versa.
  • PG-102-100-AA Modbus RTU to BACnet MSTP converter is an excellent solution to this requirement.This helps the gateway in reading the data from the Energy meters on Modbus RTU and it caches this data internally and then provides it on BACnet MS/TP when requested from the Controller.

Scenario 2

  • There are Chillers on the other site which provides data output on BACnet MS/TP.
  • The site has a PLC on Modbus RTU that needs the temperature data from thermostat on BACnet MS/TP.
  • A direct exchange of data between Chiller and PLC is not possible as the Chiller provides data output on BACnet MS/TP and PLC understands Modbus RTU only.

Solution

  • The devices can directly communicate with each other only if they are on the same protocol. Modbus RTU and BACnet MS/TP are Serial Protocols and hence a converter is needed which will convert data from BACnet MS/TP device to Modbus RTU and vice versa.
  • PG-102-100-AA Modbus RTU to BACnet MSTP converter is an excellent solution to this requirement. This helps the gateway in reading the data from the Chiller on BACnet MS/TP and it caches this data internally and then provides it on Modbus RTU when requested from the PLC.

Outline of Modbus RTU and BACnet MS/TP

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

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.

How to configure the PG-102-100-AA 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-102-100-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-100-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-100-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.

PG-103-100-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

The PG-103-100-AA can be configured to behave as a client on both Modbus RTU and BACnet IP interfaces.

PG-103-100-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-100-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-103-100-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 Schneider Ion meters on site which can provide data output on Modbus RTU.
  • The site has a building management system on BACnet IP that needs the energy data from the Schneider Ion meters.
  • A direct exchange of data is not possible between Schneider Ion meters and a Building management system as the Schneider Ion meters provide data output on Modbus RTU and the Building management system understands BACnet IP only.

Solution

  • The devices can directly communicate with other only if they are on the same protocol. Modbus RTU is a Serial protocol and BACnet IP is an Ethernet based Protocol. Hence, a converter is needed which can convert the data from BACnet IP device to Modbus RTU and vice versa.
  • PG-103-100-AA Modbus RTU to BACnet IP converter is an excellent solution for this requirement. This helps the gateway in reading the data from the Energy meters on Modbus RTU and it caches the data internally and then provides it on BACnet IP when requested from Building Management System.

Scenario 2

  • Modbus RTU PLC needs to read data from BACnet IP based Thermostats.
  • There are Thermostats on the site which can provide data output on BACnet IP.
  • A PLC on Modbus RTU on the site needs the temperature data from Thermostat on BACnet IP.
  • A direct exchange of data between a Thermostat and a PLC is not possible as the Thermostat provide data output on BACnet IP and the PLC understands Modbus RTU only.

Solution

  • The devices can directly communicate with other only if they are on the same protocol. Modbus RTU is a Serial protocol and BACnet IP is an Ethernet based Protocol. Hence, a converter is needed which can convert the data from BACnet IP device to Modbus RTU and vice versa.
  • PG-103-100-AA Modbus RTU to BACnet IP converter is an excellent solution for this requirement. This helps the gateway in reading the data from the Thermostats on BACnet IP and it caches the data internally and then provides it on Modbus RTU when requested from the PLC.

Outline of Modbus RTU and BACnet IP

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

BACnet IP:

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

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.

How to configure the PG-103-100-AA 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-103-100-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-103-100-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-103-100-AA. This includes but is not limited to:
  • Node ids of the slave devices
  • IP addresses/device address of the slave devices
  • Baud rate, parity, stop bits for serial communication
  • 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.

PG-100-104-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-100-104-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-100-104-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-104-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 Schneider Ion meters on the site which provide data output on Modbus RTU.
  • The site has a building management system on SNMP that needs the energy data from Schneider ion meters.
  • A direct exchange of data between Schneider ion meters and building management system is not possible as the Schneider Ion meters provide data output on Modbus RTU and building management system understands SNMP only.

Solution

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

Scenario 2

  • There are PAC units on the other site which provide data output on SNMP.
  • The site has a PLC on Modbus RTU that needs the temperature data from PAC units on SNMP.
  • A direct exchange of data between PAC units and PLC is not possible as the PAC units provide data output on SNMP and the PLC understands Modbus RTU only.

Solution

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

Outline of Modbus RTU and SNMP

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

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.

How to configure the PG-100-104-AA 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-100-104-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-104-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-104-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.

PG-100-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

The PG-100-105-AC can be configured to behave as a server on both LonWorks and Modbus RTU 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-100-105-AC can be configured to behave as a client on both LonWorks and Modbus RTU interfaces.

PG-100-105-AC gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-100-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-100-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 Schneider Ion energy meters on the site which provides data output on Modbus RTU.
  • The site has a LonWorks based Controller that needs the energy data from the Schneider ion meters.
  • A direct exchange of data between Energy meters and Controller is not possible as the energy meters provide data output on Modbus RTU and Controller understands LonWorks only.

Solution

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

Scenario 2

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

Solution

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

Outline of Modbus RTU and LonWorks

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

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.

How to configure the PG-100-105-AC 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-100-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-100-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-100-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.

PG-100-106-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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.

Outline of Modbus RTU and Metasys N2

Modbus RTU

ModbusRTU 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 conecction 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.

How to configure the PG-100-106-AA 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-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.

PG-100-101-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-100-101-AA can be configured to behave as a client on both Modbus RTU and Modbus TCP interfaces.

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

PG-100-101-AA Modbus TCP to Modbus RTU Gateway

Scenario 1

  • There are several Schneider Ion energy meters on the site which provides data output on Modbus RTU.
  • The site has a SCADA on Modbus TCP which needs the data from the Ion meters on Modbus RTU.
  • A direct exchange of data between Energy meters and SCADA is not possible as the Energy meters provide data output on Modbus RTU and SCADA understands Modbus TCP only.

Solution

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

Scenario 2

  • There are several Variable frequency drives on the site which provide data output on Modbus TCP.
  • The site has a PLC on Modbus RTU that needs data from Variable frequency drives on Modbus TCP.
  • A direct exchange of data between Variable frequency drives and PLC is not possible as Variable frequency drives provide data output on Modbus TCP and PLC understands Modbus RTU only.

Solution

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

Outline of Modbus RTU and Modbus TCP

Modbus RTU

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

Modbus TCP

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

How to configure the PG-100-101-AA 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-100-101-AA gateway.
  • However, it is very helpful to know how to configure the devices. All the required tools and supporting product manuals will be provided completely free of cost with your purchase.
  • Configuration of the PG-100-101-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-101-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.

PG-103-106-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-103-106-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-103-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-103-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 site which can provide data output on Metasys N2.
  • The site has a SCADA on BACnet IP that needs the data from Ion Meters on Metasys N2.
  • A direct exchange of data between SCADA and Metasys N2 Controllers is not possible as Metasys N2 Controllers provide data output on Metasys N2 and the SCADA understands BACnet IP 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 BACnet IP is an Ethernet Protocol and hence we need a converter that will help to convert the data from BACnet IP device to Metasys N2 and vice versa.
  • PG-103-106-AA Metasys N2 to BACnet IP 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 provide it on BACnet IP when requested from the SCADA system.

Scenario 2

  • There are several variable frequency drives on the site which provide data output on BACnet IP.
  • The site has a NAE controller on Metasys N2 which needs data from Variable Frequency Drives on BACnet IP.
  • A direct exchange of data between NAE controller and Variable Frequency Drives is not possible as Variable Frequency Drives provide data output on BACnet IP and 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 is a Serial Protocol while BACnet IP is an Ethernet Protocol and hence we need a converter that will help to convert the data from BACnet IP device to Metasys N2 and vice versa.
  • PG-103-106-AA Metasys N2 to BACnet IP converter is an excellent solution for this requirement. This helps the gateway in reading data from the Variable Frequency Drive on BACnet IP and it caches this data internally and then provides it on Metasys N2 when requested from the NAE Controller.

Outline of Metasys N2 and BACnet IP

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 IP

BACnet (Building Automation and Control Network) is a communications protocol that helps the communication between building automation end-devices and building management systems. The BACnet protocol specification like every other protocol specification defines both how data is represented on the network and the services that are used to move data from one BACnet node to another. The specification also tells us about messages that identify data and network nodes such as who-Has, I-Have, Who-Is, and I-Am.

To meet the requirement of the widest possible set of applications BACnet was designed to support several different physical and link layers.

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

How to configure the PG-103-106-AA 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-103-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-103-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-103-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.

PG-100-101-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

PG-100-101-AA can be configured to behave as a client on both Modbus RTU and Modbus TCP interfaces.

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

PG-100-101-AA Modbus TCP to Modbus RTU Gateway

Scenario 1

  • There are several Schneider Ion energy meters on the site which provides data output on Modbus RTU.
  • The site has a SCADA on Modbus TCP which needs the data from the Ion meters on Modbus RTU.
  • A direct exchange of data between Energy meters and SCADA is not possible as the Energy meters provide data output on Modbus RTU and SCADA understands Modbus TCP only.

Solution

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

Scenario 2

  • There are several Variable frequency drives on the site which provide data output on Modbus TCP.
  • The site has a PLC on Modbus RTU that needs data from Variable frequency drives on Modbus TCP.
  • A direct exchange of data between Variable frequency drives and PLC is not possible as Variable frequency drives provide data output on Modbus TCP and PLC understands Modbus RTU only.

Solution

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

Outline of Modbus RTU and Modbus TCP

Modbus RTU

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

Modbus TCP

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

How to configure the PG-100-101-AA 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-100-101-AA gateway.
  • However, it is very helpful to know how to configure the devices. All the required tools and supporting product manuals will be provided completely free of cost with your purchase.
  • Configuration of the PG-100-101-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-101-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.

PG-102-101-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

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

The PG-102-101-AA can be configured to behave as a client on both Modbus TCP and BACnet MS/TP interfaces.

PG-102-101-AA gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-102-101-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-101-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 Variable frequency drives on the site which provides data output on Modbus TCP.
  • The site has a BACnet MS/TP based Controller which needs the energy data from the Variable frequency drives.
  • A direct exchange of data between Variable frequency drives and controller is not possible as the Variable frequency drives provide data output on Modbus TCP and Controller understands BACnet MS/TP only.

Solution

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

Scenario 2

  • There are Chillers on the other site which provides data output on BACnet MS/TP.
  • The site has a SCADA on Modbus TCP which needs the temperature data from chillers on BACnet MS/TP.
  • A direct exchange of data between Chillers and SCADA is not possible as the Chillers provide data output on BACnet MS/TP 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 an Ethernet based protocol and BACnet MS/TP is a Serial protocol. Hence, a converter is needed which converts the data from BACnet MS/TP device to Modbus TCP and vice versa.
  • PG-102-101-AA BACnet MS/TP to Modbus TCP converter is an excellent solution to this requirement. This helps the gateway in reading data from the Chillers on BACnet MS/TP and it caches this data internally and provides it on Modbus TCP when requested from the SCADA.

Outline of Modbus TCP and BACnet MS/TP

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.

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.

How to configure the PG-102-101-AA 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-102-101-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-101-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-101-AA. This includes but is not limited to:
  • Node ids of the slave devices
  • IP addresses/device address of the slave devices
  • Baud rate, parity, stop bits for serial communication
  • 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.

PG-101-103-XX

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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

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

When configured as a BACnet IP client, our gateway can read data from your BACnet IP devices  and publish it as Modbus TCP data. Also,  it can write commands sent from the Modbus TCP side to the BACnet IP devices.

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

The PG-101-103-XX can be configured to behave as a client on both Modbus TCP and BACnet IP interfaces.

PG-101-103-XX gateways have benefitted system integrators worldwide with its powerful line of gateways. Additionally, PG-101-103-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-103-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 Variable frequency drives which can provide data output on Modbus TCP on the site.
  • The site has a building management system on BACnet IP that needs the energy data from the Variable frequency drives.
  • A direct exchange of data between the Variable frequency drives and a Building management system is not possible as the Variable frequency drives provide data output on Modbus TCP and the Building management system understands BACnet IP only.

Solution

  • The devices can only connect directly to each other if they are on the same protocol. Modbus TCP and BACnet IP are Ethernet protocols and hence a converter is needed that can convert the data from the BACnet IP device to Modbus TCP and vice versa.
  • PG-101-103-XX Modbus TCP to BACnet IP converter is an excellent solution for this requirement. It helps the gateway to read the data from the Variable frequency drives on Modbus TCP and it will cache this data internally and then will provide it on BACnet IP when requested from the Building Management system.

Scenario 2

  • We have Thermostats on the site which can provide data output on BACnet IP.
  • The site has a SCADA on Modbus TCP that needs the temperature data from thermostat on BACnet IP.
  • A direct exchange of data between Thermostat and the SCADA is not possible as Thermostat provide data output on BACnet IP and the SCADA understands Modbus TCP only.

Solution

  • The devices can only connect directly to each other if they are on the same protocol. Modbus TCP and BACnet IP are Ethernet protocols and hence a converter is needed that can convert the data from the BACnet IP device to Modbus TCP and vice versa.
  • PG-101-103-XX Modbus TCP to BACnet IP converter is an excellent solution for this requirement. It helps the gateway to read the data from the Thermostat on BACnet IP and it will caches this data internally and then will provide it on Modbus TCP when requested from SCADA.

Outline of Modbus TCP and BACnet IP

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.

BACnet IP

The BACnet/IP allows users to transfer data to and from devices over Ethernet using BACnet/IP Protocol. It allows users to use different applications to discover devices, objects and properties of objects of any field device that supports BACnet IP.

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.

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

PG-101-104-XX

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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.

PG-101-105-AC

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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.

Outline of Modbus TCP and LonWorks

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.

How to configure the PG-101-105-AC 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-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.

PG-101-106-AA

by sales.aus@protoconvert.com sales.aus@protoconvert.com No Comments

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.

Outline of Modbus TCP and Metasys N2

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.

How to configure the PG-101-106-AA 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-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.