BACnet Wiki - User contributions [en]

BACnet Standard

2026-02-09T19:05:00Z

BACnetEd:

The BACnet Standard can be purchased from the ASHRAE Bookstore.

The official BACnet Website [https://bacnet.org/ is this].

For the official BACnet standard go to this link and search for "BACnet 135"

For the official BACnet *TEST* standard go to this link and search for "BACnet 135.1"

There is an online read-only version available via [https://www.ashrae.org/technical-resources/standards-and-guidelines/read-only-versions-of-ashrae-standards this link]. Go to this link and search for "135-2024"

BTL Procedure

2025-11-29T19:34:46Z

BACnetEd:

Here is a summary/checklist to get your device through the BTL certification process:

* Pre-test your device using our BACnet Test Suite
* Contact the 4 labs, ([https://btl.org/device-testing/#provider-section link here]) let them know that you are interested, confirm they can test your IUT (Implementation Under Test)
* Confirm they will test to Protocol Revision 26 (or perhaps higher)
* Confirm they will provide an estimate (quote) based on the "BTL Functionality Checklist" that you will fill in
* Find out when they can start testing, and estimate how long will it take
* Confirm Payment terms
* Ask for any other requirements they may have
* Complete the "BTL Functionality Checklist". The original is in the "BTL Test Package-26" which can be downloaded from the BTL website
* Send this to the candidate lab(s) and get a final estimate of the costs
* Contact BTL themselves and let them know your intent to start testing with the selected Lab, and ask them to initiate procedures for eventual registration. Someone, not sure who, I think BTL, will issue a TCxxxxxx number for tracking purposes.
* Ask BTL for additional guidance
* There will be additional fees for the "Certification" and "Listing". (You probably do want to be "Listed" on the BTL website (link) for marketing purposes (this link is well referenced by users). But you are able to proceed with just the certificate if desired).
* Select a Lab, proceed
* [https://www.bac-test.com/ BITS] can assist you with this process.

BTL Procedure

2025-11-29T19:32:17Z

BACnetEd: Created page with "Here is a summary/checklist to get your device through the BTL certification process: * Pre-test your device using our BACnet Test Suite * Contact the 4 labs, (link here) let them know that you are interested, confirm they can test your IUT (Implementation Under Test) * Confirm they will test to Protocol Revision 26 (or perhaps higher) * Confirm they will provide an estimate (quote) based on the "BTL Functionality Checklist" that you will fill in * Find out when they ca..."

Here is a summary/checklist to get your device through the BTL certification process:

* Pre-test your device using our BACnet Test Suite
* Contact the 4 labs, (link here) let them know that you are interested, confirm they can test your IUT (Implementation Under Test)
* Confirm they will test to Protocol Revision 26 (or perhaps higher)
* Confirm they will provide an estimate (quote) based on the "BTL Functionality Checklist" that you will fill in
* Find out when they can start testing, and estimate how long will it take
* Confirm Payment terms
* Ask for any other requirements they may have
* Complete the "BTL Functionality Checklist". The original is in the "BTL Test Package-26" which can be downloaded from the BTL website
* Send this to the candidate lab(s) and get a final estimate of the costs
* Contact BTL themselves and let them know your intent to start testing with the selected Lab, and ask them to initiate procedures for eventual registration. Someone, not sure who, I think BTL, will issue a TCxxxxxx number for tracking purposes.
* Ask BTL for additional guidance
* There will be additional fees for the "Certification" and "Listing". (You probably do want to be "Listed" on the BTL website (link) for marketing purposes (this link is well referenced by users). But you are able to proceed with just the certificate if desired).
* Select a Lab, proceed
* BITS can assist you with this process.

Main Page

2025-11-29T19:28:05Z

BACnetEd:

<big>'''The new BACnetWiki'''</big>

This is a reboot of the BACnet Wiki for consolidating thoughts and discussions around BACnet. Email me at '''edward@bac-test.com''' if needed

'''Resources'''
* [[BACnet Product Gallery]] - Equipment, tools, services
* [[BACnet Developer Resources]] - for BACnet Stack programmers
* [[BACnet User Resources]] - for those of us who use BACnet devices
* [[Facilities Manager Resources]] - for those responsible for a site containing hundreds or thousands of BACnet devices
* [[Resources for Beginners]]
* [[Installer Resources]] - help with installing BACnet systems

* The [[BACnet Standard]]
* [https://www.linkedin.com/groups/13566440/ BACnet Developers Group on LinkedIn]
* [[BACnet Protocol]]
* [[BIBBS - BACnet Interoperability Building Blocks]]
* [[BACnet Services Supported]]
* [[BACnet Addenda 135]]
* [[BACnet Addenda 135.1]]
* [[BACnet BTL Tests to final 135.1 Tracking]]
* [[BACnet Interpretations]]
* [[BTL Procedure | BTL Submittal Process]]
* [[BTL Resources]]
* [[BTL Test Plan]]
* [[BTL Implementation Guideline]]
* Proposed [[Diagnostic Object]]
* [[BACnet Best Practices]]
* [[BACnet Protocol Wish List]]
* [[BACnet MS/TP Best Practices]]
* [[RS-485 Polarity]]
* [[BACnet Organizations]]
* [[Book of Records]]

DM-R-B - Device Management - Restart

2025-11-29T12:20:44Z

BACnetEd: Created page with "2025-11-29 I have asked this question My reference: oi00192 Does a device *HAVE* to support sending a UCOV on restart? ... (Clause 19.3) "When a device is powered on, when it restarts due to a ReinitializeDevice service (ACTIVATE_CHANGES, COLDSTART or WARMSTART), or when it restarts for some other reason, the device shall transmit an UnconfirmedCOVNotification request. " (B-ASC and lesser devices are not required to support DM-BR-B, nor is DM-R-B listed, but the text..."

2025-11-29 I have asked this question
My reference: oi00192

Does a device *HAVE* to support sending a UCOV on restart? ... (Clause 19.3)

"When a device is powered on, when it restarts due to a ReinitializeDevice service (ACTIVATE_CHANGES, COLDSTART
or WARMSTART), or when it restarts for some other reason, the device shall transmit an UnconfirmedCOVNotification
request. "

(B-ASC and lesser devices are not required to support DM-BR-B, nor is DM-R-B listed, but the text above implies otherwise..., and any Network_Port modification, requiring an ACTIVATE_CHANGES will too)

Very small devices, if forced to do the above, are not going to maintain a writable, and by definition persistable, Restart_Notification_Recipients list, and thus will fall back to a broadcast UCOV, bringing us back to the "very busy network on site power-up" issue that caused the suppression of I-Ams on startups....

BIBBS - BACnet Interoperability Building Blocks

2025-11-29T12:19:44Z

BACnetEd:

{| class="wikitable"
|+ Table of BIBBs
|-
! BIBB !! Category !! Description
|-
| [[DM-R-B - Device Management - Restart|DM-R-B]] || Device Manaement || Restart
|}

BIBBS - BACnet Interoperability Building Blocks

2025-11-29T12:18:04Z

BACnetEd: Created page with "{| class="wikitable" |+ Table of BIBBs |- ! BIBB !! Description |- | DM-R-B || Restart |}"

{| class="wikitable"
|+ Table of BIBBs
|-
! BIBB !! Description
|-
| DM-R-B || Restart
|}

Main Page

2025-11-29T12:14:41Z

BACnetEd:

<big>'''The new BACnetWiki'''</big>

This is a reboot of the BACnet Wiki for consolidating thoughts and discussions around BACnet. Email me at '''edward@bac-test.com''' if needed

'''Resources'''
* [[BACnet Product Gallery]] - Equipment, tools, services
* [[BACnet Developer Resources]] - for BACnet Stack programmers
* [[BACnet User Resources]] - for those of us who use BACnet devices
* [[Facilities Manager Resources]] - for those responsible for a site containing hundreds or thousands of BACnet devices
* [[Resources for Beginners]]
* [[Installer Resources]] - help with installing BACnet systems

* The [[BACnet Standard]]
* [https://www.linkedin.com/groups/13566440/ BACnet Developers Group on LinkedIn]
* [[BACnet Protocol]]
* [[BIBBS - BACnet Interoperability Building Blocks]]
* [[BACnet Services Supported]]
* [[BACnet Addenda 135]]
* [[BACnet Addenda 135.1]]
* [[BACnet BTL Tests to final 135.1 Tracking]]
* [[BACnet Interpretations]]
* [[BTL Resources]]
* [[BTL Test Plan]]
* [[BTL Implementation Guideline]]
* Proposed [[Diagnostic Object]]
* [[BACnet Best Practices]]
* [[BACnet Protocol Wish List]]
* [[BACnet MS/TP Best Practices]]
* [[RS-485 Polarity]]
* [[BACnet Organizations]]
* [[Book of Records]]

BACnet Addenda 135.1

2025-11-22T12:26:47Z

BACnetEd:

{| class="wikitable"
|+ BACnet 135.1 Addenda
|-
! Addendum !! Date !! Description !! Link
|-
| 135.1-2023u || 30 May 2025 || EPICS format, DM_BR, BACnet/SC tests || [https://www.ashrae.org/file%20library/technical%20resources/standards%20and%20guidelines/standards%20addenda/135_1_2023_u_20250530.pdf link]
|}

BACnet Addenda 135.1

2025-11-22T12:24:00Z

BACnetEd: Created page with "{| class="wikitable" |+ BACnet 135.1 Addenda |- ! Header text !! Header text !! Header text |- | 135.1-2023u || 30 May 2025 || [https://www.ashrae.org/file%20library/technical%20resources/standards%20and%20guidelines/standards%20addenda/135_1_2023_u_20250530.pdf link] |}"

{| class="wikitable"
|+ BACnet 135.1 Addenda
|-
! Header text !! Header text !! Header text
|-
| 135.1-2023u || 30 May 2025 || [https://www.ashrae.org/file%20library/technical%20resources/standards%20and%20guidelines/standards%20addenda/135_1_2023_u_20250530.pdf link]
|}

BACnet Addenda

2025-09-25T13:49:58Z

BACnetEd:

BACnet Addenda can be found [https://www.ashrae.org/technical-resources/standards-and-guidelines/standards-addenda on the ASHRAE website]

{| class="wikitable"
|+ BACnet Addenda
|-
! Standard !! Addendum !! Description
|-
| 135-2016|| bj|| BACnet Secure Connect / BACnet/SC
|-
| 135-|| br|| Writing NULL to non-commandable properties must result in ACK
|}

RS-485 Polarity

2025-07-31T14:41:58Z

BACnetEd:

RS-485 comprises two signals, one that 'tracks' the UART logic levels (high voltage == 1, low voltage == 0). The other signal does the opposite. The meaning of these two signals has been polluted by chip and box vendors, which leads to a lot of confusion. A lot of further confusion arises when one considers the UART logic levels vs signal levels and labels. This article attempts to resolve the status, hopefully without adding to the confusion.

'''Basic Rule from the specification (and I have the actual specification)

* A > B means "binary 0 on the bus" or "ON".
* A < B means "binary 1 on the bus" or "OFF".

And A is non-inverting (and thus B is inverting)

'''Identifying 'A' and 'B' signals'''

Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit.

The A signal is the wire that, when in the idle state, is at a slightly higher voltage than the 'B' signal. This difference in voltage measurements is the result of the biasing and termination resistors of the circuit. See [https://en.wikipedia.org/wiki/RS-485#/media/File:Rs485-bias-termination.svg Wikipedia]

'''Identifying 'Mark/Idle' and 'Space' '''

Look at the data bits. The idle condition is always the 'mark' condition. The start bit is always a 'space'. Drawings on the internet are in conflict with each other and cannot be relied upon.

{| class="wikitable" style="text-align: center;"
|+ Nominal Terminology
|-
! Our Terminology !! Description !! Terminonlogy !! Data (UART) Representation !! When Idle
|-
| A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High
|-
| B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low
|}

{| class="wikitable" style="text-align: center;"
|+ Manufacturer's Labeling
|-
! Non-inverting !! Inverting !! Class !! Manufacturer examples !!
|-
| A || B || Nominal || BITS, FieldServer
|-
| + || - || Symbol || BACnet Specification || The non-inverting input of the
EIA-485 transceiver is designated in this specification as "plus" or "+"
|-
| RT+ || RT- || || EnOcean SmartServer IoT
|-
| + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300
|-
| B+ || A- || || MBS UBR-01 Mk II
|-
| 485+ || 485- || Symbol || FieldServer
|-
| U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]
|-
| B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]
|-
| A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485], AirBox
|-
| A || B || || [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf TI Polarity Conventions]
|-
| ? || ? || || KMC router, A- and B+, true polarity TBC
|}

The BACnet Specification (135 - 9.2.2) says: The non-inverting input of the
EIA-485 transceiver is designated in this specification as "plus" or "+" and the inverting input as "minus" or "-". It is recommended, but not required, that the black or red insulated wire of the twisted pair be designated as "plus" and the white, clear, or green insulated wire be designated as "minus."

TI has a very definitive [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf document], but one that has to be read carefully in terms of terminology. Read this document with the following table in mind. Note, according to TI (and our opinion), the [https://en.wikipedia.org/wiki/RS-485 Wikipedia article] on bus states is WRONG ! :

{| class="wikitable" style="text-align: center;"
|+ RS-485 Bus State Terminology
|-
! UART input/output !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 Bus Binary state
|-
| 1 || A > B|| Mark/Idle || On || Logic 0
|-
| 0 || A < B || Space || Off || Logic 1
|}

BACnet Addenda 135

2025-07-30T13:16:24Z

BACnetEd:

{| class="wikitable"
|+ Caption text
|-
! Addendum !! Topics !! Comment
|-
| 135-2012bb || ZeroConfig || Example
|}

BACnet Addenda 135

2025-07-30T13:16:11Z

BACnetEd: Created page with "{| class="wikitable" |+ Caption text |- ! Addendum !! Topics !! Comment |- | 135-2012bb || ZeroCcnfig || Example |}"

{| class="wikitable"
|+ Caption text
|-
! Addendum !! Topics !! Comment
|-
| 135-2012bb || ZeroCcnfig || Example
|}

PICS - Protocol Implementation Conformance Statement

2025-07-20T19:01:36Z

BACnetEd: Created page with "This document describes the BACnet implementation of your device, mainly for Systems Integrators to review for suitability for task. A template can be found here [https://bacnet.org/conformance-pics/ here]"

This document describes the BACnet implementation of your device, mainly for Systems Integrators to review for suitability for task.

A template can be found here [https://bacnet.org/conformance-pics/ here]

BACnet Test Suite - Top 10 Scores

2025-07-12T13:16:04Z

BACnetEd:

{| class="wikitable"
|+ Weighted Test Results
|-
! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Bayesian Score
|-
| 1 || SMC || FS-Router-BAC2 || V2.08n || || 78%
|-
| 2 || CCR || BASRouterLX || 1.43 || 2.0.0 || 78%
|-
| 3 || JCI || TEC3612-00 || 2.0.5.0200 || || 74%
|-
| 4 || JCI || MS-NCE25 || 6.2.2.6 || || 74%
|-
| 5 || MBS || UBR-01 / MK II || 1.23.0.1 || 6.0.0.0 || 73%
|-
| 6 || JCI || MS-VMA1620-0 || 6.2.2.6 || || 73%
|-
| 7 || ASI || 9540 || 3.6.119 || || 72%
|-
| 8 || JCI || MS-NCE2566-0 || 9.0.7.7978 || || 69%
|-
| 9 || Steve Karg || bacnet-stack || 1.4.1 || || 65%
|-
| 10 || JCI || TL-BRTRP-0 || 2.0.22 || || 52%
|}

Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]

BACnet Test Suite - Top 10 Scores

2025-07-12T11:13:10Z

BACnetEd:

{| class="wikitable"
|+ Weighted Test Results
|-
! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Bayesian Score
|-
| 1 || CCR || BASRouterLX || 1.43 || 2.0.0 || 78%
|-
| 2 || JCI || TEC3612-00 || 2.0.5.0200 || || 74%
|-
| 3 || JCI || MS-NCE25 || 6.2.2.6 || || 74%
|-
| 4 || MBS || UBR-01 / MK II || 1.23.0.1 || 6.0.0.0 || 73%
|-
| 5 || JCI || MS-VMA1620-0 || 6.2.2.6 || || 73%
|-
| 6 || ASI || 9540 || 3.6.119 || || 72%
|-
| 7 || JCI || MS-NCE2566-0 || 9.0.7.7978 || || 69%
|-
| 8 || Steve Karg || bacnet-stack || 1.4.1 || || 65%
|-
| 9 || Steve Karg || mods4bts || 1.4.1 || || 65%
|-
| 10 || JCI || TL-BRTRP-0 || 2.0.22 || || 52%
|}

Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]

BTL Resources

2025-07-10T17:01:16Z

BACnetEd:

* Minimum acceptable Protocol Revisions for submittal to BTL [https://btl.org/news/minimum-protocol-revision-changes-january-1-2025/ link - 2025]
* BTL Testing Policies [https://btl.org/testing-documentation/ link]

BACnet Test Suite - Top 10 Scores

2025-07-08T12:14:45Z

BACnetEd:

{| class="wikitable"
|+ Weighted Test Results
|-
! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Bayesian Score
|-
| 1 || CCR || BASRouterLX || 1.43 || 2.0.0 || 75%
|-
| 2 || MBS || UBR-01 / MK II || 1.23.0.1 || 6.0.0.0 || 71%
|-
| 3 || ASI || 9540 || 3.6.119 || || 70%
|-
| 4 || Steve Karg || bacnet-stack || 1.4.1 || || 63%
|-
| 5 || Steve Karg || mods4bts || 1.4.1 || || 63%
|}

Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]

BACnet Test Suite - Top 10 Scores

2025-07-08T12:14:19Z

BACnetEd:

{| class="wikitable"
|+ Weighted Test Results
|-
! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Score
|-
| 1 || CCR || BASRouterLX || 1.43 || 2.0.0 || 75%
|-
| 2 || MBS || UBR-01 / MK II || 1.23.0.1 || 6.0.0.0 || 71%
|-
| 3 || ASI || 9540 || 3.6.119 || || 70%
|-
| 4 || Steve Karg || bacnet-stack || 1.4.1 || || 63%
|-
| 5 || Steve Karg || mods4bts || 1.4.1 || || 63%
|}

Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]

BACnet Test Suite - Top 10 Scores

2025-07-08T12:12:49Z

BACnetEd:

{| class="wikitable"
|+ Weighted Test Results
|-
! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Score
|-
| 1 || CCR || BASRouterLX || 1.43 || 2.0.0 || 75%
|-
| 2 || MBS || UBR-01 / MK II || 1.23.0.1 || 6.0.0.0 || 71%
|-
| 3 || Steve Karg || bacnet-stack || 1.4.1 || || 63%
|-
| 4 || Steve Karg || mods4bts || 1.4.1 || || 63%
|}

Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]

BACnet Test Suite - Top 10 Scores

2025-07-07T23:12:36Z

BACnetEd:

{| class="wikitable"
|+ Weighted Test Results
|-
! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Score
|-
| 1 || CCR || BASRouterLX || 1.43 || 2.0.0 || 75%
|-
| 2 || MBS || UBR-01 / MK II || 1.23.0.1 || 6.0.0.0 || 71%
|-
| 3 || Steve Karg || bacnet-stack || 1.4.1 || || 63%
|}

Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]

BACnet Test Suite - Top 10 Scores

2025-07-07T23:12:00Z

BACnetEd:

{| class="wikitable"
|+ Weighted Test Results
|-
! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Score
|-
| 1 || CCR || BASRouterLX || 1.43 || 2.0.0 || 75%
|-
| 2 || MBS || UBR-01 | MK II || 1.23.0.1 || 6.0.0.0 || 71%
|-
| 3 || Steve Karg || bacnet-stack || 1.4.1 || || 63%
|}

Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]

BACnet Test Suite - Top 10 Scores

2025-07-07T23:11:05Z

BACnetEd:

{| class="wikitable"
|+ Weighted Test Results
|-
! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Score
|-
| 1 || CCR || BASRouterLX || 1.43 || 2.0.0 || 75%
|-
| 2 || MBS || UBR-01 | MK II || 1.23.0.1 || 6.0.0.0 || 71%
|-
| 3 || bacnet-stack || 1.4.1 || || 63%
|}

Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]

BACnet Test Suite - Top 10 Scores

2025-07-07T20:35:50Z

BACnetEd:

{| class="wikitable"
|+ Weighted Test Results
|-
! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Score
|-
| 1 || MBS || UBR-01 | MK II || 1.23.0.1 || 6.0.0.0 || 189
|-
| 2 || CCR || BASRouterLX || 1.43 || 2.0.0 || 174
|}

Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]

BACnet Test Suite - Top 10 Scores

2025-07-07T20:35:08Z

BACnetEd:

{| class="wikitable"
|+ Weighted Test Results
|-
! Manufacturer !! Model !! FW Ver !! App Ver !! Score
|-
| MBS || UBR-01 | MK II || 1.23.0.1 || 6.0.0.0 || 189
|-
| CCR|| BASRouterLX || 1.43 || 2.0.0 || 174
|}

Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]

BACnet Test Suite - Top 10 Scores

2025-07-07T20:25:03Z

BACnetEd: Created page with "{| class="wikitable" |+ Weighted Test Results |- ! Manufacturer !! VID !! Model !! FW Ver !! App Ver !! Router !! App !! Hybrid |- | MBS || || UBR-01 | MK II || 1.23.0.1 || 6.0.0.0 || 60% || 76% || x |- | CCR|| || BASRouterLX || 1.43 || 2.0.0 || || || 78% |} Calculations done here"

{| class="wikitable"
|+ Weighted Test Results
|-
! Manufacturer !! VID !! Model !! FW Ver !! App Ver !! Router !! App !! Hybrid
|-
| MBS || || UBR-01 | MK II || 1.23.0.1 || 6.0.0.0 || 60% || 76% || x
|-
| CCR|| || BASRouterLX || 1.43 || 2.0.0 || || || 78%
|}

Calculations done here

BACnet BTL Tests to final 135.1 Tracking

2025-07-02T13:48:08Z

BACnetEd:

{| class="wikitable"
|+ Test Plan Cross Reference
|-
! BTL Temp Number !! 135.1 Final !! Description
|-
| 9.22.1.x2 || 9.22.1.5 || Writing to Properties Based on Data Type
|-
| 10.2.102 || 10.2.x2 || Routers Execute What-Is-Network-Number
|-
| 10.2.x2 || 10.2.8 || Routers Execute What-Is-Network-Number
|}

BACnet Standard

2025-07-02T09:44:13Z

BACnetEd:

The BACnet Standard can be purchased from the ASHRAE Bookstore.

The official BACnet Website [https://bacnet.org/ is this]. Go to this link and search for "135-2024"

There is an online read-only version available via [https://www.ashrae.org/technical-resources/standards-and-guidelines/read-only-versions-of-ashrae-standards this link]. Go to this link and search for "135-2024"

BACnet BTL Tests to final 135.1 Tracking

2025-07-01T15:57:15Z

BACnetEd:

{| class="wikitable"
|+ Test Plan Cross Reference
|-
! BTL Temp Number !! 135.1 Final !! Description
|-
| 10.2.102 || 10.2.x2 || Routers Execute What-Is-Network-Number
|-
| 10.2.x2 || 10.2.8 || Routers Execute What-Is-Network-Number
|}

BACnet BTL Tests to final 135.1 Tracking

2025-07-01T15:56:08Z

BACnetEd:

{| class="wikitable"
|+ Test Plan Cross Reference
|-
! BTL Temp Number !! 135.1 Final !! Description
|-
| 10.2.x2 || 10.2.8 || Routers Execute What-Is-Network-Number
|}

BACnet BTL Tests to final 135.1 Tracking

2025-07-01T15:55:39Z

BACnetEd: Created page with "{| class="wikitable" |+ Test Plan Cross Reference |- ! BTL Temp Number !! 135.1 Final !! Description |- | 10.2.x2 || 1.2.8 || Routers Execute What-Is-Network-Number |}"

{| class="wikitable"
|+ Test Plan Cross Reference
|-
! BTL Temp Number !! 135.1 Final !! Description
|-
| 10.2.x2 || 1.2.8 || Routers Execute What-Is-Network-Number
|}

Main Page

2025-07-01T15:53:55Z

BACnetEd:

<big>'''The new BACnetWiki'''</big>

This is a reboot of the BACnet Wiki for consolidating thoughts and discussions around BACnet. Email me at '''edward@bac-test.com''' if needed

'''Resources'''
* [[BACnet Product Gallery]] - Equipment, tools, services
* [[BACnet Developer Resources]] - for BACnet Stack programmers
* [[BACnet User Resources]] - for those of us who use BACnet devices
* [[Facilities Manager Resources]] - for those responsible for a site containing hundreds or thousands of BACnet devices
* [[Resources for Beginners]]
* [[Installer Resources]] - help with installing BACnet systems

* The [[BACnet Standard]]
* [https://www.linkedin.com/groups/13566440/ BACnet Developers Group on LinkedIn]
* [[BACnet Protocol]]
* [[BACnet Services Supported]]
* [[BACnet Addenda 135]]
* [[BACnet Addenda 135.1]]
* [[BACnet BTL Tests to final 135.1 Tracking]]
* [[BACnet Interpretations]]
* [[BTL Resources]]
* [[BTL Test Plan]]
* [[BTL Implementation Guideline]]
* Proposed [[Diagnostic Object]]
* [[BACnet Best Practices]]
* [[BACnet Protocol Wish List]]
* [[BACnet MS/TP Best Practices]]
* [[RS-485 Polarity]]
* [[BACnet Organizations]]
* [[Book of Records]]

Main Page

2025-07-01T15:52:53Z

BACnetEd:

<big>'''The new BACnetWiki'''</big>

This is a reboot of the BACnet Wiki for consolidating thoughts and discussions around BACnet. Email me at '''edward@bac-test.com''' if needed

'''Resources'''
* [[BACnet Product Gallery]] - Equipment, tools, services
* [[BACnet Developer Resources]] - for BACnet Stack programmers
* [[BACnet User Resources]] - for those of us who use BACnet devices
* [[Facilities Manager Resources]] - for those responsible for a site containing hundreds or thousands of BACnet devices
* [[Resources for Beginners]]
* [[Installer Resources]] - help with installing BACnet systems

* The [[BACnet Standard]]
* [https://www.linkedin.com/groups/13566440/ BACnet Developers Group on LinkedIn]
* [[BACnet Protocol]]
* [[BACnet Services Supported]]
* [[BACnet Addenda 135]]
* [[BACnet Addenda 135.1]]
* [[BACnet Interpretations]]
* [[BTL Resources]]
* [[BTL Test Plan]]
* [[BTL Implementation Guideline]]
* Proposed [[Diagnostic Object]]
* [[BACnet Best Practices]]
* [[BACnet Protocol Wish List]]
* [[BACnet MS/TP Best Practices]]
* [[RS-485 Polarity]]
* [[BACnet Organizations]]
* [[Book of Records]]

BACnet Services Supported

2025-07-01T15:47:30Z

BACnetEd:

{| class="wikitable sortable"
|+ BACnet Services Supported
|-
! Service !! Category !! Description !! Addendum !! Protocol_Revision !!
|-
| 0 || Alarm and Event Services || ACKNOWLEDGE_ALARM || || ||
|-
| 1 || Alarm and Event Services || CONFIRMED_COV_NOTIFICATION || || ||
|-
| 2 || Alarm and Event Services || CONFIRMED_EVENT_NOTIFICATION || || ||
|-
| 3 || Alarm and Event Services || GET_ALARM_SUMMARY || || ||
|-
| 4 || Alarm and Event Services || GET_ENROLLMENT_SUMMARY || || ||
|-
| 5 || Alarm and Event Services || SUBSCRIBE_COV || || ||
|-
| 6 || File Access Services || ATOMIC_READ_FILE || || ||
|-
| 7 || File Access Services || ATOMIC_WRITE_FILE || || ||
|-
| 8 || Object Access || ADD_LIST_ELEMENT || || ||
|-
| 9 || Object Access || REMOVE_LIST_ELEMENT || || ||
|-
| 10 || Object Access || CREATE_OBJECT || || ||
|-
| 11 || Object Access || DELETE_OBJECT || || ||
|-
| 12 || Object Access || READ_PROPERTY || || ||
|-
| 13 || Object Access || READ_PROP_CONDITIONAL || || ||
|-
| 14 || Object Access || READ_PROP_MULTIPLE || || ||
|-
| 15 || Object Access || WRITE_PROPERTY || || ||
|-
| 16 || Object Access || WRITE_PROP_MULTIPLE || || ||
|-
| 17 || Remote Device Management || DEVICE_COMMUNICATION_CONTROL || || ||
|-
| 18 || Remote Device Management || PRIVATE_TRANSFER || || ||
|-
| 19 || Remote Device Management || TEXT_MESSAGE || || ||
|-
| 20 || Remote Device Management || REINITIALIZE_DEVICE || || ||
|-
| 21 || Virtual Terminal || VT_OPEN || || ||
|-
| 22 || Virtual Terminal || VT_CLOSE || || ||
|-
| 23 || Virtual Terminal || VT_DATA || || ||
|-
| 24 || Security || AUTHENTICATE || || ||
|-
| 25 || Security || REQUEST_KEY || || ||
|-
| 26 || Unconfirmed || I_AM || || ||
|-
| 27 || Unconfirmed || I_HAVE || || ||
|-
| 28 || Unconfirmed || UNCONFIRMED_COV_NOTIFICATION || || ||
|-
| 29 || Unconfirmed || UNCONFIRMED_EVENT_NOTIFICATION || || ||
|-
| 30 || Unconfirmed || UNCONFIRMED_PRIVATE_TRANSFER || || ||
|-
| 31 || Unconfirmed || UNCONFIRMED_TEXT_MESSAGE || || ||
|-
| 32 || Unconfirmed || TIME_SYNCHRONIZATION || || ||
|-
| 33 || Unconfirmed || WHO_HAS || || ||
|-
| 34 || Unconfirmed || WHO_IS || || ||
|-
| 35 || Object Access || READ_RANGE || || ||
|-
| 36 || Unconfirmed || UTC_TIME_SYNCHRONIZATION || 135-1995 addendum b || 1
|-
| 37 || Alarm and Event Services || LIFE_SAFETY_OPERATION || 135-1995 addendum c || 2
|-
| 38 || Alarm and Event Services || SUBSCRIBE_COV_PROPERTY || || 2
|-
| 39 || Alarm and Event Services || GET_EVENT_INFORMATION || || 2
|-
| 40 || Object Access || WRITE_GROUP || 135-2010 addendum aa || 14
|-
| 41 || Alarm and Event Services || SUBSCRIBE_COV_PROPERTY_MULTIPLE || || ||
|-
| 42 || Alarm and Event Services || CONFIRMED_COV_NOTIFICATION_MULTIPLE || || ||
|-
| 43 || Unconfirmed || UNCONFIRMED_COV_NOTIFICATION_MULTIPLE || || ||
|-
| 44 || Alarm and Event Services || CONFIRMED_AUDIT_NOTIFICATION || || 20 ||
|-
| 45 || Alarm and Event Services || AUDIT_LOG_QUERY || || 20 ||
|-
| 46 || Unconfirmed || UNCONFIRMED_AUDIT_NOTIFICATION || || 20 ||
|-
| 47 || Remote Device Management || WHO_AM_I || 135-2016 Addendum bz || 22 ||
|-
| 48 || Remote Device Management || YOU_ARE || 135-2016 Addendum bz || 22 ||
|}

Main Page

2025-07-01T14:05:55Z

BACnetEd:

<big>'''The new BACnetWiki'''</big>

This is a reboot of the BACnet Wiki for consolidating thoughts and discussions around BACnet. Email me at '''edward@bac-test.com''' if needed

'''Resources'''
* [[BACnet Product Gallery]] - Equipment, tools, services
* [[BACnet Developer Resources]] - for BACnet Stack programmers
* [[BACnet User Resources]] - for those of us who use BACnet devices
* [[Facilities Manager Resources]] - for those responsible for a site containing hundreds or thousands of BACnet devices
* [[Resources for Beginners]]
* [[Installer Resources]] - help with installing BACnet systems

* The [[BACnet Standard]]
* [https://www.linkedin.com/groups/13566440/ BACnet Developers Group on LinkedIn]
* [[BACnet Protocol]]
* [[BTL Resources]]
* [[BTL Implementation Guideline]]
* Proposed [[Diagnostic Object]]
* [[BACnet Best Practices]]
* [[BACnet Protocol Wish List]]
* [[BACnet MS/TP Best Practices]]
* [[RS-485 Polarity]]
* [[BACnet Organizations]]
* [[Book of Records]]

RS-485 Polarity

2025-07-01T13:46:51Z

BACnetEd:

RS-485 comprises two signals, one that 'tracks' the UART logic levels (high voltage == 1, low voltage == 0). The other signal does the opposite. The meaning of these two signals has been polluted by chip and box vendors, which leads to a lot of confusion. A lot of further confusion arises when one considers the UART logic levels vs signal levels and labels. This article attempts to resolve the status, hopefully without adding to the confusion.

'''Basic Rule from the specification (and I have the actual specification)

* A > B means "binary 0 on the bus" or "ON".
* A < B means "binary 1 on the bus" or "OFF".

And A is non-inverting (and thus B is inverting)

'''Identifying 'A' and 'B' signals'''

Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit.

The A signal is the wire that, when in the idle state, is at a slightly higher voltage than the 'B' signal. This difference in voltage measurements is the result of the biasing and termination resistors of the circuit. See [https://en.wikipedia.org/wiki/RS-485#/media/File:Rs485-bias-termination.svg Wikipedia]

'''Identifying 'Mark/Idle' and 'Space' '''

Look at the data bits. The idle condition is always the 'mark' condition. The start bit is always a 'space'. Drawings on the internet are in conflict with each other and cannot be relied upon.

{| class="wikitable" style="text-align: center;"
|+ Nominal Terminology
|-
! Our Terminology !! Description !! Terminonlogy !! Data (UART) Representation !! When Idle
|-
| A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High
|-
| B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low
|}

{| class="wikitable" style="text-align: center;"
|+ Manufacturer's Labeling
|-
! Non-inverting !! Inverting !! Class !! Manufacturer examples !!
|-
| A || B || Nominal || BITS, FieldServer
|-
| + || - || Symbol || BACnet Specification || The non-inverting input of the
EIA-485 transceiver is designated in this specification as "plus" or "+"
|-
| RT+ || RT- || || EnOcean SmartServer IoT
|-
| + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300
|-
| B+ || A- || || MBS UBR-01 Mk II
|-
| 485+ || 485- || Symbol || FieldServer
|-
| U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]
|-
| B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]
|-
| A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485]
|-
| A || B || || [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf TI Polarity Conventions]
|}

The BACnet Specification (135 - 9.2.2) says: The non-inverting input of the
EIA-485 transceiver is designated in this specification as "plus" or "+" and the inverting input as "minus" or "-". It is recommended, but not required, that the black or red insulated wire of the twisted pair be designated as "plus" and the white, clear, or green insulated wire be designated as "minus."

TI has a very definitive [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf document], but one that has to be read carefully in terms of terminology. Read this document with the following table in mind. Note, according to TI (and our opinion), the [https://en.wikipedia.org/wiki/RS-485 Wikipedia article] on bus states is WRONG ! :

{| class="wikitable" style="text-align: center;"
|+ RS-485 Bus State Terminology
|-
! UART input/output !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 Bus Binary state
|-
| 1 || A > B|| Mark/Idle || On || Logic 0
|-
| 0 || A < B || Space || Off || Logic 1
|}

RS-485 Polarity

2025-06-29T23:03:05Z

BACnetEd:

RS-485 comprises two signals, one that 'tracks' the UART logic levels (high voltage == 1, low voltage == 0). The other signal does the opposite. The meaning of these two signals has been polluted by chip and box vendors, which leads to a lot of confusion. A lot of further confusion arises when one considers the UART logic levels vs signal levels and labels. This article attempts to resolve the status, hopefully without adding to the confusion.

'''Basic Rule from the specification (and I have the actual specification)

* A > B means "binary 0 on the bus" or "ON".
* A < B means "binary 1 on the bus" or "OFF".

And A is non-inverting (and thus B is inverting)

'''Identifying 'A' and 'B' signals'''

Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit.

The A signal is the wire that, when in the idle state, is at a slightly higher voltage than the 'B' signal. This difference in voltage measurements is the result of the biasing and termination resistors of the circuit. See [https://en.wikipedia.org/wiki/RS-485#/media/File:Rs485-bias-termination.svg Wikipedia]

'''Identifying 'Mark/Idle' and 'Space' '''

Look at the data bits. The idle condition is always the 'mark' condition. The start bit is always a 'space'. Drawings on the internet are in conflict with each other and cannot be relied upon.

{| class="wikitable" style="text-align: center;"
|+ Nominal Terminology
|-
! Our Terminology !! Description !! Terminonlogy !! Data (UART) Representation !! When Idle
|-
| A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High
|-
| B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low
|}

{| class="wikitable" style="text-align: center;"
|+ Manufacturer's Labeling
|-
! Non-inverting !! Inverting !! Class !! Manufacturer examples
|-
| A || B || Nominal || BITS, FieldServer
|-
| + || - || Symbol || BACnet Specification
|-
| RT+ || RT- || || EnOcean SmartServer IoT
|-
| + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300
|-
| B+ || A- || || MBS UBR-01 Mk II
|-
| 485+ || 485- || Symbol || FieldServer
|-
| U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]
|-
| B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]
|-
| A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485]
|-
| A || B || || [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf TI Polarity Conventions]
|}

The BACnet Specification (135 - 9.2.2) says: The non-inverting input of the
EIA-485 transceiver is designated in this specification as "plus" or "+" and the inverting input as "minus" or "-". It is recommended, but not required, that the black or red insulated wire of the twisted pair be designated as "plus" and the white, clear, or green insulated wire be designated as "minus."

TI has a very definitive [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf document], but one that has to be read carefully in terms of terminology. Read this document with the following table in mind. Note, according to TI (and our opinion), the [https://en.wikipedia.org/wiki/RS-485 Wikipedia article] on bus states is WRONG ! :

{| class="wikitable" style="text-align: center;"
|+ RS-485 Bus State Terminology
|-
! UART input/output !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 Bus Binary state
|-
| 1 || A > B|| Mark/Idle || On || Logic 0
|-
| 0 || A < B || Space || Off || Logic 1
|}

RS-485 Polarity

2025-06-29T20:16:37Z

BACnetEd:

RS-485 comprises two signals, one that 'tracks' the UART logic levels (high voltage == 1, low voltage == 0). The other signal does the opposite. The meaning of these two signals has been polluted by chip and box vendors, which leads to a lot of confusion. A lot of further confusion arises when one considers the UART logic levels vs signal levels and labels. This article attempts to resolve the status, hopefully without adding to the confusion.

'''Basic Rule from the specification

* A > B means the line is logic '1' (MARK).
* A < B means the line is logic '0' (SPACE).

'''Identifying 'A' and 'B' signals'''

Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit.

The A signal is the wire that, when in the idle state, is at a slightly higher voltage than the 'B' signal. This difference in voltage measurements is the result of the biasing and termination resistors of the circuit. See [https://en.wikipedia.org/wiki/RS-485#/media/File:Rs485-bias-termination.svg Wikipedia]

'''Identifying 'Mark/Idle' and 'Space' '''

Look at the data bits. The idle condition is always the 'mark' condition. The start bit is always a 'space'. Drawings on the internet are in conflict with each other and cannot be relied upon.

{| class="wikitable" style="text-align: center;"
|+ Nominal Terminology
|-
! Our Terminology !! Description !! Terminonlogy !! Data (UART) Representation !! When Idle
|-
| A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High
|-
| B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low
|}

{| class="wikitable" style="text-align: center;"
|+ Manufacturer's Labeling
|-
! Non-inverting !! Inverting !! Class !! Manufacturer examples
|-
| A || B || Nominal || BITS, FieldServer
|-
| + || - || Symbol || BACnet Specification
|-
| RT+ || RT- || || EnOcean SmartServer IoT
|-
| + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300
|-
| B+ || A- || || MBS UBR-01 Mk II
|-
| 485+ || 485- || Symbol || FieldServer
|-
| U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]
|-
| B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]
|-
| A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485]
|-
| A || B || || [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf TI Polarity Conventions]
|}

The BACnet Specification (135 - 9.2.2) says: The non-inverting input of the
EIA-485 transceiver is designated in this specification as "plus" or "+" and the inverting input as "minus" or "-". It is recommended, but not required, that the black or red insulated wire of the twisted pair be designated as "plus" and the white, clear, or green insulated wire be designated as "minus."

TI has a very definitive [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf document], but one that has to be read carefully in terms of terminology. Read this document with the following table in mind. Note, according to TI (and our opinion), the [https://en.wikipedia.org/wiki/RS-485 Wikipedia article] on bus states is WRONG ! :

{| class="wikitable" style="text-align: center;"
|+ RS-485 Bus State Terminology
|-
! UART input/output !! Logic level !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 A volt !! RS-485 B volt
|-
| 1 || high|| A > B|| Mark/Idle || On || high || low
|-
| 0 || low || A < B || Space || Off || low || high
|}

RS-485 Polarity

2025-06-29T20:02:51Z

BACnetEd:

RS-485 comprises two signals, one that 'tracks' the UART logic levels (high voltage == 1, low voltage == 0). The other signal does the opposite. The meaning of these two signals has been polluted by chip and box vendors, which leads to a lot of confusion. A lot of further confusion arises when one considers the UART logic levels vs signal levels and labels. This article attempts to resolve the status, hopefully without adding to the confusion.

'''Basic Rule from the specification

* A > B means the line is logic '1' (MARK).
* A < B means the line is logic '0' (SPACE).

'''Identifying 'A' and 'B' signals'''

Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit.

The A signal is the wire that, when in the idle state, is at a slightly higher voltage than the 'B' signal. This difference in voltage measurements is the result of the biasing and termination resistors of the circuit. See [https://en.wikipedia.org/wiki/RS-485#/media/File:Rs485-bias-termination.svg Wikipedia]

'''Identifying 'Mark/Idle' and 'Space' '''

Look at the data bits. The idle condition is always the 'mark' condition. The start bit is always a 'space'. Drawings on the internet are in conflict with each other and cannot be relied upon.

{| class="wikitable" style="text-align: center;"
|+ Nominal Terminology
|-
! Our Terminology !! Description !! Terminonlogy !! Data (UART) Representation !! When Idle
|-
| A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High
|-
| B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low
|}

{| class="wikitable" style="text-align: center;"
|+ Manufacturer's Labeling
|-
! Non-inverting !! Inverting !! Class !! Manufacturer examples
|-
| A || B || Nominal || BITS, FieldServer
|-
| + || - || Symbol || BACnet Specification
|-
| RT+ || RT- || || EnOcean SmartServer IoT
|-
| + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300
|-
| B+ || A- || || MBS UBR-01 Mk II
|-
| 485+ || 485- || Symbol || FieldServer
|-
| U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]
|-
| B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]
|-
| A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485]
|-
| A || B || || [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf TI Polarity Conventions]
|}

TI has a very definitive [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf document], but one that has to be read carefully in terms of terminology. Read this document with the following table in mind. Note, according to TI (and our opinion), the [https://en.wikipedia.org/wiki/RS-485 Wikipedia article] on bus states is WRONG ! :

{| class="wikitable" style="text-align: center;"
|+ RS-485 Bus State Terminology
|-
! UART input/output !! Logic level !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 A volt !! RS-485 B volt
|-
| 1 || high|| A > B|| Mark/Idle || On || high || low
|-
| 0 || low || A < B || Space || Off || low || high
|}

RS-485 Polarity

2025-06-29T20:00:59Z

BACnetEd:

RS-485 comprises two signals, one that 'tracks' the UART logic levels (high voltage == 1, low voltage == 0). The other signal does the opposite. The meaning of these two signals has been polluted by chip and box vendors, which leads to a lot of confusion. A lot of further confusion arises when one considers the UART logic levels vs signal levels and labels. This article attempts to resolve the status, hopefully without adding to the confusion.

'''Identifying 'A' and 'B' signals'''

Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit.

The A signal is the wire that, when in the idle state, is at a slightly higher voltage than the 'B' signal. This difference in voltage measurements is the result of the biasing and termination resistors of the circuit. See [https://en.wikipedia.org/wiki/RS-485#/media/File:Rs485-bias-termination.svg Wikipedia]

'''Identifying 'Mark/Idle' and 'Space' '''

Look at the data bits. The idle condition is always the 'mark' condition. The start bit is always a 'space'. Drawings on the internet are in conflict with each other and cannot be relied upon.

{| class="wikitable" style="text-align: center;"
|+ Nominal Terminology
|-
! Our Terminology !! Description !! Terminonlogy !! Data (UART) Representation !! When Idle
|-
| A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High
|-
| B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low
|}

{| class="wikitable" style="text-align: center;"
|+ Manufacturer's Labeling
|-
! Non-inverting !! Inverting !! Class !! Manufacturer examples
|-
| A || B || Nominal || BITS, FieldServer
|-
| + || - || Symbol || BACnet Specification
|-
| RT+ || RT- || || EnOcean SmartServer IoT
|-
| + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300
|-
| B+ || A- || || MBS UBR-01 Mk II
|-
| 485+ || 485- || Symbol || FieldServer
|-
| U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]
|-
| B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]
|-
| A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485]
|-
| A || B || || [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf TI Polarity Conventions]
|}

TI has a very definitive [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf document], but one that has to be read carefully in terms of terminology. Read this document with the following table in mind. Note, according to TI (and our opinion), the [https://en.wikipedia.org/wiki/RS-485 Wikipedia article] on bus states is WRONG ! :

{| class="wikitable" style="text-align: center;"
|+ RS-485 Bus State Terminology
|-
! UART input/output !! Logic level !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 A volt !! RS-485 B volt
|-
| 1 || high|| A > B|| Mark/Idle || On || high || low
|-
| 0 || low || A < B || Space || Off || low || high
|}

BACnet Addenda

2025-06-23T15:21:34Z

BACnetEd:

BACnet Services Supported

2025-06-22T16:53:44Z

BACnetEd:

{| class="wikitable sortable"
|+ BACnet Services Supported
|-
! Service !! Category !! Description !! Addendum !! Protocol_Revision
|-
| 0 || Alarm and Event Services || ACKNOWLEDGE_ALARM || || ||
|-
| 1 || Alarm and Event Services || CONFIRMED_COV_NOTIFICATION || || ||
|-
| 2 || Alarm and Event Services || CONFIRMED_EVENT_NOTIFICATION || || ||
|-
| 3 || Alarm and Event Services || GET_ALARM_SUMMARY || || ||
|-
| 4 || Alarm and Event Services || GET_ENROLLMENT_SUMMARY || || ||
|-
| 5 || Alarm and Event Services || SUBSCRIBE_COV || || ||
|-
| 6 || File Access Services || ATOMIC_READ_FILE || || ||
|-
| 7 || File Access Services || ATOMIC_WRITE_FILE || || ||
|-
| 8 || Object Access || ADD_LIST_ELEMENT || || ||
|-
| 9 || Object Access || REMOVE_LIST_ELEMENT || || ||
|-
| 10 || Object Access || CREATE_OBJECT || || ||
|-
| 11 || Object Access || DELETE_OBJECT || || ||
|-
| 12 || Object Access || READ_PROPERTY || || ||
|-
| 13 || Object Access || READ_PROP_CONDITIONAL || || ||
|-
| 14 || Object Access || READ_PROP_MULTIPLE || || ||
|-
| 15 || Object Access || WRITE_PROPERTY || || ||
|-
| 16 || Object Access || WRITE_PROP_MULTIPLE || || ||
|-
| 17 || Remote Device Management || DEVICE_COMMUNICATION_CONTROL || || ||
|-
| 18 || Remote Device Management || PRIVATE_TRANSFER || || ||
|-
| 19 || Remote Device Management || TEXT_MESSAGE || || ||
|-
| 20 || Remote Device Management || REINITIALIZE_DEVICE || || ||
|-
| 21 || Virtual Terminal || VT_OPEN || || ||
|-
| 22 || Virtual Terminal || VT_CLOSE || || ||
|-
| 23 || Virtual Terminal || VT_DATA || || ||
|-
| 24 || Security || AUTHENTICATE || || ||
|-
| 25 || Security || REQUEST_KEY || || ||
|-
| 26 || Unconfirmed || I_AM || || ||
|-
| 27 || Unconfirmed || I_HAVE || || ||
|-
| 28 || Unconfirmed || UNCONFIRMED_COV_NOTIFICATION || || ||
|-
| 29 || Unconfirmed || UNCONFIRMED_EVENT_NOTIFICATION || || ||
|-
| 30 || Unconfirmed || UNCONFIRMED_PRIVATE_TRANSFER || || ||
|-
| 31 || Unconfirmed || UNCONFIRMED_TEXT_MESSAGE || || ||
|-
| 32 || Unconfirmed || TIME_SYNCHRONIZATION || || ||
|-
| 33 || Unconfirmed || WHO_HAS || || ||
|-
| 34 || Unconfirmed || WHO_IS || || ||
|-
| 35 || Object Access || READ_RANGE || || ||
|-
| 36 || Unconfirmed || UTC_TIME_SYNCHRONIZATION || 135-1995 addendum b || 1
|-
| 37 || Alarm and Event Services || LIFE_SAFETY_OPERATION || 135-1995 addendum c || 2
|-
| 38 || Alarm and Event Services || SUBSCRIBE_COV_PROPERTY || || 2
|-
| 39 || Alarm and Event Services || GET_EVENT_INFORMATION || || 2
|-
| 40 || Object Access || WRITE_GROUP || 135-2010 addendum aa || 14
|-
| 41 || Alarm and Event Services || SUBSCRIBE_COV_PROPERTY_MULTIPLE || || ||
|-
| 42 || Alarm and Event Services || CONFIRMED_COV_NOTIFICATION_MULTIPLE || || ||
|-
| 43 || Unconfirmed || UNCONFIRMED_COV_NOTIFICATION_MULTIPLE || || ||
|-
| 44 || Alarm and Event Services || CONFIRMED_AUDIT_NOTIFICATION || || 20 ||
|-
| 45 || Alarm and Event Services || AUDIT_LOG_QUERY || || 20 ||
|-
| 46 || Unconfirmed || UNCONFIRMED_AUDIT_NOTIFICATION || || 20 ||
|-
| 47 || Remote Device Management || WHO_AM_I || 135-2016 Addendum bz || 22 ||
|-
| 48 || Remote Device Management || YOU_ARE || 135-2016 Addendum bz || 22 ||
|}

BACnet Services Supported

2025-06-22T16:52:43Z

BACnetEd:

{| class="wikitable sortable"
|+ BACnet Services Supported
|-
! Service !! Category !! Description !! Addendum !! Protocol_Revision
|-
| 0 || Alarm and Event Services || ACKNOWLEDGE_ALARM || || ||
|-
| 1 || Alarm and Event Services || CONFIRMED_COV_NOTIFICATION || || ||
|-
| 2 || Alarm and Event Services || CONFIRMED_EVENT_NOTIFICATION || || ||
|-
| 3 || Alarm and Event Services || GET_ALARM_SUMMARY || || ||
|-
| 4 || Alarm and Event Services || GET_ENROLLMENT_SUMMARY || || ||
|-
| 5 || Alarm and Event Services || SUBSCRIBE_COV || || ||
|-
| 6 || File Access Services || ATOMIC_READ_FILE || || ||
|-
| 7 || File Access Services || ATOMIC_WRITE_FILE || || ||
|-
| 8 || Object Access || ADD_LIST_ELEMENT || || ||
|-
| 9 || Object Access || REMOVE_LIST_ELEMENT || || ||
|-
| 10 || Object Access || CREATE_OBJECT || || ||
|-
| 11 || Object Access || DELETE_OBJECT || || ||
|-
| 12 || Object Access || READ_PROPERTY || || ||
|-
| 13 || Object Access || READ_PROP_CONDITIONAL || || ||
|-
| 14 || Object Access || READ_PROP_MULTIPLE || || ||
|-
| 15 || Object Access || WRITE_PROPERTY || || ||
|-
| 16 || Object Access || WRITE_PROP_MULTIPLE || || ||
|-
| 17 || Remote Device Management || DEVICE_COMMUNICATION_CONTROL || || ||
|-
| 18 || Remote Device Management || PRIVATE_TRANSFER || || ||
|-
| 19 || Remote Device Management || TEXT_MESSAGE || || ||
|-
| 20 || Remote Device Management || REINITIALIZE_DEVICE || || ||
|-
| 21 || Virtual Terminal || VT_OPEN || || ||
|-
| 22 || Virtual Terminal || VT_CLOSE || || ||
|-
| 23 || Virtual Terminal || VT_DATA || || ||
|-
| 24 || Security || AUTHENTICATE || || ||
|-
| 25 || Security || REQUEST_KEY || || ||
|-
| 26 || Unconfirmed || I_AM || || ||
|-
| 27 || Unconfirmed || I_HAVE || || ||
|-
| 28 || Unconfirmed || UNCONFIRMED_COV_NOTIFICATION || || ||
|-
| 29 || Unconfirmed || UNCONFIRMED_EVENT_NOTIFICATION || || ||
|-
| 30 || Unconfirmed || UNCONFIRMED_PRIVATE_TRANSFER || || ||
|-
| 31 || Unconfirmed || UNCONFIRMED_TEXT_MESSAGE || || ||
|-
| 32 || Unconfirmed || TIME_SYNCHRONIZATION || || ||
|-
| 33 || Unconfirmed || WHO_HAS || || ||
|-
| 34 || Unconfirmed || WHO_IS || || ||
|-
| 35 || Object Access || READ_RANGE || || ||
|-
| 36 || Unconfirmed || UTC_TIME_SYNCHRONIZATION || || 135-1995 addendum b || 1
|-
| 37 || Alarm and Event Services || LIFE_SAFETY_OPERATION || || 135-1995 addendum c || 2
|-
| 38 || Alarm and Event Services || SUBSCRIBE_COV_PROPERTY || || || 2
|-
| 39 || Alarm and Event Services || GET_EVENT_INFORMATION || || || 2
|-
| 40 || Object Access || WRITE_GROUP || || 135-2010 addendum aa || 14
|-
| 41 || Alarm and Event Services || SUBSCRIBE_COV_PROPERTY_MULTIPLE || || ||
|-
| 42 || Alarm and Event Services || CONFIRMED_COV_NOTIFICATION_MULTIPLE || || ||
|-
| 43 || Unconfirmed || UNCONFIRMED_COV_NOTIFICATION_MULTIPLE || || ||
|-
| 44 || Alarm and Event Services || CONFIRMED_AUDIT_NOTIFICATION || || 20 ||
|-
| 45 || Alarm and Event Services || AUDIT_LOG_QUERY || || 20 ||
|-
| 46 || Unconfirmed || UNCONFIRMED_AUDIT_NOTIFICATION || || 20 ||
|-
| 47 || Remote Device Management || WHO_AM_I || 135-2016 Addendum bz || 22 ||
|-
| 48 || Remote Device Management || YOU_ARE || 135-2016 Addendum bz || 22 ||
|}

Time

2024-07-13T13:47:50Z

BACnetEd: Created page with "BACnet Time management is somewhat confusing. Here is a summary of a few of the issues. "Timezone" is defined as a combination of "Offset" + "Daylight Savings". So a "timezone" _includes_ a rule for calculating DST..... which makes it NOT the same as the colored bars on common timezone charts. e.g. https://www.timeanddate.com/time/map/ is _wrong_ (!) It is really displaying UTC offsets of the world. For example * the Native American city of "Navajo Nation" which ..."

BACnet Time management is somewhat confusing. Here is a summary of a few of the issues.

"Timezone" is defined as a combination of "Offset" + "Daylight Savings". So a "timezone" _includes_ a rule for calculating DST..... which makes it NOT the same as the colored bars on common timezone charts. e.g. https://www.timeanddate.com/time/map/ is _wrong_ (!) It is really displaying UTC offsets of the world.

For example
* the Native American city of "Navajo Nation" which is _inside_ Arizona, is in a _different_ Timezone from Arizona itself.

Also for example
* MST (Mountain Standard Time) is a Timezone
* MDT (Mountain Daylight Time) is a *DIFFERENT* Timezone...

All of the above examples, however, have the same UTC_Offset.

From the BACnet Specification:

BACnet 12.11.25

UTC_Offset

The UTC_Offset property, of type INTEGER, shall indicate the number of minutes (-1440 to +1440) offset between localstandard time and Universal Time Coordinated. The time zones to the west of the zero degree meridian shall be positivevalues, and those to the east shall be negative values. The value of the UTC_Offset property is subtracted from the UTCreceived in UTCTimeSynchronization service requests to calculate the correct local standard time.

* My UTC_Offset is 0.
* Your UTC_Offset is -60 minutes

* My standard time is UTC-0minutes
* Your standard time is UTC-(-60)minutes

* my local time is standard time + 60minutes for Daylight savings = UTC+60
* Your local time is standard time + 60minutes for daylight savings = UTC+120

* My timezone (summer time) is +60 minutes
* Your timezone (summer time) is +120 minutes

local time is:

* mine is = UTC - UTC_Offset + 60 minutes for DST = UTC - 0 + 70 = UTC+60 minutes
* yours is = UTC - UTC_OFFSET + 60 minutes for DST = UTC - (-60) + 60 = UTC+120 minutes

Diagnostic Object

2024-07-01T16:39:21Z

BACnetEd:

This is a proof-of-concept project in preparation for submitting a new "BACnet Diagnostic Object" proposal to the BACnet Steering Committee

There is a discussion group at [https://forum.bac-test.com/t/bacnet-diagnostic-object-properties-and-services/10 the BACnet Forum]

See the Wiki overview of [[Diagnostic Features]], and related [[Diagnostic Services]]

{| class="wikitable"
|+ BACnet Diagnostic Object (one per device)
|-
! Property !! Req !! New !! Datatype !! Description
|-
| BACnet Stack Vendor ID || O || || Unsigned || Different to the Vendor ID of the device itself if 3rd party stack
|-
| BACnet Stack Library Version || O || Y || String || This is the version of the 3rd party library
|-
| BACnet Stack Version || R || Y || String || OEM may modify the above, this needs to be versioned. Else if OEM custom, that version
|-
| Controller Firmware Version || R || N || String || This is the version of controllers 'business logic'
|-
| Application Version || O || N || String || This is the version of user configurable programs, scripts or logic'
|-
| BTL Certificate # || O || Y || String ||
|-
| BTL Issue Date || O || Y || BACnetDate ||
|}

* RAM %
* Program memory %
* CPU load %
* Temperature
* Certificate expiration dates

'''Initial Ideas'''

'''Site-wide'''

* Duplicate Device ID detected
* Looped Route (Jen’s words)

'''System'''

* An array/list of strings (and values) to display error messages
* - repetition count
* - priority
* - non-repeating
* - suppressible
* - ack required
* - delete (once, forever)
* - filters (same as suppressible?)
* - features similar to existing alarms/event buffers/remote destinations (code-share)
* ESE ?
* flasherr ?
* Enforced version numbering (including bug/feature/eng/market)

'''Control'''
* Debug / production mode at runtime
* Debug verbosity levels
* ‘C or ‘F system-wide
* Developer mode flag (with password?)

'''Routing'''

* High-water queue usage
* Duplicate Network Numbers
* Broadcast storm (loop) detected / suppressed ([[Circular Route Detection]])
* Monitoring remote connections (devices)
* Attempts made
* Passes / fails / MTTR etc.

'''General Datalink'''

* Messages per second (minute/hour)
* queue sizes, high-water, choked/ message rate

'''IP Datalinks'''

* Duplicate IP address
* Netmask Error

'''MS/TP Datalinks'''

* Measure Tusage (token handling time)

'''Justifications'''

* Enhanced Monitoring and Troubleshooting: A standardized way to monitor the health and status of devices, systems, and networks. It allows for real-time visibility into potential issues, which can aid in troubleshooting and reducing downtime.
* Proactive Maintenance: By collecting and analyzing diagnostic data, building managers can identify issues before they escalate into significant problems. This proactive approach to maintenance can minimize disruptions, extend the lifespan of equipment, and reduce repair costs.
* Integration and Interoperability: BACnet is designed to facilitate interoperability between various building automation systems and devices. By defining a standardized diagnostic object, different devices and systems can share diagnostic information more effectively, regardless of the manufacturer.
* Reduced Downtime: Swift identification and resolution of issues through diagnostic data can significantly reduce downtime of critical systems, leading to improved operational continuity and tenant satisfaction.

BACnet Protocol Wish List

2024-06-24T08:40:25Z

BACnetEd:

{| class="wikitable"
|+ BACnet Wish List and status
|-
! Item !! Description !! Status
|-
| Align Version with BTL records || There is no formalized link between the Application Version and Firmware Revision and the BTL certificate || ?
|-
| ReadRangeArray service || Using starting index and count. The ability to read more than 1 item on an 'oversized' array (because the array is so large).. one-by-one if segmentation not supported is... tedious. ||
|-
| || Create the concept of a "BACnet Clock" that can be placed "Out of Service" so that time and date can be manipulated easily for testing both Time Synch and e.g. Logging, calendars, schedules without disrupting the OS clock. ||
|-
| || BACnet over BLE (Bluetooth Low Energy / Bluetooth 5.1++) - not for the field network side, but for smartphones and laptops running native BACnet clients to use the bluetooth datalink that ALL smartphones and laptops have nowadays. ||
|-
| || Add DST/Timezone to the (local) TimeSync services (perhaps a new one). Doing a local time synch _without_ these parameters is pretty much a disaster (those parameters have to be written individually, cannot be broadcast etc. etc.) || See [[Wishlist-BACnet Time|BACnet Time Wishlist]]
|-
| || Adding 'max message rate' to COVs ||
|-
| || Wildcards in "WhoHas" Object Name. e.g. who-has "Room * SP" ||
|-
| || Deprecate one-hop BBMDs - "subnet-directed broadcasts" are deprecated for DDOS amplification attacks (Stevens pg 531) ||
|}

Participate in a discussion at the [https://forum.bac-test.com/t/bacnet-new-feature-suggestions/11 BACnet Forum]

BACnet Protocol Wish List

2024-06-24T08:40:04Z

BACnetEd:

{| class="wikitable"
|+ BACnet Wish List and status
|-
! Item !! Description !! Status
|-
| Align Version with BTL records || There is no formalized link between the Application Version and Firmware Revision and the BTL certificate || ?
|-
| ReadRangeArray service || Using starting index and count. The ability to read more than 1 item on an 'oversized' array (because the array is so large).. one-by-one if segmentation not supported is... tedious. ||
|-
| || Create the concept of a "BACnet Clock" that can be placed "Out of Service" so that time and date can be manipulated easily for testing both Time Synch and e.g. Logging, calendars, schedules without disrupting the OS clock. ||
|-
| || BACnet over BLE (Bluetooth Low Energy / Bluetooth 5.1++) - not for the field network side, but for smartphones and laptops running native BACnet clients to use the bluetooth datalink that ALL smartphones and laptops have nowadays. ||
|-
| || Add DST/Timezone to the (local) TimeSync services (perhaps a new one). Doing a local time synch _without_ these parameters is pretty much a disaster (those parameters have to be written individually, cannot be broadcast etc. etc.) || See [[Wishlist-BACnet Time|BACnet Time Wishlist]]
|-
| || Adding 'max message rate' to COVs ||
|-
| || Wildcards in "WhoHas" Object Name. e.g. who-has "Room * SP" ||
|-
| || Deprecate one-hop BBMDs - "subnet-directed broadcasts" are deprecated for DDOS amplification attacks (Stevens pg 531) |
|}

Participate in a discussion at the [https://forum.bac-test.com/t/bacnet-new-feature-suggestions/11 BACnet Forum]

BACnet Protocol Wish List

2024-06-24T08:37:12Z

BACnetEd:

{| class="wikitable"
|+ BACnet Wish List and status
|-
! Item !! Description !! Status
|-
| Align Version with BTL records || There is no formalized link between the Application Version and Firmware Revision and the BTL certificate || ?
|-
| ReadRangeArray service || Using starting index and count. The ability to read more than 1 item on an 'oversized' array (because the array is so large).. one-by-one if segmentation not supported is... tedious. ||
|-
| || Create the concept of a "BACnet Clock" that can be placed "Out of Service" so that time and date can be manipulated easily for testing both Time Synch and e.g. Logging, calendars, schedules without disrupting the OS clock. ||
|-
| || BACnet over BLE (Bluetooth Low Energy / Bluetooth 5.1++) - not for the field network side, but for smartphones and laptops running native BACnet clients to use the bluetooth datalink that ALL smartphones and laptops have nowadays. ||
|-
| || Add DST/Timezone to the (local) TimeSync services (perhaps a new one). Doing a local time synch _without_ these parameters is pretty much a disaster (those parameters have to be written individually, cannot be broadcast etc. etc.) || See [[Wishlist-BACnet Time|BACnet Time Wishlist]]
|-
| || Adding 'max message rate' to COVs ||
|-
| || Wildcards in "WhoHas" Object Name. e.g. who-has "Room * SP" ||
|}

Participate in a discussion at the [https://forum.bac-test.com/t/bacnet-new-feature-suggestions/11 BACnet Forum]

BACnet Standard

2024-06-20T15:35:25Z

BACnetEd:

The BACnet Standard can be purchased from the ASHRAE Bookstore.

The official BACnet Website [https://bacnet.org/ is this].

There is an online read-only version available via [https://www.ashrae.org/technical-resources/standards-and-guidelines/read-only-versions-of-ashrae-standards this link].