The experiences of users and implementers of BACnet have led to many constructive suggestions for improving the original standard, ANSI/ASHRAE 135-1995 and, more recently, to its successors, ANSI/ASHRAE 135-2001, 135-2004 and 135-2008. The files available below are in Adobe Portable Document Format (PDF). Anyone wishing to comment on public review drafts during the listed comment period can get the necessary forms and instructions on the ASHRAE Website.
This Page was Last Updated on December 3, 2009
BACnet Protocol Version and Revision Numbers
With the publication of Addenda 135-2008j, l, o, r, s, v on June 20, 2009, the following apply:
| Version Number | = 1 |
| Revision Number | = 9 |
Addenda to BACnet-2008
Note: Many of the addenda to BACnet-2008 were begun during the "lifetime" of BACnet-2004 but their development and final public reviews were not completed in time to be incorporated into BACnet-2008. Therefore, some of the files for earlier drafts contain the string "2004" in their titles even though they pertain to revisions to BACnet that will eventually be applied to BACnet-2008 or, possibly, subsequent consolidated versions of the standard.
Published Addenda to BACnet-2004 (incorporated into BACnet-2008)
Published Addenda to BACnet-2001 (incorporated into BACnet-2004)
- Addendum 135-2001a
- Add Partial Day Scheduling to the Schedule object
- Enable reporting of proprietary events by the Event Enrollment object
- Allow detailed error reporting when all ReadPropertyMultiple accesses fail
- Remove the Recipient property from the Event Enrollment object
- Add the capability to issue I-Am responses on behalf of MS/TP slave devices
- Add a new silenced mode to the DeviceCommunicationControl service
- Add 21 new engineering units
- Specify the behavior of a BACnetArray when its size is changed
- Clarify the behavior of a BACnet router when it receives an unknown network message type
- Addendum 135-2001b
- Remove UTC timestamps from Trend Logs and guarantee Trend Log record ordering
- Addendum 135-2001c
- Allow Life Safety objects to advertise supported mode
- Add Unsilence Options to the LifeSafetyOperation Service
- Specify the relationship between the Event_Type and Event_Parameter properties
- Add a new Accumulator Object Type
- Add a new Pulse Converter Object Type
- Standardize event notification priorities
- Define Abort reason when insufficient segments are available
- Add new Error Codes and specify usage
- Addendum 135-2001d
- Add clauses describing BACnet-EIB/KNX mapping
Published Addenda to BACnet-1995 (incorporated into BACnet-2001)
- Addendum 135-1995a
- Add Annex J - BACnet/IP and supporting definitions
- Addendum 135-1995b
- Inconsistencies are eliminated in the definitions of the Analog and Binary Value object types
- Any device that receives and executes UnconfirmedEventNotification service requests must support programmable process identifiers
- Modify each event-generating object type to contain the last timestamp for each acknowledgeable transition
- Modify the Notification Class object by requiring that the 'Notification Class' property be equivalent to the instance number of the Notification Class object
- Modify the Event Notification services to make the 'To State' parameter mandatory for notifications of type ACK_NOTIFICATION
- A new BACnetDeviceObjectPropertyReference production is added and its use in the Event Enrollment and Schedule object types is specified
- Add a Multi-state Value object type
- Add an Averaging object type
- Change all 'Process Identifier' properties and parameters to Unsigned32
- Change the Multi-state Input object type to correct flaws related to fault detection and reporting and achieve consistency with the proposed Multi-state Value object type
- Add a Protocol_Revision property to the Device object type
- The File object type is changed to allow truncation and partial deletion operations
- A new ReadRange service is added to permit reading a range of data items from a property whose datatype is a list or array of lists
- A new UTCTimeSynchronization service is introduced and related changes are made to properties in the Device object type
- Add a Trend Log object type
- The UnconfirmedCOVNotification service is extended to allow notifications without prior subscription as a means of distributing globally important data to a potentially large number of recipients
- Add eight new BACnet engineering units
- Addendum 135-1995c
- Add a new Life Safety Point object type that represents the characteristics of initiating and indicating devices in the fire, life safety, and security applications
- Add a new Life Safety Zone object type that represents the characteristics associated with an arbitrary group of BACnet Life Safety Point and Life Safety Zone objects
- Add functionality to the existing BACnet alarm and event features needed to support the Life Safety Point and Life Safety Zone object types
- Add a new LifeSafetyOperation service that provides silence and reset capabilities needed for life safety systems
- Add a new subclause to 19 to describe the use of existing BACnet services to provide backup and restore capability
- Define a new service, SubscribeCOVProperty, to allow COV notifications for arbitrary properties of an object with subscriber-specified COV increments
- Add Vendor ID to proprietary MS/TP frames
- Add a new service, GetEventInformation, that provides enough information to acknowledge alarms
- Addendum 135-1995d
- Replace Clause 22 with a new clause entitled "Conformance and Interoperability"
- Update Annex A, "Protocol Implementation Conformance Statement"
- Add a new Annex K entitled "BACnet Interoperability Building Blocks (BIBBs)"
- Add a new Annex L entitled "Descriptions and Profiles of Standardized BACnet Devices"
- Addendum 135-1995e
- Define the PTP connection status when the half-router can and cannot re-establish the connection
- Add Object Profiles and Extensions
- Add the capability for devices to advertise the maximum number of segments of a segmented APDU that they can receive
Standard ANSI/ASHRAE 135.1
The need to define a set of procedures for the testing of BACnet implementations has led to the drafting of a companion standard, ANSI/ASHRAE 135.1, Method of Test for Conformance to BACnet. The companion standard to ANSI/ASHRAE Standard 135 (BACnet) contains detailed tests for every feature of the BACnet protocol and provides the basis for testing and listing programs that have been established by BACnet International, the successor organization to the BACnet Manufacturers Association.
Addenda to 135.1-2007
Published Addenda to 135.1-2003 (incorporated into 135.1-2007)
|