DM-R-B - Device Management - Restart

From BACnet Wiki
Revision as of 04:20, 29 November 2025 by BACnetEd (talk | contribs) (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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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 above implies otherwise..., and any Network_Port modification, requiring an ACTIVATE_CHANGES will too)

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....

Retrieved from "http://bacnetwiki.com/index.php?title=DM-R-B_-_Device_Management_-_Restart&oldid=13708"