What BTL Is
The BACnet Testing Laboratory (BTL), operated by BACnet International, is the accredited body that tests a BACnet device against the standard and issues a BTL Listing when it passes. A BTL Listing is evidence a third party verified a device’s conformance claims; it is not the same thing as a device that simply interoperates on a bench, because bench testing only exercises the paths an integrator happens to think to try.
The PICS Is the Contract
A vendor submits a device along with a Protocol Implementation Conformance Statement (PICS): a document declaring exactly which BIBBs, which object types, and which standardized device profile the device claims. The PICS is the contract. BTL runs its test suite against every claim the PICS makes, not against the device in general, so a device that claims less is tested against less, and a device that overclaims fails the scenarios behind whatever it claimed but does not actually do.
How a Scenario Works
A BTL scenario is not a smoke test. It sets a specific precondition on the Implementation Under Test (IUT), sends a stimulus, and verifies the response down to frame structure, tag types, and property values, not just whether a value looks approximately right in a packet capture. The suite runs more than 1,100 such scenarios, and many are deliberately subtle: segmentation behavior under load, a subscription lifetime expiring mid-notification, a router’s behavior at a network boundary. Those are exactly the conditions a bench test, run by one integrator on a quiet network, is least likely to reproduce.
Result Classes: PASS, FAIL, SKIP
A conformance report scores every scenario one of three ways. PASS means the device answered correctly, down to frame structure and tag types. FAIL means it answered wrongly or did not answer where a response was required. SKIP means the scenario does not apply to this device at all, a scenario needing a Schedule object on a device that does not model schedules, for example, and is neither a pass nor a failure. Treating a SKIP as a PASS inflates a coverage number without changing what was actually verified, and it is not how BTL itself scores a submission. The full breakdown covers this in more detail.
What Chipkin Provides
The CAS BACnet Stack 5.x line is BTL listed and in the field on tens of thousands of devices. The Chipkin BACnet Testing Tool, the same harness Chipkin uses internally to validate every commit, is available to point at your own device before a BTL submission, after a firmware change, or inside a CI pipeline. Talk to us about a pre-submission test run.
Where to Go Next
- Why bench testing isn’t enough, and what BTL catches that it doesn’t: Why “It Works on My Bench” Is Not BTL Conformance
- Reading a coverage report: Understanding BTL Results: PASS, FAIL, SKIP
- The tool behind pre-submission testing: How the Chipkin BACnet Testing Tool Works Under the Hood
- BACnet Device Profiles
- BACnet BIBBs
- BACnet