The OPC server acts as a master on Johnson Controls Metasys N2 network consisting of a mix of slave devices communicating using N2 (original Johnson Controls protocol) or N2Open protocol. N2 and N2Open are Optomux-based protocols used in HVAC (Heating, Ventilation and Air Conditioning) and other building automation networks. The server supports DC, DX, FX, TC, VND and many other N2/N2Open devices, and is extensible using “hardware type definition” files.
Can be used to replace the NCM (Network Control Module) and enable OPC access to N2 slaves. Optionally, the OPC server can also pass through (forward) communication from other master, such as the NCM unit.
The server can handle multiple N2 networks simultaneously, and up to 255 slave devices on each network. The computer can connect to an N2 network via serial port, or using TCP through an Ethernet/serial convertor.
Configuration program with rich user interface is supplied with the server. You can use both the items pre-defined for a hardware type of your device, or add your own named items. The configuration is stored in an XML file. The server can run as Windows Service or Local Server.
Connection via serial
port:
Serial port may be internal, or external to the PC (e.g. connected by USB).
Connection using TCP through an Ethernet/serial convertor:
The OPC server collects data by reading values from N2 and N2Open slaves. The reading is one-shot (for OPC reads) and/or periodic (for OPC subscriptions). Multiple subscriptions to the same item are merged together.
OPC writes are transformed to N2 write commands on per call basis.
Any PC hardware compatible with operating systems listed below.
Serial communication port(s) for RS-232 connection to slave devices, and/or for connection to a master device for pass-through (if configured).
Ethernet network adapter(s) for connection with slave devices through Ethernet/serial convertor (if configured).
Operating system:
o Microsoft Windows XP with Service Pack 2 or later (x86)
o Microsoft Windows Vista with Service Pack 1 or later (x86, x64)
o Microsoft Windows 7 (x86, x64)
o Microsoft Windows Server 2003 with Service Pack 1 or later (x86)
o Microsoft Windows Server 2008 (x86, x64)
o Microsoft Windows Server 2008 R2 (x64)
Prerequisites:
§ Microsoft .NET Framework 2.0 with Service Pack 1 (x86)
§ Microsoft .NET Framework 3.5 with Service Pack 1 (x86)
Serial port to Metasys N2 network:
|
Setting |
Recommended
(default) |
Available |
|
Baud rate |
9,600 |
Standard
rates between 110-256,000 |
|
Byte size |
8 |
7/8 |
|
Parity |
None |
None/Odd/Even/Mark/Space |
|
Stop bits |
1 |
1/1.5/2 |
|
Handshaking |
None |
None/Hardware/Software |
TCP/IP socket to Ethernet/serial convertor:
|
Setting |
Recommended
(default) |
Available |
|
Host address |
(192.168.1.21) |
Any
numeric IP address, or symbolic DNS host name |
|
Host port |
10001 |
1-65535 |
N2 Protocol:
|
üSingle Item Read |
üSingle Item Write |
|
üExtended Single Item Read |
üExtended Single Item Write |
|
üFunctional Module Block Read |
üFunctional Module Block Write |
N2Open Protocol:
|
üRead Analog Input (Region 1) |
üRead Binary Input (Region 2) |
|
üRead Analog Output (Region 3) |
üRead Binary Output (Region 4) |
|
üRead Internal Parameter (Regions 5,6,7) |
üWrite Analog Input (Region 1) |
|
üWrite Binary Input (Region 2) |
üWrite Analog Output (Region 3) |
|
üWrite Binary Output (Region 4) |
üWrite Internal Parameter (Regions 5,6,7) |
|
üOverride Analog Input |
üOverride Binary Input |
|
üOverride Analog Output |
üOverride Binary Output |
|
üOverride Internal Parameter |
üOverride Release |
|
üIdentify Device Type (*) |
|
(*) issued automatically
N2 Protocol:
|
üFloating point number (16 bits JC format) |
üUnsigned 8 bits |
|
üUnsigned 16 bits |
üUnsigned 32 bits |
|
üOther types that can be mapped to types listed here |
|
N2Open Protocol:
|
üFloat (32 bits IEEE format) |
üInteger (16 bits signed) |
|
üInteger (32 bits signed) |
üByte (8 bits unsigned) |
|
Protocol |
Device
Model |
Abbre-viation |
Compati- bility |
Hardware Type
Definition Provided |
|
N2 |
Johnson
Controls DC-9100 Plant Controller |
DC9100 |
Assumed |
üYes |
|
N2 |
Johnson
Controls DX-9100 Extended Digital Plant Controller |
DX9100 |
üTested |
üYes |
|
N2
through DX9100 |
Johnson
Controls XT-9100 Extension Module |
|
Assumed |
üYes |
|
N2 |
Johnson
Controls TC-9100 Universal Controller |
TC9100 |
Assumed |
üYes |
|
N2
through TC9100 |
Johnson
Controls TM-9180 Room Command Module |
|
Assumed |
üYes |
|
N2 |
other
models |
|
Assumed |
No |
|
N2Open |
General
Vendor Device |
VND |
üTested |
üYes |
|
N2Open |
Johnson
Controls MR40 Advanced Electronic Control for compressor and defrost
management |
|
üTested |
üYes
(VND) |
|
N2Open |
IME
NEMO 96/35 Multimeter |
|
üTested |
üYes
(VND) |
|
N2Open |
Johnson
Controls FX-15 “Universal” Controller |
|
Assumed |
üYes
(VND) |
|
N2Open |
Johnson
Controls FX-16 Master Controller (multi-media programmable controller) |
|
Assumed |
üYes
(VND) |
|
N2Open |
other
models |
|
Assumed |
üYes
(VND) |
VND test represented by MR40 device. Single hardware type definition is provided for all VND devices.
The OPC server can pass through (forward) requests and responses from/to any Optomux-compatible master, including N2/N2Open serial masters.
Serial to N2 (RS-232/RS-485)
convertors:
|
Protocol |
Device
Model |
Compati- bility |
|
serial |
Johnson
Controls IU-9100 Interface Unit |
üTested |
|
serial |
other
models |
Assumed |
The convertor must support automatic DSC (Data Send Control).
Ethernet/serial convertors:
|
Protocol |
Device Model |
Compati- bility |
|
TCP |
Lantronix
UDS1100 |
üTested |
|
TCP |
Lantronix
UDS2100 |
Assumed |
|
TCP |
MOXA
NPort 5150 |
üTested |
|
TCP |
MOXA
NPort 5110 |
Assumed |
|
TCP |
other
models |
Assumed |
ü all OPC DA (Data Access) 2.0x Specifications (Released)
ü all OPC DA (Data Access) 3.0x Specifications (Released)
ü all OPC Common 1.0x Specifications (Released)
ü OPC UA (Universal Architecture) 1.00 Specifications for Data Access
ü OPC UA (Universal Architecture) 1.01 Specifications for Data Access
OPC clients can access the server locally, or remotely (over DCOM, or UA transport protocols).
Mark "Johnson Controls" and mark "Metasys" are owned by Johnson Controls, Inc. and/or its affiliates.
OPC Labs, s.r.o. or PiiGAB, Processinformation i Göteborg AB,
are not associated with Johnson Controls. Johnson Controls has not provided any
assistance in developing this product, and have not made determination that the
server is compatible with Johnson Controls' products.