Transport paths and boundaries
Release v0.11.0. For newer owner APIs and actual wire qualification, use the current transport evidence matrix.
A transport appearing in the codebase is not the same as every package, CLI binary, operating system, and hardware combination supporting that transport equally.
Choose a path
Section titled “Choose a path”| Path | How to start | Important boundary |
|---|---|---|
| BACnet/IP | CLI, Python client, or Rust client | Direct reads, discovery, and routed traffic are distinct tests |
| BACnet/IPv6 | CLI --ipv6, Python, or Rust feature path |
Requires appropriate IPv6 addressing/interface and network validation |
| BACnet/SC | SC-enabled CLI, Python, or Rust | Certificate trust, local identities, and hub behavior must be configured |
| MS/TP | Rust serial path or Python mini-device | No reviewed CLI transport flag; qualify the actual serial hardware |
| Ethernet/802.3 | Advanced Rust transport path | Platform/privilege evidence is incomplete; not a general CLI tutorial |
This is a guide to entry points, not a formal supported-platform or conformance matrix.
Separate BACnet/IP, BACnet/SC, and MS/TP topology examples.
Features are package-specific
Section titled “Features are package-specific”The v0.11.0 CLI manifest enables its IPv6 path and defines optional sc-tls and pcap features. Its default optional-feature list is empty. The Python binding manifest enables underlying SC, IPv6, and serial transport features, but a Cargo feature selection alone is not proof of an installable or qualified wheel on a particular host.
Inspect the selected binary or wheel and its release build configuration. Do not turn a code-level table into five identical “fully supported” badges.
Do not infer these capabilities
Section titled “Do not infer these capabilities”There is no browser-based BACnet transport promised by this site. The release notes withdraw unsupported WASM surfaces. A demo or a codec is not a complete browser network interface.
The README does not claim Annex J NAT traversal or IPv4 BACnet/IP multicast. A BBMD setup guide must not accidentally imply either. A standalone MS/TP device example is not a combined client/server endpoint claim, and the presence of segmentation code elsewhere does not automatically qualify end-to-end segmented MS/TP.
Understand the evidence labels
Section titled “Understand the evidence labels”The project’s conformance ledger distinguishes implementation presence, missing tests or source review, specifically evidenced clause behavior, deferred decisions, and unsupported designs. Preserve those distinctions when describing a feature.
A row with clause-specific evidence supports that row’s stated scope. It does not upgrade the whole object, service family, transport, or product to full conformance. The generated draft PICS and ledger are not a BTL certification.
Which guide next?
Section titled “Which guide next?”Start with connection configuration for BACnet/IP, SC setup for hub/certificate deployments, or MS/TP commissioning for serial labs.
Sources and release scope
Section titled “Sources and release scope”These instructions target v0.11.0. Source review is not a claim of hardware qualification.
Release scope · CLI features · Python transport features · Conformance evidence.
Release v0.11.0 ·Current development. Follow the scope named on each page. Pre-1.0 APIs; partial conformance.Support & limitations