BACnet Wiki - User contributions [en]

http://bacnetwiki.com/api.php?action=feedcontributions&feedformat=atom&user=BACnetEd BACnet Wiki - User contributions [en] 2026-09-18T03:13:30Z User contributions MediaWiki 1.40.0 http://bacnetwiki.com/index.php?title=MS/TP_Troubleshooting&diff=13743 MS/TP Troubleshooting 2026-09-06T15:43:22Z

<p>BACnetEd: </p> <hr /> <div>This page is intended as a guide to troubleshooting BACnet MS/TP networks.<br /> <br /> {| class="wikitable"<br /> |+ Curated List of the most common problems<br /> |-<br /> ! Votes !! Description <br /> |-<br /> | 1 || Improper grounding - device not grounded<br /> |-<br /> | 1 || Improper grounding - common not grounded with 100R resistor to ground<br /> |-<br /> | 1 || Improper grounding - Shield not terminated<br /> |-<br /> | 1 || Improper Baud rate setting<br /> |-<br /> | 1 || Duplicate MAC address on segment<br /> |-<br /> | 1 || MAC address set beyond Max_Masters<br /> |-<br /> | 1 || Excessive traffic due to polling activity<br /> |-<br /> | 1 || Excessive traffic due to broadcasts elsewhere on the network<br /> |-<br /> | 1 || One bad device brings down the whole network<br /> |}<br /> <br /> <br /> {| class="wikitable"<br /> |+ Troubleshooting Methods<br /> |-<br /> ! Symptom !! Suggested Starting Point<br /> |-<br /> | I cannot see any devices on the MS/TP nework || Quiet Network Checklist<br /> |-<br /> | etc || Other<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=MS/TP_Troubleshooting&diff=13742 MS/TP Troubleshooting 2026-09-06T15:00:54Z

<p>BACnetEd: </p> <hr /> <div>This page is intended as a guide to troubleshooting BACnet MS/TP networks.<br /> <br /> {| class="wikitable"<br /> |+ Curated List of the most common problems<br /> |-<br /> ! Votes !! Description <br /> |-<br /> | 1 || Improper grounding - device not grounded<br /> |-<br /> | 1 || Improper grounding - common not grounded with 100R resistor to ground<br /> |-<br /> | 1 || Improper grounding - Shield not terminated<br /> |-<br /> | 1 || Improper Baud rate setting<br /> |-<br /> | 1 || Duplicate MAC address on segment<br /> |-<br /> | 1 || MAC address set beyond Max_Masters<br /> |-<br /> | 1 || Excessive traffic due to polling activity<br /> |-<br /> | 1 || Excessive traffic due to broadcasts elsewhere on the network<br /> |-<br /> | 1 || One bad device brings down the whole network<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=MS/TP_Troubleshooting&diff=13741 MS/TP Troubleshooting 2026-09-06T14:58:37Z

<p>BACnetEd: </p> <hr /> <div>This page is intended as a guide to troubleshooting BACnet MS/TP networks.<br /> <br /> {| class="wikitable"<br /> |+ Curated List of the most common problems<br /> |-<br /> ! Votes !! Description <br /> |-<br /> | 1 || Improper grounding - device not grounded<br /> |-<br /> | 1 || Improper grounding - common not grounded with 100R resistor to ground<br /> |-<br /> | 1 || Improper grounding - Shield not terminated<br /> |-<br /> | 1 || Improper Baud rate setting<br /> |-<br /> | 1 || Duplicate MAC address on segment<br /> |-<br /> | 1 || MAC address set beyond Max_Masters<br /> |-<br /> | 1 || Excessive traffic due to polling activity<br /> |-<br /> | 1 || Excessive traffic due to broadcasts elsewhere on the network<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=MS/TP_Troubleshooting&diff=13740 MS/TP Troubleshooting 2026-09-06T14:56:54Z

<p>BACnetEd: Created page with "This page is intended as a guide to troubleshooting BACnet MS/TP networks. {| class="wikitable" |+ Curated List of the most common problems |- ! Votes !! Description |- | 1 || Improper grounding - device not grounded |- | 1 || Improper grounding - common not grounded with 100R resistor to ground |- | 1 || Improper grounding - Shield not terminated |}"</p> <hr /> <div>This page is intended as a guide to troubleshooting BACnet MS/TP networks.<br /> <br /> {| class="wikitable"<br /> |+ Curated List of the most common problems<br /> |-<br /> ! Votes !! Description <br /> |-<br /> | 1 || Improper grounding - device not grounded<br /> |-<br /> | 1 || Improper grounding - common not grounded with 100R resistor to ground<br /> |-<br /> | 1 || Improper grounding - Shield not terminated<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=Main_Page&diff=13739 Main Page 2026-09-06T14:54:25Z

<p>BACnetEd: </p> <hr /> <div><big>'''The new BACnetWiki'''</big><br /> <br /> This is a reboot of the BACnet Wiki for consolidating thoughts and discussions around BACnet. Email me at '''edward@bac-test.com''' if needed<br /> <br /> '''Resources'''<br /> * [[BACnet Product Gallery]] - Equipment, tools, services<br /> * [[BACnet Developer Resources]] - for BACnet Stack programmers<br /> * [[BACnet User Resources]] - for those of us who use BACnet devices<br /> * [[Facilities Manager Resources]] - for those responsible for a site containing hundreds or thousands of BACnet devices<br /> * [[Resources for Beginners]]<br /> * [[Installer Resources]] - help with installing BACnet systems<br /> <br /> * The [[BACnet Standard]]<br /> * [[MS/TP Troubleshooting]]<br /> * [https://www.linkedin.com/groups/13566440/ BACnet Developers Group on LinkedIn]<br /> * [[BACnet Protocol]]<br /> * [[BIBBS - BACnet Interoperability Building Blocks]]<br /> * [[BACnet Services Supported]]<br /> * [[BACnet Addenda 135]]<br /> * [[BACnet Addenda 135.1]]<br /> * [[BACnet BTL Tests to final 135.1 Tracking]]<br /> * [[BACnet Interpretations]]<br /> * [[BTL Procedure | BTL Submittal Process]]<br /> * [[BTL Resources]]<br /> * [[BTL Test Commentary]]<br /> * [[BTL Implementation Guideline]]<br /> * Proposed [[Diagnostic Object]]<br /> * [[BACnet Best Practices]]<br /> * [[BACnet Protocol Wish List]]<br /> * [[BACnet MS/TP Best Practices]]<br /> * [[BACnet/T1L]]<br /> * [[RS-485 Polarity]]<br /> * [[BACnet Organizations]]<br /> * [[Book of Records]]</div>

BACnetEd http://bacnetwiki.com/index.php?title=Main_Page&diff=13738 Main Page 2026-09-06T14:54:01Z

<p>BACnetEd: </p> <hr /> <div><big>'''The new BACnetWiki'''</big><br /> <br /> This is a reboot of the BACnet Wiki for consolidating thoughts and discussions around BACnet. Email me at '''edward@bac-test.com''' if needed<br /> <br /> '''Resources'''<br /> * [[BACnet Product Gallery]] - Equipment, tools, services<br /> * [[BACnet Developer Resources]] - for BACnet Stack programmers<br /> * [[BACnet User Resources]] - for those of us who use BACnet devices<br /> * [[Facilities Manager Resources]] - for those responsible for a site containing hundreds or thousands of BACnet devices<br /> * [[Resources for Beginners]]<br /> * [[Installer Resources]] - help with installing BACnet systems<br /> <br /> * The [[BACnet Standard]]<br /> * [MS/TP Troubleshooting]<br /> * [https://www.linkedin.com/groups/13566440/ BACnet Developers Group on LinkedIn]<br /> * [[BACnet Protocol]]<br /> * [[BIBBS - BACnet Interoperability Building Blocks]]<br /> * [[BACnet Services Supported]]<br /> * [[BACnet Addenda 135]]<br /> * [[BACnet Addenda 135.1]]<br /> * [[BACnet BTL Tests to final 135.1 Tracking]]<br /> * [[BACnet Interpretations]]<br /> * [[BTL Procedure | BTL Submittal Process]]<br /> * [[BTL Resources]]<br /> * [[BTL Test Commentary]]<br /> * [[BTL Implementation Guideline]]<br /> * Proposed [[Diagnostic Object]]<br /> * [[BACnet Best Practices]]<br /> * [[BACnet Protocol Wish List]]<br /> * [[BACnet MS/TP Best Practices]]<br /> * [[BACnet/T1L]]<br /> * [[RS-485 Polarity]]<br /> * [[BACnet Organizations]]<br /> * [[Book of Records]]</div>

BACnetEd http://bacnetwiki.com/index.php?title=Peer_Transfer_Object&diff=13737 Peer Transfer Object 2026-09-04T14:49:27Z

<p>BACnetEd: </p> <hr /> <div>This is a proof-of-concept project in preparation for submitting a new "Peer Transfer Object" proposal to the BACnet Steering Committee<br /> <br /> See the Wiki overview of [[Diagnostic Features]], and related [[Diagnostic Services]]<br /> <br /> {| class="wikitable"<br /> |+ Peer Transfer Object (one per device)<br /> |-<br /> ! Property !! Req !! New !! Datatype !! Description<br /> |-<br /> | ObjectID ID || R || N || BACnetObjectID || Mandatory for every BACnet Object<br /> |-<br /> | Compression Enabled || O || Y || Boolean || Schema based / Varint choices of on the wire packets<br /> |-<br /> |}<br /> <br /> <br /> '''Initial Ideas'''<br /> <br /> '''Site-wide'''<br /> <br /> </div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_MS/TP&diff=13736 BACnet MS/TP 2026-09-04T14:48:05Z

<p>BACnetEd: Created page with "BACnet MS/TP - or "Mulitdrop Serial Bus / Token Passing" is a RS-485 physical layer designed to support multiple devices sharing a RS-485 bus. It is primarily used for small controllers such as for VAVs, RTUs, sensors or actuators. The language has changed to avoid the derogatory Master-Slave/Token Passing used in the past, but it will take a while for the industry to migrate from this embedded use of the language."</p> <hr /> <div>BACnet MS/TP - or "Mulitdrop Serial Bus / Token Passing" is a RS-485 physical layer designed to support multiple devices sharing a RS-485 bus. It is primarily used for small controllers such as for VAVs, RTUs, sensors or actuators.<br /> <br /> The language has changed to avoid the derogatory Master-Slave/Token Passing used in the past, but it will take a while for the industry to migrate from this embedded use of the language.</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Datalinks&diff=13735 BACnet Datalinks 2026-09-04T14:43:43Z

<p>BACnetEd: </p> <hr /> <div>{| class="wikitable"<br /> |+ BACnet Datalinks<br /> |-<br /> ! Datalink !! Physical Medium !! Description !! Status<br /> |-<br /> | [[BACnet MS/TP]] || RS-485 || Master Slave / Token Passing || Active<br /> |-<br /> | BACnet/IP|| TCP/IP over Ethernet || || Active<br /> |-<br /> | PTP || RS-232 || Peer-to-Peer || <br /> |-<br /> | Ethernet || Ethernet || Note - "Ethernet", not IP || Active<br /> |-<br /> | AB || IP || BACnet Secure Connect / BACnet/SC || <br /> |-<br /> | 8 || ARCNET || ARCNET (ATA 878.1) || <br /> |-<br /> | 10 || RS-232 || PTP (Peer-to-Peer) || <br /> |-<br /> | 11 || Lon || LonTalk (ISO/IEC 14908.1) || <br /> |-<br /> | U || IPv6 || BACnet/IPv6 || <br /> |-<br /> | O || Zigbee || ZigBee || <br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Vendor_ID_List&diff=13734 BACnet Vendor ID List 2026-08-18T10:44:11Z

<p>BACnetEd: Created page with "The official BACnet Vendor ID list can be found on the BACnet.org website [https://bacnet.org/assigned-vendor-ids/ link]"</p> <hr /> <div>The official BACnet Vendor ID list can be found on the BACnet.org website [https://bacnet.org/assigned-vendor-ids/ link]</div>

BACnetEd http://bacnetwiki.com/index.php?title=Peer_Transfer_Object&diff=13733 Peer Transfer Object 2026-08-18T08:55:29Z

<p>BACnetEd: </p> <hr /> <div>This is a proof-of-concept project in preparation for submitting a new "Peer Transfer Object" proposal to the BACnet Steering Committee<br /> <br /> See the Wiki overview of [[Diagnostic Features]], and related [[Diagnostic Services]]<br /> <br /> {| class="wikitable"<br /> |+ Peer Transfer Object (one per device)<br /> |-<br /> ! Property !! Req !! New !! Datatype !! Description<br /> |-<br /> | ObjectID ID || R || N || BACnetObjectID || Mandatory for every BACnet Object<br /> |-<br /> | Compression Enabled || O || Y || Boolean || Schema based / Varint choices of on the wire packets<br /> |-<br /> |}<br /> <br /> <br /> '''Initial Ideas'''<br /> <br /> '''Site-wide'''</div>

BACnetEd http://bacnetwiki.com/index.php?title=BTL_Procedure&diff=13732 BTL Procedure 2026-08-16T13:26:36Z

<p>BACnetEd: </p> <hr /> <div>Here is a summary/checklist to get your device through the BTL certification process:<br /> <br /> * Pre-test your device using our BACnet Test Suite<br /> * 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)<br /> * Confirm they will test to Protocol Revision 26 (or perhaps higher)<br /> * Confirm they will provide an estimate (quote) based on the "BTL Functionality Checklist" that you will fill in<br /> * Find out when they can start testing, and estimate how long will it take<br /> * Confirm Payment terms<br /> * Ask for any other requirements they may have<br /> * Complete the "BTL Functionality Checklist". The original is in the "BTL Test Package-26" which can be downloaded from the BTL website<br /> * Send this to the candidate lab(s) and get a final estimate of the costs<br /> * 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.<br /> * Pay the $750 (?) registration fee.<br /> * Ask BTL for additional guidance<br /> * 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).<br /> * Select a Lab, proceed<br /> * [https://www.bac-test.com/ BITS] can assist you with this process.<br /> * (Optional) submit Test Results to [https://wspcert.de/en/welcome WSPCert] for certification.<br /> <br /> <br /> </div>

BACnetEd http://bacnetwiki.com/index.php?title=BTL_Procedure&diff=13731 BTL Procedure 2026-08-16T13:15:55Z

<p>BACnetEd: </p> <hr /> <div>Here is a summary/checklist to get your device through the BTL certification process:<br /> <br /> * Pre-test your device using our BACnet Test Suite<br /> * 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)<br /> * Confirm they will test to Protocol Revision 26 (or perhaps higher)<br /> * Confirm they will provide an estimate (quote) based on the "BTL Functionality Checklist" that you will fill in<br /> * Find out when they can start testing, and estimate how long will it take<br /> * Confirm Payment terms<br /> * Ask for any other requirements they may have<br /> * Complete the "BTL Functionality Checklist". The original is in the "BTL Test Package-26" which can be downloaded from the BTL website<br /> * Send this to the candidate lab(s) and get a final estimate of the costs<br /> * 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.<br /> * Pay the $750 (?) registration fee.<br /> * Ask BTL for additional guidance<br /> * 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).<br /> * Select a Lab, proceed<br /> * [https://www.bac-test.com/ BITS] can assist you with this process.<br /> * (Optional) submit Test Results to [https://wspcert.de/en/welcome WSPCert] for certification.</div>

BACnetEd http://bacnetwiki.com/index.php?title=BTL_Procedure&diff=13730 BTL Procedure 2026-08-16T13:12:10Z

<p>BACnetEd: </p> <hr /> <div>Here is a summary/checklist to get your device through the BTL certification process:<br /> <br /> * Pre-test your device using our BACnet Test Suite<br /> * 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)<br /> * Confirm they will test to Protocol Revision 26 (or perhaps higher)<br /> * Confirm they will provide an estimate (quote) based on the "BTL Functionality Checklist" that you will fill in<br /> * Find out when they can start testing, and estimate how long will it take<br /> * Confirm Payment terms<br /> * Ask for any other requirements they may have<br /> * Complete the "BTL Functionality Checklist". The original is in the "BTL Test Package-26" which can be downloaded from the BTL website<br /> * Send this to the candidate lab(s) and get a final estimate of the costs<br /> * 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.<br /> * Ask BTL for additional guidance<br /> * 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).<br /> * Select a Lab, proceed<br /> * [https://www.bac-test.com/ BITS] can assist you with this process.<br /> * (Optional) submit Test Results to [https://wspcert.de/en/welcome WSPCert] for certification.</div>

BACnetEd http://bacnetwiki.com/index.php?title=Peer_Transfer_Object&diff=13729 Peer Transfer Object 2026-08-15T13:15:20Z

<p>BACnetEd: Created page with "This is a proof-of-concept project in preparation for submitting a new "Peer Transfer Object" proposal to the BACnet Steering Committee See the Wiki overview of Diagnostic Features, and related Diagnostic Services {| class="wikitable" |+ Peer Transfer 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 Stac..."</p> <hr /> <div>This is a proof-of-concept project in preparation for submitting a new "Peer Transfer Object" proposal to the BACnet Steering Committee<br /> <br /> See the Wiki overview of [[Diagnostic Features]], and related [[Diagnostic Services]]<br /> <br /> {| class="wikitable"<br /> |+ Peer Transfer Object (one per device)<br /> |-<br /> ! Property !! Req !! New !! Datatype !! Description<br /> |-<br /> | BACnet Stack Vendor ID || O || || Unsigned || Different to the Vendor ID of the device itself if 3rd party stack<br /> |-<br /> | BACnet Stack Library Version || O || Y || String || This is the version of the 3rd party library<br /> |-<br /> | BACnet Stack Version || R || Y || String || OEM may modify the above, this needs to be versioned. Else if OEM custom, that version<br /> |-<br /> | Controller Firmware Version || R || N || String || This is the version of controllers 'business logic'<br /> |-<br /> | Application Version || O || N || String || This is the version of user configurable programs, scripts or logic'<br /> |-<br /> | BTL Certificate # || O || Y || String || <br /> |-<br /> | BTL Issue Date || O || Y || BACnetDate ||<br /> |-<br /> | RAM % || || || || <br /> |-<br /> | Program memory % || || || || <br /> |-<br /> | CPU load % || || || || <br /> |-<br /> | Temperature || || || || <br /> |-<br /> | Certificate expiration dates || || || || <br /> |}<br /> <br /> <br /> '''Initial Ideas'''<br /> <br /> '''Site-wide'''<br /> <br /> * Duplicate Device ID detected<br /> * Looped Route (Jen’s words)<br /> <br /> <br /> '''System'''<br /> <br /> * An array/list of strings (and values) to display error messages<br /> * - repetition count<br /> * - priority<br /> * - non-repeating<br /> * - suppressible<br /> * - ack required<br /> * - delete (once, forever)<br /> * - filters (same as suppressible?)<br /> * - features similar to existing alarms/event buffers/remote destinations (code-share)<br /> * ESE ?<br /> * flasherr ?<br /> * Enforced version numbering (including bug/feature/eng/market)<br /> <br /> <br /> '''Control'''<br /> <br /> * Debug / production mode at runtime<br /> * Debug verbosity levels<br /> * ‘C or ‘F system-wide<br /> * Developer mode flag (with password?)<br /> <br /> <br /> '''Routing'''<br /> <br /> * High-water queue usage<br /> * Duplicate Network Numbers<br /> * Broadcast storm (loop) detected / suppressed ([[Circular Route Detection]])<br /> * Monitoring remote connections (devices)<br /> * Attempts made<br /> * Passes / fails / MTTR etc.<br /> <br /> <br /> '''General Datalink'''<br /> <br /> * Messages per second (minute/hour)<br /> * queue sizes, high-water, choked/ message rate<br /> <br /> <br /> '''IP Datalinks'''<br /> <br /> * Duplicate IP address<br /> * Netmask Error<br /> <br /> '''MS/TP Datalinks'''<br /> <br /> * Measure Tusage (token handling time)<br /> <br /> '''Justifications'''<br /> <br /> * 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.<br /> * 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.<br /> * 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.<br /> * 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.</div>

BACnetEd http://bacnetwiki.com/index.php?title=Diagnostic_Object&diff=13728 Diagnostic Object 2026-08-15T13:13:43Z

<p>BACnetEd: </p> <hr /> <div>This is a proof-of-concept project in preparation for submitting a new "BACnet Diagnostic Object" proposal to the BACnet Steering Committee<br /> <br /> See the Wiki overview of [[Diagnostic Features]], and related [[Diagnostic Services]]<br /> <br /> {| class="wikitable"<br /> |+ BACnet Diagnostic Object (one per device)<br /> |-<br /> ! Property !! Req !! New !! Datatype !! Description<br /> |-<br /> | BACnet Stack Vendor ID || O || || Unsigned || Different to the Vendor ID of the device itself if 3rd party stack<br /> |-<br /> | BACnet Stack Library Version || O || Y || String || This is the version of the 3rd party library<br /> |-<br /> | BACnet Stack Version || R || Y || String || OEM may modify the above, this needs to be versioned. Else if OEM custom, that version<br /> |-<br /> | Controller Firmware Version || R || N || String || This is the version of controllers 'business logic'<br /> |-<br /> | Application Version || O || N || String || This is the version of user configurable programs, scripts or logic'<br /> |-<br /> | BTL Certificate # || O || Y || String || <br /> |-<br /> | BTL Issue Date || O || Y || BACnetDate ||<br /> |-<br /> | RAM % || || || || <br /> |-<br /> | Program memory % || || || || <br /> |-<br /> | CPU load % || || || || <br /> |-<br /> | Temperature || || || || <br /> |-<br /> | Certificate expiration dates || || || || <br /> |}<br /> <br /> <br /> '''Initial Ideas'''<br /> <br /> '''Site-wide'''<br /> <br /> * Duplicate Device ID detected<br /> * Looped Route (Jen’s words)<br /> <br /> <br /> '''System'''<br /> <br /> * An array/list of strings (and values) to display error messages<br /> * - repetition count<br /> * - priority<br /> * - non-repeating<br /> * - suppressible<br /> * - ack required<br /> * - delete (once, forever)<br /> * - filters (same as suppressible?)<br /> * - features similar to existing alarms/event buffers/remote destinations (code-share)<br /> * ESE ?<br /> * flasherr ?<br /> * Enforced version numbering (including bug/feature/eng/market)<br /> <br /> <br /> '''Control'''<br /> <br /> * Debug / production mode at runtime<br /> * Debug verbosity levels<br /> * ‘C or ‘F system-wide<br /> * Developer mode flag (with password?)<br /> <br /> <br /> '''Routing'''<br /> <br /> * High-water queue usage<br /> * Duplicate Network Numbers<br /> * Broadcast storm (loop) detected / suppressed ([[Circular Route Detection]])<br /> * Monitoring remote connections (devices)<br /> * Attempts made<br /> * Passes / fails / MTTR etc.<br /> <br /> <br /> '''General Datalink'''<br /> <br /> * Messages per second (minute/hour)<br /> * queue sizes, high-water, choked/ message rate<br /> <br /> <br /> '''IP Datalinks'''<br /> <br /> * Duplicate IP address<br /> * Netmask Error<br /> <br /> '''MS/TP Datalinks'''<br /> <br /> * Measure Tusage (token handling time)<br /> <br /> '''Justifications'''<br /> <br /> * 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.<br /> * 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.<br /> * 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.<br /> * 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.</div>

BACnetEd http://bacnetwiki.com/index.php?title=Test&diff=13727 Test 2026-08-01T16:42:53Z

<p>BACnetEd: Created page with "{| class="wikitable sortable filterable" ! Product ! Manufacturer ! Category ! Status ! Priority ! Date reported |- | ASI IntelliFront | ASI Controls | Controller | Open | High | 2026-07-21 |- | PXC4 | Siemens | Controller | Closed | Medium | 2026-06-15 |- | CIPer 50 | Honeywell | Controller | Investigating | High | 2026-07-30 |- | Automation Server | Schneider Electric | Supervisor | Open | Low | 2026-05-12 |- | JACE 9000 | Tridium | Supervisor | Closed | Medium | 2026-..."</p> <hr /> <div>{| class="wikitable sortable filterable"<br /> ! Product<br /> ! Manufacturer<br /> ! Category<br /> ! Status<br /> ! Priority<br /> ! Date reported<br /> |-<br /> | ASI IntelliFront<br /> | ASI Controls<br /> | Controller<br /> | Open<br /> | High<br /> | 2026-07-21<br /> |-<br /> | PXC4<br /> | Siemens<br /> | Controller<br /> | Closed<br /> | Medium<br /> | 2026-06-15<br /> |-<br /> | CIPer 50<br /> | Honeywell<br /> | Controller<br /> | Investigating<br /> | High<br /> | 2026-07-30<br /> |-<br /> | Automation Server<br /> | Schneider Electric<br /> | Supervisor<br /> | Open<br /> | Low<br /> | 2026-05-12<br /> |-<br /> | JACE 9000<br /> | Tridium<br /> | Supervisor<br /> | Closed<br /> | Medium<br /> | 2026-04-09<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=135.1_-_13.1.2_TD_Initiated_Unsegmented_Request_and_Segmented_Response_(Non-Window)&diff=13726 135.1 - 13.1.2 TD Initiated Unsegmented Request and Segmented Response (Non-Window) 2026-07-23T12:47:41Z

<p>BACnetEd: Created page with "This test is considered invalid. Test 13.1.2 from 135.1 contradicts the BACnet standard. According to Clause 5.4.5.4 of the BACnet standard: === UnexpectedPDU_Received If an unexpected PDU (BACnet-Confirmed-Request-PDU) that is secured with the same settings as the original PDU is received from the network layer, then stop SegmentTimer; issue an N-UNITDATA.request with 'data_expecting_reply' = FALSE to transmit a BACnet-Abort-PDU with 'server' = TRUE; and enter the ID..."</p> <hr /> <div>This test is considered invalid.<br /> <br /> <br /> Test 13.1.2 from 135.1 contradicts the BACnet standard. According<br /> to Clause 5.4.5.4 of the BACnet standard:<br /> ===<br /> UnexpectedPDU_Received<br /> If an unexpected PDU (BACnet-Confirmed-Request-PDU) that is secured with<br /> the same settings as the original PDU is received from the network<br /> layer,<br /> <br /> then stop SegmentTimer; issue an N-UNITDATA.request with<br /> 'data_expecting_reply' = FALSE to transmit a<br /> BACnet-Abort-PDU with 'server' = TRUE; and enter the IDLE state.<br /> ===<br /> <br /> Note that the standard does not have the DuplicateRequestReceived event<br /> in the SEGMENTED_RESPONSE state, so it is UnexpectedPDU_Received, which<br /> sends BACnet-Abort-PDU.</div>

BACnetEd http://bacnetwiki.com/index.php?title=BTL_Test_Commentary&diff=13725 BTL Test Commentary 2026-07-23T12:47:23Z

<p>BACnetEd: </p> <hr /> <div>{| class="wikitable"<br /> |+ 135.1 Tests and comments <br /> |-<br /> ! 135.1 Test !! BTL Test !! Description !! Notes !! Detail<br /> |-<br /> | 13.1.2 || || TD Initiated Unsegmented Request and Segmented Response (Non-Window) || This test does not reflect the 135 standard, and is invalid. || [[135.1 - 13.1.2 TD Initiated Unsegmented Request and Segmented Response (Non-Window) | link ]]<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=BTL_Test_Commentary&diff=13724 BTL Test Commentary 2026-07-23T12:41:58Z

<p>BACnetEd: </p> <hr /> <div>{| class="wikitable"<br /> |+ 135.1 Tests and comments<br /> |-<br /> ! 135.1 Test !! BTL Test !! Description !! Notes<br /> |-<br /> | 13.1.2 || || TD Initiated Unsegmented Request and Segmented Response (Non-Window) || This test does not reflect the 135 standard, and is invalid.<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=BTL_Test_Commentary&diff=13723 BTL Test Commentary 2026-07-23T12:41:16Z

<p>BACnetEd: Created page with "{| class="wikitable" |+ 135.1 Tests and comments |- ! 135.1 Test !! BTL Test !! Notes |- | 13.1.2 TD Initiated Unsegmented Request and Segmented Response (Non-Window) || || This test does not reflect the 135 standard, and is invalid. |}"</p> <hr /> <div>{| class="wikitable"<br /> |+ 135.1 Tests and comments<br /> |-<br /> ! 135.1 Test !! BTL Test !! Notes<br /> |-<br /> | 13.1.2 TD Initiated Unsegmented Request and Segmented Response (Non-Window) || || This test does not reflect the 135 standard, and is invalid.<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=Main_Page&diff=13722 Main Page 2026-07-23T12:39:38Z

<p>BACnetEd: </p> <hr /> <div><big>'''The new BACnetWiki'''</big><br /> <br /> This is a reboot of the BACnet Wiki for consolidating thoughts and discussions around BACnet. Email me at '''edward@bac-test.com''' if needed<br /> <br /> '''Resources'''<br /> * [[BACnet Product Gallery]] - Equipment, tools, services<br /> * [[BACnet Developer Resources]] - for BACnet Stack programmers<br /> * [[BACnet User Resources]] - for those of us who use BACnet devices<br /> * [[Facilities Manager Resources]] - for those responsible for a site containing hundreds or thousands of BACnet devices<br /> * [[Resources for Beginners]]<br /> * [[Installer Resources]] - help with installing BACnet systems<br /> <br /> * The [[BACnet Standard]]<br /> * [https://www.linkedin.com/groups/13566440/ BACnet Developers Group on LinkedIn]<br /> * [[BACnet Protocol]]<br /> * [[BIBBS - BACnet Interoperability Building Blocks]]<br /> * [[BACnet Services Supported]]<br /> * [[BACnet Addenda 135]]<br /> * [[BACnet Addenda 135.1]]<br /> * [[BACnet BTL Tests to final 135.1 Tracking]]<br /> * [[BACnet Interpretations]]<br /> * [[BTL Procedure | BTL Submittal Process]]<br /> * [[BTL Resources]]<br /> * [[BTL Test Commentary]]<br /> * [[BTL Implementation Guideline]]<br /> * Proposed [[Diagnostic Object]]<br /> * [[BACnet Best Practices]]<br /> * [[BACnet Protocol Wish List]]<br /> * [[BACnet MS/TP Best Practices]]<br /> * [[BACnet/T1L]]<br /> * [[RS-485 Polarity]]<br /> * [[BACnet Organizations]]<br /> * [[Book of Records]]</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet/T1L&diff=13721 BACnet/T1L 2026-07-03T08:44:00Z

<p>BACnetEd: Created page with ""BACnet/T1L is NOT a BACnet standard, it is simply BACnet/IP (or BACnet/SC) over a 10BASE-T1L datalink. 10BASE-T1L is also "simple" Ethernet over a twisted pair, or SPE (Single Pair Ethernet) 10BASE-T1L has great potential in Building Automation due to the fact that twisted pair is common, well known in the industry, and there is the possibility of re-using in-place or legacy network wiring. As such, here is a list of Building Automation / BACnet resources that are r..."</p> <hr /> <div>"BACnet/T1L is NOT a BACnet standard, it is simply BACnet/IP (or BACnet/SC) over a 10BASE-T1L datalink. 10BASE-T1L is also "simple" Ethernet over a twisted pair, or SPE (Single Pair Ethernet)<br /> <br /> <br /> 10BASE-T1L has great potential in Building Automation due to the fact that twisted pair is common, well known in the industry, and there is the possibility of re-using in-place or legacy network wiring.<br /> <br /> <br /> As such, here is a list of Building Automation / BACnet resources that are relevant to BACnet<br /> <br /> <br /> {| class="wikitable"<br /> |+ Caption text<br /> |-<br /> ! Header text !! Header text !! Header text !! Header text<br /> |-<br /> | Example || Example || Example || Example<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=Main_Page&diff=13720 Main Page 2026-07-03T08:39:15Z

<p>BACnetEd: </p> <hr /> <div><big>'''The new BACnetWiki'''</big><br /> <br /> This is a reboot of the BACnet Wiki for consolidating thoughts and discussions around BACnet. Email me at '''edward@bac-test.com''' if needed<br /> <br /> '''Resources'''<br /> * [[BACnet Product Gallery]] - Equipment, tools, services<br /> * [[BACnet Developer Resources]] - for BACnet Stack programmers<br /> * [[BACnet User Resources]] - for those of us who use BACnet devices<br /> * [[Facilities Manager Resources]] - for those responsible for a site containing hundreds or thousands of BACnet devices<br /> * [[Resources for Beginners]]<br /> * [[Installer Resources]] - help with installing BACnet systems<br /> <br /> * The [[BACnet Standard]]<br /> * [https://www.linkedin.com/groups/13566440/ BACnet Developers Group on LinkedIn]<br /> * [[BACnet Protocol]]<br /> * [[BIBBS - BACnet Interoperability Building Blocks]]<br /> * [[BACnet Services Supported]]<br /> * [[BACnet Addenda 135]]<br /> * [[BACnet Addenda 135.1]]<br /> * [[BACnet BTL Tests to final 135.1 Tracking]]<br /> * [[BACnet Interpretations]]<br /> * [[BTL Procedure | BTL Submittal Process]]<br /> * [[BTL Resources]]<br /> * [[BTL Test Plan]]<br /> * [[BTL Implementation Guideline]]<br /> * Proposed [[Diagnostic Object]]<br /> * [[BACnet Best Practices]]<br /> * [[BACnet Protocol Wish List]]<br /> * [[BACnet MS/TP Best Practices]]<br /> * [[BACnet/T1L]]<br /> * [[RS-485 Polarity]]<br /> * [[BACnet Organizations]]<br /> * [[Book of Records]]</div>

BACnetEd http://bacnetwiki.com/index.php?title=Vendors_-_BACnet_Routers&diff=13719 Vendors - BACnet Routers 2026-07-01T09:44:53Z

<p>BACnetEd: Created page with "{| class="wikitable" |+ BACnet Router Vendors |- ! Vendor !! Model !! Description !! BACnet/SC Hub !! Link |- | Contemporarty Controls || BASrouterSX || || [https://www.ccontrols.com/basautomation/basroutersx.php link] |- | Contemporarty Controls || BASrouter || || [https://www.ccontrols.com/basautomation/basrouter.php link] |- | MSA || FS-ROUTER-BAC2 || || [https://gb.msasafety.com/IIoT-Gateways/System-Integrators/BACnet-Router/p/bacnet-router?locale=en link] |- | KMC..."</p> <hr /> <div>{| class="wikitable"<br /> |+ BACnet Router Vendors<br /> |-<br /> ! Vendor !! Model !! Description !! BACnet/SC Hub !! Link<br /> |-<br /> | Contemporarty Controls || BASrouterSX || || [https://www.ccontrols.com/basautomation/basroutersx.php link]<br /> |-<br /> | Contemporarty Controls || BASrouter || || [https://www.ccontrols.com/basautomation/basrouter.php link]<br /> |-<br /> | MSA || FS-ROUTER-BAC2 || || [https://gb.msasafety.com/IIoT-Gateways/System-Integrators/BACnet-Router/p/bacnet-router?locale=en link]<br /> |-<br /> | KMC || BAC-5051AE || || [https://www.kmccontrols.com/product/62509/ link]<br /> |-<br /> | MBS || UBR-01 Mk II || || [https://en.mbs-solutions.de/ubr-01-mk-ii-bacnet-router link]<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Product_Gallery&diff=13718 BACnet Product Gallery 2026-07-01T09:35:03Z

<p>BACnetEd: </p> <hr /> <div>{| class="wikitable"<br /> |+ Caption text<br /> |-<br /> ! Model !! Description !! BTL !! Vendor !! Contact (email)<br /> |-<br /> | BTS || BACnet Test Suite - aimed at manufacturers || No || BITS || edward at bac-test.com<br /> |-<br /> | BSA || BACnet Site Auditor - Scans a site, identifying problems || No || BITS || edward at bac-test.com<br /> |-<br /> | [[Vendors - BACnet Routers|BACnet Routers]] || Links to a new page || Yes || Various || <br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=RS-485_Polarity&diff=13717 RS-485 Polarity 2026-06-26T20:37:43Z

<p>BACnetEd: </p> <hr /> <div>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. 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.<br /> <br /> '''Quotations directly from the Standerd. Basic Rule from the specification (and I have the actual specification)<br /> <br /> * A > B means "binary 0 on the bus" or "ON".<br /> * A < B means "binary 1 on the bus" or "OFF".<br /> * "The logic function of the generator and the receiver is beyond the scope of this standard, and therefore not defined"<br /> <br /> And A is non-inverting (and thus B is inverting)<br /> <br /> <br /> '''Identifying 'A' and 'B' signals'''<br /> <br /> Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit. <br /> <br /> 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]<br /> <br /> <br /> '''Identifying 'Mark/Idle' and 'Space' '''<br /> <br /> 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.<br /> <br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ Nominal Terminology<br /> |-<br /> ! Specification !! Description !! Terminology !! Data (UART) Representation !! When Idle<br /> |-<br /> | A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High<br /> |-<br /> | B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low<br /> |}<br /> <br /> <br /> <br /> {| class="wikitable" style="text-align: center;" <br /> |+ Manufacturer's Labeling<br /> |-<br /> ! Non-inverting !! Inverting !! Class !! Manufacturer examples !!<br /> |-<br /> | A || B || Nominal || BITS, FieldServer<br /> |-<br /> | + || - || Symbol || BACnet Specification || The non-inverting input of the<br /> EIA-485 transceiver is designated in this specification as "plus" or "+" <br /> |-<br /> | RT+ || RT- || || EnOcean SmartServer IoT<br /> |-<br /> | + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300<br /> |-<br /> | B+ || A- || || MBS UBR-01 Mk II || This is obviously contrary to everyone else <br /> |-<br /> | 485+ || 485- || Symbol || FieldServer<br /> |-<br /> | U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]<br /> |-<br /> | B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]<br /> |-<br /> | A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485], AirBox<br /> |-<br /> | 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]<br /> |-<br /> | ? || ? || || KMC router, A- and B+, true polarity TBC<br /> |}<br /> <br /> The BACnet Specification (135 - 9.2.2) says: The non-inverting input of the<br /> 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." <br /> <br /> 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 ! :<br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ RS-485 Bus State Terminology<br /> |-<br /> ! UART input/output !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 Bus Binary state<br /> |-<br /> | 1 || A > B|| Mark/Idle || On || Binary 0<br /> |-<br /> | 0 || A < B || Space || Off || Binary 1<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=RS-485_Polarity&diff=13716 RS-485 Polarity 2026-06-26T20:32:34Z

<p>BACnetEd: </p> <hr /> <div>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. 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.<br /> <br /> '''Quotations directly from the Standerd. Basic Rule from the specification (and I have the actual specification)<br /> <br /> * A > B means "binary 0 on the bus" or "ON".<br /> * A < B means "binary 1 on the bus" or "OFF".<br /> * "The logic function of the generator and the receiver is beyond the scope of this standard, and therefore not defined"<br /> <br /> And A is non-inverting (and thus B is inverting)<br /> <br /> <br /> '''Identifying 'A' and 'B' signals'''<br /> <br /> Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit. <br /> <br /> 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]<br /> <br /> <br /> '''Identifying 'Mark/Idle' and 'Space' '''<br /> <br /> 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.<br /> <br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ Nominal Terminology<br /> |-<br /> ! Specification !! Description !! Terminology !! Data (UART) Representation !! When Idle<br /> |-<br /> | A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High<br /> |-<br /> | B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low<br /> |}<br /> <br /> <br /> <br /> {| class="wikitable" style="text-align: center;" <br /> |+ Manufacturer's Labeling<br /> |-<br /> ! Non-inverting !! Inverting !! Class !! Manufacturer examples !!<br /> |-<br /> | A || B || Nominal || BITS, FieldServer<br /> |-<br /> | + || - || Symbol || BACnet Specification || The non-inverting input of the<br /> EIA-485 transceiver is designated in this specification as "plus" or "+" <br /> |-<br /> | RT+ || RT- || || EnOcean SmartServer IoT<br /> |-<br /> | + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300<br /> |-<br /> | B+ || A- || || MBS UBR-01 Mk II || This is obviously contrary to everyone else <br /> |-<br /> | 485+ || 485- || Symbol || FieldServer<br /> |-<br /> | U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]<br /> |-<br /> | B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]<br /> |-<br /> | A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485], AirBox<br /> |-<br /> | 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]<br /> |-<br /> | ? || ? || || KMC router, A- and B+, true polarity TBC<br /> |}<br /> <br /> The BACnet Specification (135 - 9.2.2) says: The non-inverting input of the<br /> 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." <br /> <br /> 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 ! :<br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ RS-485 Bus State Terminology<br /> |-<br /> ! UART input/output !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 Bus Binary state<br /> |-<br /> | 1 || A > B|| Mark/Idle || On || Logic 0<br /> |-<br /> | 0 || A < B || Space || Off || Logic 1<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=RS-485_Polarity&diff=13715 RS-485 Polarity 2026-06-26T20:31:40Z

<p>BACnetEd: </p> <hr /> <div>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. 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.<br /> <br /> '''Quotations directly from the Standerd. Basic Rule from the specification (and I have the actual specification)<br /> <br /> * A > B means "binary 0 on the bus" or "ON".<br /> * A < B means "binary 1 on the bus" or "OFF".<br /> * "The logic function of the generator and the receiver is beyond the scope of this standard, and therefore not defined"<br /> <br /> And A is non-inverting (and thus B is inverting)<br /> <br /> <br /> '''Identifying 'A' and 'B' signals'''<br /> <br /> Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit. <br /> <br /> 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]<br /> <br /> <br /> '''Identifying 'Mark/Idle' and 'Space' '''<br /> <br /> 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.<br /> <br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ Nominal Terminology<br /> |-<br /> ! Our Terminology !! Description !! Terminonlogy !! Data (UART) Representation !! When Idle<br /> |-<br /> | A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High<br /> |-<br /> | B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low<br /> |}<br /> <br /> <br /> <br /> {| class="wikitable" style="text-align: center;" <br /> |+ Manufacturer's Labeling<br /> |-<br /> ! Non-inverting !! Inverting !! Class !! Manufacturer examples !!<br /> |-<br /> | A || B || Nominal || BITS, FieldServer<br /> |-<br /> | + || - || Symbol || BACnet Specification || The non-inverting input of the<br /> EIA-485 transceiver is designated in this specification as "plus" or "+" <br /> |-<br /> | RT+ || RT- || || EnOcean SmartServer IoT<br /> |-<br /> | + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300<br /> |-<br /> | B+ || A- || || MBS UBR-01 Mk II || This is obviously contrary to everyone else <br /> |-<br /> | 485+ || 485- || Symbol || FieldServer<br /> |-<br /> | U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]<br /> |-<br /> | B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]<br /> |-<br /> | A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485], AirBox<br /> |-<br /> | 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]<br /> |-<br /> | ? || ? || || KMC router, A- and B+, true polarity TBC<br /> |}<br /> <br /> The BACnet Specification (135 - 9.2.2) says: The non-inverting input of the<br /> 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." <br /> <br /> 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 ! :<br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ RS-485 Bus State Terminology<br /> |-<br /> ! UART input/output !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 Bus Binary state<br /> |-<br /> | 1 || A > B|| Mark/Idle || On || Logic 0<br /> |-<br /> | 0 || A < B || Space || Off || Logic 1<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=RS-485_Polarity&diff=13714 RS-485 Polarity 2026-06-22T09:28:33Z

<p>BACnetEd: </p> <hr /> <div>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.<br /> <br /> '''Basic Rule from the specification (and I have the actual specification)<br /> <br /> * A > B means "binary 0 on the bus" or "ON".<br /> * A < B means "binary 1 on the bus" or "OFF".<br /> <br /> And A is non-inverting (and thus B is inverting)<br /> <br /> '''Identifying 'A' and 'B' signals'''<br /> <br /> Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit. <br /> <br /> 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]<br /> <br /> <br /> '''Identifying 'Mark/Idle' and 'Space' '''<br /> <br /> 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.<br /> <br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ Nominal Terminology<br /> |-<br /> ! Our Terminology !! Description !! Terminonlogy !! Data (UART) Representation !! When Idle<br /> |-<br /> | A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High<br /> |-<br /> | B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low<br /> |}<br /> <br /> <br /> <br /> {| class="wikitable" style="text-align: center;" <br /> |+ Manufacturer's Labeling<br /> |-<br /> ! Non-inverting !! Inverting !! Class !! Manufacturer examples !!<br /> |-<br /> | A || B || Nominal || BITS, FieldServer<br /> |-<br /> | + || - || Symbol || BACnet Specification || The non-inverting input of the<br /> EIA-485 transceiver is designated in this specification as "plus" or "+" <br /> |-<br /> | RT+ || RT- || || EnOcean SmartServer IoT<br /> |-<br /> | + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300<br /> |-<br /> | B+ || A- || || MBS UBR-01 Mk II || This is obviously contrary to everyone else <br /> |-<br /> | 485+ || 485- || Symbol || FieldServer<br /> |-<br /> | U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]<br /> |-<br /> | B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]<br /> |-<br /> | A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485], AirBox<br /> |-<br /> | 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]<br /> |-<br /> | ? || ? || || KMC router, A- and B+, true polarity TBC<br /> |}<br /> <br /> The BACnet Specification (135 - 9.2.2) says: The non-inverting input of the<br /> 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." <br /> <br /> 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 ! :<br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ RS-485 Bus State Terminology<br /> |-<br /> ! UART input/output !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 Bus Binary state<br /> |-<br /> | 1 || A > B|| Mark/Idle || On || Logic 0<br /> |-<br /> | 0 || A < B || Space || Off || Logic 1<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=RS-485_Polarity&diff=13713 RS-485 Polarity 2026-06-22T09:28:05Z

<p>BACnetEd: </p> <hr /> <div>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.<br /> <br /> '''Basic Rule from the specification (and I have the actual specification)<br /> <br /> * A > B means "binary 0 on the bus" or "ON".<br /> * A < B means "binary 1 on the bus" or "OFF".<br /> <br /> And A is non-inverting (and thus B is inverting)<br /> <br /> '''Identifying 'A' and 'B' signals'''<br /> <br /> Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit. <br /> <br /> 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]<br /> <br /> <br /> '''Identifying 'Mark/Idle' and 'Space' '''<br /> <br /> 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.<br /> <br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ Nominal Terminology<br /> |-<br /> ! Our Terminology !! Description !! Terminonlogy !! Data (UART) Representation !! When Idle<br /> |-<br /> | A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High<br /> |-<br /> | B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low<br /> |}<br /> <br /> <br /> <br /> {| class="wikitable" style="text-align: center;" <br /> |+ Manufacturer's Labeling<br /> |-<br /> ! Non-inverting !! Inverting !! Class !! Manufacturer examples !!<br /> |-<br /> | A || B || Nominal || BITS, FieldServer<br /> |-<br /> | + || - || Symbol || BACnet Specification || The non-inverting input of the<br /> EIA-485 transceiver is designated in this specification as "plus" or "+" <br /> |-<br /> | RT+ || RT- || || EnOcean SmartServer IoT<br /> |-<br /> | + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300<br /> |-<br /> | B+ || A- || This is obviously contrary to everyone else || MBS UBR-01 Mk II<br /> |-<br /> | 485+ || 485- || Symbol || FieldServer<br /> |-<br /> | U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]<br /> |-<br /> | B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]<br /> |-<br /> | A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485], AirBox<br /> |-<br /> | 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]<br /> |-<br /> | ? || ? || || KMC router, A- and B+, true polarity TBC<br /> |}<br /> <br /> The BACnet Specification (135 - 9.2.2) says: The non-inverting input of the<br /> 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." <br /> <br /> 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 ! :<br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ RS-485 Bus State Terminology<br /> |-<br /> ! UART input/output !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 Bus Binary state<br /> |-<br /> | 1 || A > B|| Mark/Idle || On || Logic 0<br /> |-<br /> | 0 || A < B || Space || Off || Logic 1<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Standard&diff=13712 BACnet Standard 2026-02-09T19:05:00Z

<p>BACnetEd: </p> <hr /> <div>The BACnet Standard can be purchased from the ASHRAE Bookstore.<br /> <br /> <br /> The official BACnet Website [https://bacnet.org/ is this]. <br /> <br /> For the official BACnet standard go to this link and search for "BACnet 135"<br /> <br /> For the official BACnet *TEST* standard go to this link and search for "BACnet 135.1"<br /> <br /> <br /> <br /> 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"</div>

BACnetEd http://bacnetwiki.com/index.php?title=BTL_Procedure&diff=13711 BTL Procedure 2025-11-29T19:34:46Z

<p>BACnetEd: </p> <hr /> <div>Here is a summary/checklist to get your device through the BTL certification process:<br /> <br /> * Pre-test your device using our BACnet Test Suite<br /> * 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)<br /> * Confirm they will test to Protocol Revision 26 (or perhaps higher)<br /> * Confirm they will provide an estimate (quote) based on the "BTL Functionality Checklist" that you will fill in<br /> * Find out when they can start testing, and estimate how long will it take<br /> * Confirm Payment terms<br /> * Ask for any other requirements they may have<br /> * Complete the "BTL Functionality Checklist". The original is in the "BTL Test Package-26" which can be downloaded from the BTL website<br /> * Send this to the candidate lab(s) and get a final estimate of the costs<br /> * 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.<br /> * Ask BTL for additional guidance<br /> * 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).<br /> * Select a Lab, proceed<br /> * [https://www.bac-test.com/ BITS] can assist you with this process.</div>

BACnetEd http://bacnetwiki.com/index.php?title=BTL_Procedure&diff=13710 BTL Procedure 2025-11-29T19:32:17Z

<p>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..."</p> <hr /> <div>Here is a summary/checklist to get your device through the BTL certification process:<br /> <br /> * Pre-test your device using our BACnet Test Suite<br /> * Contact the 4 labs, (link here) let them know that you are interested, confirm they can test your IUT (Implementation Under Test)<br /> * Confirm they will test to Protocol Revision 26 (or perhaps higher)<br /> * Confirm they will provide an estimate (quote) based on the "BTL Functionality Checklist" that you will fill in<br /> * Find out when they can start testing, and estimate how long will it take<br /> * Confirm Payment terms<br /> * Ask for any other requirements they may have<br /> * Complete the "BTL Functionality Checklist". The original is in the "BTL Test Package-26" which can be downloaded from the BTL website<br /> * Send this to the candidate lab(s) and get a final estimate of the costs<br /> * 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.<br /> * Ask BTL for additional guidance<br /> * 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).<br /> * Select a Lab, proceed<br /> * BITS can assist you with this process.</div>

BACnetEd http://bacnetwiki.com/index.php?title=Main_Page&diff=13709 Main Page 2025-11-29T19:28:05Z

<p>BACnetEd: </p> <hr /> <div><big>'''The new BACnetWiki'''</big><br /> <br /> This is a reboot of the BACnet Wiki for consolidating thoughts and discussions around BACnet. Email me at '''edward@bac-test.com''' if needed<br /> <br /> '''Resources'''<br /> * [[BACnet Product Gallery]] - Equipment, tools, services<br /> * [[BACnet Developer Resources]] - for BACnet Stack programmers<br /> * [[BACnet User Resources]] - for those of us who use BACnet devices<br /> * [[Facilities Manager Resources]] - for those responsible for a site containing hundreds or thousands of BACnet devices<br /> * [[Resources for Beginners]]<br /> * [[Installer Resources]] - help with installing BACnet systems<br /> <br /> * The [[BACnet Standard]]<br /> * [https://www.linkedin.com/groups/13566440/ BACnet Developers Group on LinkedIn]<br /> * [[BACnet Protocol]]<br /> * [[BIBBS - BACnet Interoperability Building Blocks]]<br /> * [[BACnet Services Supported]]<br /> * [[BACnet Addenda 135]]<br /> * [[BACnet Addenda 135.1]]<br /> * [[BACnet BTL Tests to final 135.1 Tracking]]<br /> * [[BACnet Interpretations]]<br /> * [[BTL Procedure | BTL Submittal Process]]<br /> * [[BTL Resources]]<br /> * [[BTL Test Plan]]<br /> * [[BTL Implementation Guideline]]<br /> * Proposed [[Diagnostic Object]]<br /> * [[BACnet Best Practices]]<br /> * [[BACnet Protocol Wish List]]<br /> * [[BACnet MS/TP Best Practices]]<br /> * [[RS-485 Polarity]]<br /> * [[BACnet Organizations]]<br /> * [[Book of Records]]</div>

BACnetEd http://bacnetwiki.com/index.php?title=DM-R-B_-_Device_Management_-_Restart&diff=13708 DM-R-B - Device Management - Restart 2025-11-29T12:20:44Z

<p>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..."</p> <hr /> <div>2025-11-29 I have asked this question<br /> My reference: oi00192<br /> <br /> Does a device *HAVE* to support sending a UCOV on restart? ... (Clause 19.3)<br /> <br /> "When a device is powered on, when it restarts due to a ReinitializeDevice service (ACTIVATE_CHANGES, COLDSTART<br /> or WARMSTART), or when it restarts for some other reason, the device shall transmit an UnconfirmedCOVNotification<br /> request. "<br /> <br /> (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)<br /> <br /> 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....</div>

BACnetEd http://bacnetwiki.com/index.php?title=BIBBS_-_BACnet_Interoperability_Building_Blocks&diff=13707 BIBBS - BACnet Interoperability Building Blocks 2025-11-29T12:19:44Z

<p>BACnetEd: </p> <hr /> <div>{| class="wikitable"<br /> |+ Table of BIBBs <br /> |-<br /> ! BIBB !! Category !! Description<br /> |-<br /> | [[DM-R-B - Device Management - Restart|DM-R-B]] || Device Manaement || Restart <br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=BIBBS_-_BACnet_Interoperability_Building_Blocks&diff=13706 BIBBS - BACnet Interoperability Building Blocks 2025-11-29T12:18:04Z

<p>BACnetEd: Created page with "{| class="wikitable" |+ Table of BIBBs |- ! BIBB !! Description |- | DM-R-B || Restart |}"</p> <hr /> <div>{| class="wikitable"<br /> |+ Table of BIBBs <br /> |-<br /> ! BIBB !! Description<br /> |-<br /> | DM-R-B || Restart <br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=Main_Page&diff=13705 Main Page 2025-11-29T12:14:41Z

<p>BACnetEd: </p> <hr /> <div><big>'''The new BACnetWiki'''</big><br /> <br /> This is a reboot of the BACnet Wiki for consolidating thoughts and discussions around BACnet. Email me at '''edward@bac-test.com''' if needed<br /> <br /> '''Resources'''<br /> * [[BACnet Product Gallery]] - Equipment, tools, services<br /> * [[BACnet Developer Resources]] - for BACnet Stack programmers<br /> * [[BACnet User Resources]] - for those of us who use BACnet devices<br /> * [[Facilities Manager Resources]] - for those responsible for a site containing hundreds or thousands of BACnet devices<br /> * [[Resources for Beginners]]<br /> * [[Installer Resources]] - help with installing BACnet systems<br /> <br /> * The [[BACnet Standard]]<br /> * [https://www.linkedin.com/groups/13566440/ BACnet Developers Group on LinkedIn]<br /> * [[BACnet Protocol]]<br /> * [[BIBBS - BACnet Interoperability Building Blocks]]<br /> * [[BACnet Services Supported]]<br /> * [[BACnet Addenda 135]]<br /> * [[BACnet Addenda 135.1]]<br /> * [[BACnet BTL Tests to final 135.1 Tracking]]<br /> * [[BACnet Interpretations]]<br /> * [[BTL Resources]]<br /> * [[BTL Test Plan]]<br /> * [[BTL Implementation Guideline]]<br /> * Proposed [[Diagnostic Object]]<br /> * [[BACnet Best Practices]]<br /> * [[BACnet Protocol Wish List]]<br /> * [[BACnet MS/TP Best Practices]]<br /> * [[RS-485 Polarity]]<br /> * [[BACnet Organizations]]<br /> * [[Book of Records]]</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Addenda_135.1&diff=13704 BACnet Addenda 135.1 2025-11-22T12:26:47Z

<p>BACnetEd: </p> <hr /> <div>{| class="wikitable"<br /> |+ BACnet 135.1 Addenda<br /> |-<br /> ! Addendum !! Date !! Description !! Link<br /> |-<br /> | 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]<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Addenda_135.1&diff=13703 BACnet Addenda 135.1 2025-11-22T12:24:00Z

<p>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] |}"</p> <hr /> <div>{| class="wikitable"<br /> |+ BACnet 135.1 Addenda<br /> |-<br /> ! Header text !! Header text !! Header text<br /> |-<br /> | 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]<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Addenda&diff=13702 BACnet Addenda 2025-09-25T13:49:58Z

<p>BACnetEd: </p> <hr /> <div>BACnet Addenda can be found [https://www.ashrae.org/technical-resources/standards-and-guidelines/standards-addenda on the ASHRAE website]<br /> <br /> <br /> {| class="wikitable"<br /> |+ BACnet Addenda<br /> |-<br /> ! Standard !! Addendum !! Description<br /> |-<br /> | 135-2016|| bj|| BACnet Secure Connect / BACnet/SC<br /> |-<br /> | 135-|| br|| Writing NULL to non-commandable properties must result in ACK<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=RS-485_Polarity&diff=13701 RS-485 Polarity 2025-07-31T14:41:58Z

<p>BACnetEd: </p> <hr /> <div>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.<br /> <br /> '''Basic Rule from the specification (and I have the actual specification)<br /> <br /> * A > B means "binary 0 on the bus" or "ON".<br /> * A < B means "binary 1 on the bus" or "OFF".<br /> <br /> And A is non-inverting (and thus B is inverting)<br /> <br /> '''Identifying 'A' and 'B' signals'''<br /> <br /> Remember that UARTs output a logic '1' (high voltage) for idle state! This signal will go to 0v for the start bit. <br /> <br /> 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]<br /> <br /> <br /> '''Identifying 'Mark/Idle' and 'Space' '''<br /> <br /> 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.<br /> <br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ Nominal Terminology<br /> |-<br /> ! Our Terminology !! Description !! Terminonlogy !! Data (UART) Representation !! When Idle<br /> |-<br /> | A || Tracking UART value || Non-Inverting || A is high when UART emitting 1, A is low when UART emitting 0 || High<br /> |-<br /> | B || Non-tracking || Inverting || B is low when UART emitting 1, B is high when UART emitting 0 || Low<br /> |}<br /> <br /> <br /> <br /> {| class="wikitable" style="text-align: center;" <br /> |+ Manufacturer's Labeling<br /> |-<br /> ! Non-inverting !! Inverting !! Class !! Manufacturer examples !!<br /> |-<br /> | A || B || Nominal || BITS, FieldServer<br /> |-<br /> | + || - || Symbol || BACnet Specification || The non-inverting input of the<br /> EIA-485 transceiver is designated in this specification as "plus" or "+" <br /> |-<br /> | RT+ || RT- || || EnOcean SmartServer IoT<br /> |-<br /> | + || - || Symbol || FT-Click, BASRouter LX, Onicon F-4300<br /> |-<br /> | B+ || A- || || MBS UBR-01 Mk II<br /> |-<br /> | 485+ || 485- || Symbol || FieldServer<br /> |-<br /> | U+ || U- || || [https://en.wikipedia.org/wiki/RS-485#Waveform_example Wikipedia]<br /> |-<br /> | B || A || || [https://en.wikipedia.org/wiki/RS-485#Signals Wikipedia. See, what a fiasco]<br /> |-<br /> | A+ || B- || || [https://www.waveshare.com/product/iot-communication/wired-comm-converter/usb-to-rs485.htm Waveshare USB to RS-485], AirBox<br /> |-<br /> | 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]<br /> |-<br /> | ? || ? || || KMC router, A- and B+, true polarity TBC<br /> |}<br /> <br /> The BACnet Specification (135 - 9.2.2) says: The non-inverting input of the<br /> 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." <br /> <br /> 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 ! :<br /> <br /> {| class="wikitable" style="text-align: center;"<br /> |+ RS-485 Bus State Terminology<br /> |-<br /> ! UART input/output !! A vs B !! Legacy !! RS-485 Bus State !! RS-485 Bus Binary state<br /> |-<br /> | 1 || A > B|| Mark/Idle || On || Logic 0<br /> |-<br /> | 0 || A < B || Space || Off || Logic 1<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Addenda_135&diff=13700 BACnet Addenda 135 2025-07-30T13:16:24Z

<p>BACnetEd: </p> <hr /> <div>{| class="wikitable"<br /> |+ Caption text<br /> |-<br /> ! Addendum !! Topics !! Comment<br /> |-<br /> | 135-2012bb || ZeroConfig || Example<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Addenda_135&diff=13699 BACnet Addenda 135 2025-07-30T13:16:11Z

<p>BACnetEd: Created page with "{| class="wikitable" |+ Caption text |- ! Addendum !! Topics !! Comment |- | 135-2012bb || ZeroCcnfig || Example |}"</p> <hr /> <div>{| class="wikitable"<br /> |+ Caption text<br /> |-<br /> ! Addendum !! Topics !! Comment<br /> |-<br /> | 135-2012bb || ZeroCcnfig || Example<br /> |}</div>

BACnetEd http://bacnetwiki.com/index.php?title=PICS_-_Protocol_Implementation_Conformance_Statement&diff=13698 PICS - Protocol Implementation Conformance Statement 2025-07-20T19:01:36Z

<p>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]"</p> <hr /> <div>This document describes the BACnet implementation of your device, mainly for Systems Integrators to review for suitability for task.<br /> <br /> A template can be found here [https://bacnet.org/conformance-pics/ here]</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Test_Suite_-_Top_10_Scores&diff=13697 BACnet Test Suite - Top 10 Scores 2025-07-12T13:16:04Z

<p>BACnetEd: </p> <hr /> <div>{| class="wikitable"<br /> |+ Weighted Test Results<br /> |-<br /> ! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Bayesian Score<br /> |-<br /> | 1 || SMC || FS-Router-BAC2 || V2.08n || || 78%<br /> |-<br /> | 2 || CCR || BASRouterLX || 1.43 || 2.0.0 || 78%<br /> |-<br /> | 3 || JCI || TEC3612-00 || 2.0.5.0200 || || 74%<br /> |-<br /> | 4 || JCI || MS-NCE25 || 6.2.2.6 || || 74%<br /> |-<br /> | 5 || MBS || UBR-01 / MK II || 1.23.0.1 || 6.0.0.0 || 73%<br /> |-<br /> | 6 || JCI || MS-VMA1620-0 || 6.2.2.6 || || 73%<br /> |-<br /> | 7 || ASI || 9540 || 3.6.119 || || 72%<br /> |-<br /> | 8 || JCI || MS-NCE2566-0 || 9.0.7.7978 || || 69%<br /> |-<br /> | 9 || Steve Karg || bacnet-stack || 1.4.1 || || 65%<br /> |-<br /> | 10 || JCI || TL-BRTRP-0 || 2.0.22 || || 52%<br /> |}<br /> <br /> <br /> Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]</div>

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Test_Suite_-_Top_10_Scores&diff=13696 BACnet Test Suite - Top 10 Scores 2025-07-12T11:13:10Z

<p>BACnetEd: </p> <hr /> <div>{| class="wikitable"<br /> |+ Weighted Test Results<br /> |-<br /> ! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Bayesian Score<br /> |-<br /> | 1 || CCR || BASRouterLX || 1.43 || 2.0.0 || 78%<br /> |-<br /> | 2 || JCI || TEC3612-00 || 2.0.5.0200 || || 74%<br /> |-<br /> | 3 || JCI || MS-NCE25 || 6.2.2.6 || || 74%<br /> |-<br /> | 4 || MBS || UBR-01 / MK II || 1.23.0.1 || 6.0.0.0 || 73%<br /> |-<br /> | 5 || JCI || MS-VMA1620-0 || 6.2.2.6 || || 73%<br /> |-<br /> | 6 || ASI || 9540 || 3.6.119 || || 72%<br /> |-<br /> | 7 || JCI || MS-NCE2566-0 || 9.0.7.7978 || || 69%<br /> |-<br /> | 8 || Steve Karg || bacnet-stack || 1.4.1 || || 65%<br /> |-<br /> | 9 || Steve Karg || mods4bts || 1.4.1 || || 65%<br /> |-<br /> | 10 || JCI || TL-BRTRP-0 || 2.0.22 || || 52%<br /> |}<br /> <br /> <br /> Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]</div>

BACnetEd http://bacnetwiki.com/index.php?title=BTL_Resources&diff=13695 BTL Resources 2025-07-10T17:01:16Z

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

BACnetEd http://bacnetwiki.com/index.php?title=BACnet_Test_Suite_-_Top_10_Scores&diff=13693 BACnet Test Suite - Top 10 Scores 2025-07-08T12:14:45Z

<p>BACnetEd: </p> <hr /> <div>{| class="wikitable"<br /> |+ Weighted Test Results<br /> |-<br /> ! Rank || Manufacturer !! Model !! FW Ver !! App Ver !! Bayesian Score<br /> |-<br /> | 1 || CCR || BASRouterLX || 1.43 || 2.0.0 || 75%<br /> |-<br /> | 2 || MBS || UBR-01 / MK II || 1.23.0.1 || 6.0.0.0 || 71%<br /> |-<br /> | 3 || ASI || 9540 || 3.6.119 || || 70%<br /> |-<br /> | 4 || Steve Karg || bacnet-stack || 1.4.1 || || 63%<br /> |-<br /> | 5 || Steve Karg || mods4bts || 1.4.1 || || 63%<br /> |}<br /> <br /> <br /> Calculations [https://docs.google.com/spreadsheets/d/10hQ19MxwiUfu5mEjeVNorlavk6PW3xp5qNoXWwZ1FUI/edit?gid=0#gid=0 done here]</div>

BACnetEd