What DM-DCC-B Is
DM-DCC-B (Device Management-Device Communication Control-B) is the BACnet Interoperability Building Block (BIBB) for a device that executes DeviceCommunicationControl: an operator or tool can tell the device to stop initiating BACnet traffic, or to stop responding to most services as well, for a bounded duration or indefinitely.
A device claiming DM-DCC-B is the server side of this exchange. Initiating DeviceCommunicationControl is an operator-workstation behavior and is not part of this BIBB.
What It Requires
| Piece | What it does |
|---|---|
| Password handling | A device that requires a password refuses the request without it |
| Duration handling | The device resumes on its own once a bounded duration elapses; an indefinite disable requires another DeviceCommunicationControl, a ReinitializeDevice, or a local action to lift |
| Disable scope | The device honors both the initiation-only and the full response-disable variants of the request |
Where You Meet It in the Field
Any controller a technician can quiet during diagnostics, or an operator can silence during a commissioning cleanup, is claiming DM-DCC-B. It matters most on a noisy or misbehaving device, where silencing it is how you isolate whether it or the network is the problem.
[!WARNING] A device disabled indefinitely and unreachable locally can strand itself. The DeviceCommunicationControl reference covers the recovery path in detail before you rely on an indefinite disable in the field.
What Chipkin Provides
The CAS BACnet Stack supports DM-DCC-B today, including timed and indefinite durations and password handling, with a specific BTL PASS behind the DeviceCommunicationControl behavior. Talk to us about your specific device-management scenario.