Application Notes

Metasys N2 Open by Johnson Controls

Metasys N2OPEN was developed by Johnson Controls as a network to interface their various devices and controllers. It is defined around the RS-485 set of data communications standards and runs at 9600 baud, 8 data bits, and no parity and in half-duplex mode. This network supports communications with a diverse range of devices manufactured by Johnson Controls and 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. FieldServer can act as the Master or Slave on the Metasys by Johnson Controls network depending upon the configuration.

Many Metasys N2 by Johnson Controls compatible devices use their own flavor of the protocol. The different flavors are designed to co-exist on the same Metasys N2 Johnson Controls network. Care must be taken to ensure the device of interest is covered by the FieldServer implementation. At present the FieldServer Metasys N2 by Johnson Controls driver will support communications with the following devices or classes of devices when acting as a client:

  • N2Open-compliant devices. N2Open is a published N2-compatible protocol enabling 3rd party device vendors to integrate with N2.
  • VMA 1400 series
  • DX9100 and XT9100

When acting as a server the FieldServer Metasys N2 by JCI driver can emulate an N2Open device only.

Devices that have been tested with FieldServer:

  • UNT
  • VMA1410,
  • VMA1420
  • DX9100 with XT9100 extension
  • LCP/DX9100
  • NCM (FieldServer as N2Open server)
  • VAV
  • AHU
  • VND

Available Metasys Drivers from FieldServer Technologies

AN005 -- Applying FieldServers in Building Automation Applications

Links

Using FieldServers in Metasys N2 Applications – A webinar presentation developed to train integrators in use of FieldServer in Metasys N2 applications

Connecting Metasys and BACnet Networks – A webinar presentation developed to train integrators in interfacing Metasys and BACnet networks