BACnet object support - Metasys - LIT-1201531 - System Integration - BACnet Controller Integration - 11.0

BACnet Controller Integration Technical Bulletin

Product name
BACnet Controller Integration
Document type
Technical Bulletin
Document number
Revision date

The Metasys system integrates and exposes objects as standard BACnet object types. The user configures and enables the BACnet Integration and Field Bus Integration feature in the supervisory controllers.

The Metasys system supports a subset of standard BACnet object types, but does not support integration of any proprietary object types in other BACnet devices. Of the supported standard BACnet objects, only the required and optional properties are viewable for non Metasys Series controllers (referred to as General BACnet Device in this document); proprietary properties are not supported.

The following list of BACnet object types are both those supported in the Metasys supervisory controllers for BACnet/Field Bus integration, and those exposed as BACnet objects to third-party BACnet devices that discover the supervisory controller. Refer to the Object Dictionary in online Help or the Network Engine Protocol Implementation Conformance Statement Technical Bulletin (LIT-1201532) for further details on objects supported.
Important: Electric Demand Control, Electric Demand Monitoring, and Generator Load Control objects are intended for use only in Japan.
  • Accumulator

  • Analog Input (AI)

  • Analog Output (AO)

  • Analog Value (AV)

  • Averaging

    Note: Averaging objects created in the NAE appear as extensions to the object that the average is associated with. When exposed to a third-party BACnet device, the extension appears as its own BACnet Averaging object.
  • Binary Input (BI)

  • Binary Output (BO)

  • Binary Value (BV)

  • Bitstring Value (ODS only)
  • Calendar

  • Characterstring Value

  • Command

  • Date Pattern Value (ODS only)
  • Date Time Pattern Value (ODS only)
  • Date Time Value (ODS only)
  • Date Value (ODS only)
  • Device (only the NAE/NCE/SNE/SNC exposes the Device object)

  • Event Enrollment

  • Electric Demand Control

  • Electric Demand Monitoring

  • File

  • Generator Load Control

  • Group

  • Integer Value

  • Large Analog Value (ODS only)

  • Life Safety Point

  • Life Safety Zone

  • Load Control

  • Loop

  • Multistate Input (MI)

  • Multistate Output (MO)

  • Multistate Value (MV)

  • Notification Class (Notification)

  • Octet String Value (ODS only)

  • Positive Integer Value

  • Program (the Metasys Control System object qualifies as a BACnet Program object)

  • Pulse Converter

  • Schedule

  • Time Pattern Value (ODS only)
  • Time Value (ODS only)
  • Trend

    Note: Trend objects created in the supervisory controllers appear as extensions to the object that the trend is associated with. When exposed to a third-party BACnet device, the extension appears as its own BACnet Trend object.
  • Trend Log Multiple

In the network engine, all mapped field points, including those on the N2 Bus, LonWorks® trunk as well as all field bus and BACnet integrated points are exposed as the corresponding BACnet objects types (AI, AO, BI, BO, MSI and so on) to third party BACnet devices. By default, the network engines do not allow routing messages to MS/TP devices connected to a network engine field bus. If you do enable routing, third party devices can map devices and their points connected to the local field buses.

Important: Do not enable routing during normal operation on NCE25, NAE35 or NAE45 series network engines as the increased traffic will likely increase offline/online event reporting.

See Enabling the routing mode.