LonWorks to Metasys N2 Gateway | |Metasys N2 to LonWorks Protocol Converter
  • This gateway can read LonWorks data from your LonWorks devices and publish it as Metasys N2 data.
  • It can also write to the LonWorks devices.
  • This gateway can also do the reverse, read Metasys N2 data and publish it as LonWorks data.
  • It can also write to the Metasys N2 devices.

In summary, this gateway can act as:

  • Master on the LonWorks network: Hence it is capable of reading data from the various LonWorks slave devices and writing data to them if required.
  • Slave on the LonWorks network: You can use the gateway in this mode if you have a LonWorks master on the network which would be reading data from the gateway.
  • Client/Master on the Metasys N2 network: Hence it is capable of reading data from the various Metasys N2 devices and writing data to them if required.
  • Server/Slave on the Metasys N2 network: The gateway can be configured to be a server of data values; hence another Metasys N2 client can read data from the gateway and write data into the gateway.

Block Diagram:


Application Scenario 1
  • On a site you have several Cummins PCC Controllers on various diesel Generators that can provide data output on LonWorks.
  • The site has a Network Automation Engine on Metasys N2 that needs the energy data from the Controller.
  • Since the LonWorks Controller provides data output on LonWorks and the Network Automation Engine understands only Metasys N2 a direct data exchange is not possible.

Block Diagram:


Solution:

The devices can not directly communicate with each other as they are not on the same protocol. LonWorks and Metasys N2 are Serial based Protocol. You need something that will convert data from Metasys N2 device to LonWorks and vice versa.

ProtoConvert’s LonWorks to Metasys N2 converter will be an excellent solution for this requirement. The gateway reads data from the PCC Controller on LonWorks. It caches this data internally and then provides it on Metasys N2 when requested from the Network Automation Engine.

Application Scenario 2
  • On the other site we have controllers that can provide data output on Metasys N2.
  • The site has a PLC on LonWorks that needs the temperature data from controllers on Metasys N2.
  • Since the controllers provide data output on Metasys N2 and the PLC understands only LonWorks and a direct data exchange is not possible.

Block Diagram:


Solution:

The devices can not directly communicate with each other as they are not on the same protocol. LonWorks and Metasys N2 Serial based Protocol. You need something that will convert data from Metasys N2 to LonWorks and vice versa.

ProtoConvert’s LonWorks to Metasys N2 converter will be an excellent solution for this requirement. The gateway reads data from the controllers on Metasys N2. It caches this data internally and then provides it on LonWorks when requested from the PLC.



An Overview of the two protocols

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

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.