Search

Click for Help
or call 1-888-665-3678
or 1-704-849-2773


Click Send us Email

OPC Server for N2 Networks – Unlimited Tags



This item is no longer available for online ordering. See below for details on alternate products or products that may have superceded this item.

With the PiiGAB OPC Server you can link any HMI/SCADA or customer OPC Client application to building automation system devices that use the N2 and N2 Open protocols. This license provides connectivity for N2 capable devices for an unlimited number of tags.
OPC Self-Certified Logo The OPC server acts as a master on N2 network consisting of a mix of slave devices communicating using N2 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.

The OPC Server 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 masters, such as the NCM unit.

The server can handle multiple N2 networks simultaneously with 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.

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

This license imposes no limit on the number of tags/addresses you can access in your N2 protocol compatible devices. A 500 Tag license is available if you only need to access a limited number of tags/addresses.

An annual maintenance and support agreement is available for the OPC Server for N2 Networks – Unlimited Tags. Click here

Modes of Operation

The OPC server collects data by reading values from N2 and N2Open slaves. Reads are 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 a per-call basis.

Supported Functionality

Commands

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)
  • Write Analog Input (Region 1)
  • Read Binary Input (Region 2)
  • Write Binary Input (Region 2)
  • Read Analog Output (Region 3)
  • Write Analog Output (Region 3)
  • Read Binary Output (Region 4)
  • Write Binary Output (Region 4)
  • Read Internal Parameter (Regions 5,6,7)
  • Write Internal Parameter (Regions 5,6,7)
  • Override Analog Input
  • Override Binary Input
  • Override Analog Output
  • Override Binary Output
  • Override Internal Parameter
  • Override Release
  • Data Types

    N2 Protocol:

  • Unsigned 8 bit
  • Unsigned 16 bit
  • Unsigned 32 bit
  • Floating point (16 bit JC format)
  • Other types that can be mapped to types listed here
  • N2Open Protocol:

  • Byte (8 bit unsigned)
  • Integer (16 bit signed)
  • Integer (32 bit signed)
  • Float (32 bit IEEE format)
  • Connection Information

    Serial Port to N2 Network:

  • Baud Rate
  • Standard rates between 110-256K (Default: 9600)
  • Byte Size
  • Selectable 7 or 8 bits (Default: 8)
  • Parity
  • None/Odd/Even/Mark/Space (Default: None)
  • Stop Bits
  • 1, 1.5, 2 (Default: 1)
  • Handshaking
  • None/Hardware/Software (Default: None

    TCP/IP Socket to Ethernet/Serial Converter:

  • Host Address
  • Any numeric IP address, or symbolic DNS host name
  • Host Port
  • 1 - 65,535 (Default: 10001)

    Supported Devices

    N2 Protocol: DC-9100, DX9100, XT-9100 (through DX-9100), TC-9100

    N2Open Protocol: MR40, FX-15, FX-16, General Vendor Device

    Note: This is a non-exhaustive list of supported devices. Devices supporting the N2 or N2Open protocols should be compatible with this OPC Server. Please contact us if you have questions and your device is not listed.

    If you have devices in your building automation system, that are not N2/N2Open, we have drivers for BACNet/IP or our Building Automation Suite which includes the drivers for BACNet/IP and Modbus among others.

    Broad OPC Support

    The N2 OPC Server from PiiGAB implements the OPC 1.0, 2.0, and 3.0 Data Access Specifications giving you the choice of the widest range of OPC client applications.

    Requirements:

    Hardware

    • Any PC hardware compatible with the operating systems listed below.
    • Serial port(s) for RS-232 connection to slave devices, and/or 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

    • Microsoft Windows XP with Service Pack 2 or later (x86)
    • Microsoft Windows Vista with Service Pack 1 or later (x86)
    • Microsoft Windows 7 (x86)
    • Microsoft Windows Server 2003 with Service Pack 1 or later (x86)
    • Microsoft Windows Server 2008 (x86)

    Prerequisites

    • Microsoft .NET Framework 2.0 with Service Pack 1 (x86)
    • Microsoft .NET Framework 3.5 with Service Pack 1 (x86)

    Click here for the OPC Server for N2 Networks End-User License Agreement.

     

    Click to verify BBB accreditation and to see a BBB report.

    QUICK LINKS

    NEED HELP?

    CONNECT

    © Copyright Software Toolbox, Inc. 1996-2021, All Rights Reserved Worldwide.
    Usage subject to our Website Terms & Conditions and Privacy Policy
    BasketID= 6677375633BA4214B44E220FBA30FCD0

    1-888-665-3678 (US)

    +1-704-849-2773 (Global),

    +1-704-849-6388

    Who We Are
    Ask A Question
    How to Buy