You are here:   Products > Device Interfaces > BACnet®
Register   |  Login
BACnet® Interface

BACnet® Interface

Overview

The BACnet device interface provides the means to send a limited number of standard BACnet commands to control BACnet compliant equipment or controllers.  BACnet is an open protocol standard for building automation control systems.

The BACnet interface opens up your facility to hundreds of HVAC products and vendors that can be automatically scheduled and controlled directly from your event/room reservation system.

This particular device driver only supports BACnet/IP (Annex J) of the BACnet standard.  For more information about BACnet see the BACnet website.  Note: BACnet Ethernet (IEEE 802.3) will be supported at v1.0.6 and higher.

Network Architecture (BACnet/IP)

Available Actions

WriteProperty

The WriteProperty action sends a standard BACnet WriteProperty command to a BACnet object when an event item has been triggered.

This action only applies to the following event triggers:  EventStart, EventStop, EventSetupStart, EventSetupStop, EventTeardownStart, EventTeardownStop.

StartStop

The StartStop action sends a standard BACnet WriteProperty service command to a single BACnet object for each side (start and stop) of an event.  The Start value is sent to the object when an Event Start or Event Setup Start has been triggered.  The Stop value is sent to the object when an Event Stop or Event Teardown Stop has occurred.

This action only applies to the following event triggers:  EventStartStop, EventSetupTeardown

System Requirements

BACnet/IP (Annex J)

  • Windows 2003 R2, Windows XP, Windows 7
  • The PC or Server that the Events2HVAC windows service is running on must be able to access the BACnet LAN using BACnet/IP.
  • If the server is not on the same LAN segment as the BACnet/IP segment then server must be able to connect to a remote BBMD device located on the BACnet/IP segment.
  • If another vendor’s BACNet driver is running on an Events2HVAC client or server PC, one or both applications may not work together since BACNet uses a standard port 47808 to communicate.  Special setup will be necessary in this case.

BACnet Ethernet (IEEE 802.3)

  • BACnet Ethernet driver only works on 32-bit platforms
  • WinPCap installed on server
  • Windows 2003 R2 (x86), Windows XP (x86), Windows 7 (x86)
  • The PC or Server that the Events2HVAC windows service is running must be on the same BACnet LAN segment.   If the server is not on the same LAN segment as the BACnet segment then a BACnet router must be used on each segment.
  • If another vendor’s BACNet driver is running on an Events2HVAC client or server PC, one or both applications may not work together since BACNet uses a standard port 47808 to communicate.  Special setup will be necessary in this case.

 BACnet PICS Document


BACnet® is a registered trademark of American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE).

Device Interfaces

Minimize

BACnet®BACnet®

BACnet®

Device interface for BACnet® compliant systems.
JCI MSEAJCI MSEA

JCI MSEA

Device interface for the Johnson Controls MSEA web services.
JCI P2000JCI P2000

JCI P2000

Johnson Controls P2000 Card Access Interface
Proliphix NTProliphix NT

Proliphix NT

Proliphix NT/TM Series Network Thermostat
NetworkThermostat™NetworkThermostat™

NetworkThermostat™

Net/X by NetworkThermostat
CustomCustom

Custom

Custom Device Interface
Supported Devices ListSupported Devices List

Supported Devices List

List of all supported vendors and devices.