← Back to the chapter · Previous detail · Next detail →

Technical detail · CoAP Observe: Efficiency and Lifecycle

Why urgent motor notifications can exceed a routine cap

A motor-vibration notification model assumes sparse updates, but its urgent-send rule can defeat its routine rate limit.

A motor-vibration example illustrates why a measured send trace matters. Its calculation assumes three notifications per motor per day, including urgent sends. Its routine code path requires both a value change of at least 0.5 mm/s and a 60-second interval. An urgent crossing of 4.5 mm/s bypasses that interval. These are teaching thresholds, not validated machine safety limits.

The routine cap therefore supplies no overall flood bound. A routine send of 4.0 mm/s after a notified value of 4.5 mm/s can permit an immediate urgent send of 4.5 mm/s. Repeating that pattern can exceed the routine daily count. Count actual sends, including urgent traffic, before applying the sparse-notification estimate. For a thermostat notification rule, ask the same question: what does the implemented sending rule actually allow?

← Back to the chapter · Previous detail · Next detail →