Video · Wake on event — fast enough to catch a fleeing vehicle
Wake on impact. Wake on a CAN frame. Wake on a cloud command.
Seven wake sources cover the lifecycle of a parked or sleeping vehicle. Time-to-ready is under five seconds — fast enough to catch a vehicle that just started moving.
How it works
Seven sources. One power manager. Under five seconds.
Seven wake sources — Ignition, Alarm, RTC, CAN frame, Movement, Modem, Disturbance — all feed the power manager, which brings the box to ready state in under five seconds.
flowchart LR IG[Ignition<br/>vehicle ignition signal] --> PM[Power manager] AL[Alarm<br/>external alarm input] --> PM RT[RTC<br/>scheduled wall-clock / relative timer] --> PM CA[CAN frame<br/>CAN ID match] --> PM MV[Movement<br/>accelerometer threshold] --> PM MO[Modem<br/>cloud-issued remote wake] --> PM DI[Disturbance<br/>G-sensor impact threshold] --> PM PM --> BR[Box ready<br/>< 5 s]
| Source | Trigger | Use | Time-to-ready |
|---|---|---|---|
| Ignition | Vehicle ignition signal | Standard fleet box | < 5 s |
| Alarm | External alarm input | Burglar / panic-button | < 5 s |
| RTC | Scheduled wall-clock or relative timer | Periodic health upload / end-of-day | < 5 s |
| CAN frame | CAN ID match | Wake on specific signal — harness fault / door open | < 5 s |
| Movement | Accelerometer threshold | Vehicle moves while parked → wake to record | < 5 s |
| Modem | Cloud-issued remote wake | Operator wakes for live stream / clip pull | < 5 s |
| Disturbance | G-sensor impact threshold | Crash / break-in event capture | < 5 s |
What you do not write
The infrastructure MOS4 ships.
configure_wake_events Power-manager wake-source bitmask — configure which of the seven sources are active for the next sleep cycle. One call; the micro service owns the hardware register writes and source arbitration.
set_rtc_wake_time RTC wake scheduler — set a wall-clock timestamp or a relative offset for the next scheduled wake. Used for periodic health upload, end-of-day reporting, or any time-driven resume cycle.
get_wake_reason / clear_wake_reason Wake-reason read and clear — call once after resume to read the bitmask identifying the triggering source, then clear before the next sleep. The power manager owns the reason register and discriminates boot-vs-wake automatically.
boot-vs-wake discrimination The power manager distinguishes a cold boot from a wake-from-sleep at startup. Integration code sees a clean wake-reason bitmask — no raw hardware register inspection required.
request_reboot_on_idle / request_shutdown_on_idle Override-next-idle hooks — schedule a reboot or shutdown at the end of the current active window without interrupting in-flight recording or upload. The micro service waits for the idle condition before executing.
FAQ
Frequently asked questions
-
Can I wake the box on a specific CAN frame ID?
Yes. The CAN frame wake source matches on a configured CAN ID — the power manager monitors the bus and triggers resume when the matching frame is seen. This covers signals such as a harness fault, door-open event, or any application-specific frame without writing a custom wake handler.
-
What happens when the G-sensor detects an impact while the box is asleep?
The Disturbance wake source monitors the G-sensor against a configurable impact threshold. When the threshold is crossed — crash or break-in — the power manager resumes the box in under five seconds, giving the recording pipeline enough time to capture the event.
-
How does cloud-triggered remote wake work?
The Modem wake source allows an operator to issue a remote wake command from the cloud. The modem stays in a low-power listen state and signals the power manager on receipt of the command. The box is ready in under five seconds — fast enough to start a live stream or pull a clip on demand.
-
How do I read the wake reason after the box resumes?
Call get_wake_reason() once after resume to read the bitmask identifying which source triggered the wake, then call clear_wake_reason() to reset it before the next sleep cycle. The power manager owns the reason register; no integration code is required to handle the boot-vs-wake discrimination.
-
How fast is the box ready after a wake event?
Time-to-ready is under five seconds for all seven wake sources — fast enough to catch a vehicle that just started moving, or to capture a break-in impact. The power manager handles the full resume sequence, including discriminating between a cold boot and a wake-from-sleep, without integration code.
Seven sources. One resume sequence. Under five seconds.
Ignition, Alarm, RTC, CAN frame, Movement, Modem, Disturbance — configure the sources that fit your deployment and we will sketch the power lifecycle.
Continue