Protocol Standards - Open vs Closed
Every control system on a project is built on either an open standard - published, independently certified, multi-vendor - or a closed / proprietary protocol owned by one manufacturer. This distinction matters more than almost any other spec decision on a project.
See the difference
What defines it
- 1Specification is published and freely (or cheaply) available - anyone can read exactly how the protocol works.
- 2Independent certification body tests devices for real compliance (KNX Association, BACnet BTL listing, DALI Alliance, etc.).
- 3Multiple manufacturers build compliant, interoperable hardware - no single company controls the standard.
- 4An integrator who didn't do the original install can still service, expand or fault-find the system.
What defines it
- 1Protocol is owned and controlled by a single manufacturer - the spec is usually not public.
- 2Only that manufacturer's own hardware, software and app can join the system.
- 3Certification, if any, is internal - "compatible" means "compatible with our own ecosystem".
- 4Service and expansion depend on staying within that one brand's dealer network, often for the life of the system.
Why we support open protocols
The honest case for a closed system
Quick reference - is it open or closed?
| Protocol | Type | Governing body | Note |
|---|
Top 5 Closed Protocol Systems
The proprietary whole-home platforms you'll most often meet on high-end residential and commercial AV/control scopes. Tap a card for more detail.
Building Overview
Live summary of every system below. Values update the instant you change a control anywhere in this program - this is exactly what a BMS supervisory screen does with real field data.
How this lab is built
Every control writes to one shared building state, the same way real field devices report back to a BMS server. Open the Live Bus Monitor at the bottom and start pressing things - you'll see the actual protocol telegram each action generates. Head to Protocols & Topology to click through KNX, Modbus, DALI and more and see the panel wiring behind each one.
Lighting & Dimming - All Methods in One Place
Three different ways to dim a light, all doing the same job through different wiring and logic. Switch between them below - each one drives the same style of virtual bulb so you can compare how the dimming behaves.
HVAC - Zone Temperature Control
Each zone has a setpoint, a current temperature, a mode and a fan speed. Change the setpoint and watch the current reading drift toward it, and the airflow indicator react - the same sense → decide → act → confirm loop from the training notes, running continuously.
Blinds & Shading
Motorised blind position, 0% (fully closed) to 100% (fully open). Drag the slider and watch the blind visual respond.
Security & Access Control
Arm/disarm, monitor zone sensors, operate door locks, and connect this device's own camera as a live CCTV preview tile.
Alarm Mode
Door Locks
Monitored Zones
Live Camera Feed - This Device
How a real CCTV point works
A physical camera streams over the same Cat6/IP network as the rest of the BMS, usually on a segregated VLAN. The NVR (recorder) pulls each stream continuously; the app or workstation only requests a live view on demand - which is what this browser demo represents using your own device's camera instead of a real IP camera.
- 1Camera → PoE switch (power + data on one Cat6 cable)
- 2Switch → NVR (continuous recording) and → BMS/VMS server (live monitoring)
- 3VMS server → operator workstation / mobile app, same pattern as this demo tile
Scenes - One Trigger, Many Actions
A scene fires a stored combination of settings across lighting, HVAC, blinds and security in a single command. Press one and watch the live preview below - plus every other panel and the bus monitor - update at once.
Live preview - what just happened
Site Troubleshooting Assistant
Type what's happening on site - flickering, not responding, stuck, offline - pick the system if you know it, and get a checklist of likely causes to work through. Still generates useful steps even if the brand isn't listed.
Material Submittal Review - Comment Checklist
Pick the system or protocol the contractor's material submittal covers. Every item ticked below becomes a formatted review comment in consultant revise/resubmit style - untick anything already compliant before copying.
Generated review comments
Shop Drawing Review - Comment Checklist
Pick the system or protocol the contractor's shop drawing package covers. Same logic as material review, but focused on what the drawing itself must show - topology, addressing, routing and coordination.
Generated review comments
Communication Protocols & Topology
Click a protocol to inspect it. Every one shows the real DB-level panel wiring, its network topology, and a live dimming demo running in that protocol's own style - instant snap for Modbus, smooth fade for KNX/DALI, staged hop-by-hop for a mesh network.
Wireless & Mesh - How a Packet Actually Travels
Zigbee and Z-Wave devices don't talk straight to a router the way Wi-Fi does - they relay through each other in a mesh until the message reaches the coordinator, which then bridges it onto the IP network. Press play to watch one packet make that journey in slow motion.
Mesh network (Zigbee / Z-Wave)
Star network (Wi-Fi / Bluetooth)
No relaying - simple, but every device needs a strong direct signal to the access point, and range/battery life suffer. This is why Wi-Fi smart plugs sometimes drop out where a Zigbee sensor in the same spot stays connected: the Zigbee device can hop through a neighbour.
Wiring Diagrams - Annotated
Simplified field-wiring schematics with the reasoning spelled out underneath - not just what's connected, but why it has to be connected that way. Not for construction - for concept only.
Brands & Manufacturers
Widely used suppliers by system/protocol, useful for reading submittals and knowing who else is in the market before you review a technical datasheet. Not exhaustive, and not an endorsement - a reference starting point only.
Engineer’s Notes
My own working notes - wire counts, I/O per point, what actually needs power vs. just signal, and the stuff I keep having to look up on site. Click a card to open it.