ZIP_MOTOR_CONTROL_UNINITIALIZED
Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for ZIP_MOTOR_CONTROL_UNINITIALIZED) as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm triggers if any of the motors have never transmitted a feedback message.
This is expected to happen on boot or Zip Exec restart until we start preflight.
If this persists throughout preflight and causes a mission failure, follow the steps below.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
find-the-alarm-report-aircraft-droid-a["<small><b>Step 1</b></small><br/>Action: Find the alarm report: Aircraft/Droi..."]
determine-what-motor-triggered-the-ala["<small><b>Step 2</b></small><br/>Action: Determine what motor triggered the al..."]
check-firmware-software-for-the-motor["<small><b>Step 3</b></small><br/>Action: Check firmware software for the motor..."]
is-boot-role-boot-role-boot{"<small><b>Step 4</b></small><br/>Question: Is boot_role BOOT_ROLE_BOOT?"}
power-cycle-the-zip-and-re-attempt-a-f{{"<small><b>Step 5</b></small><br/>Escalation: Power cycle the zip and re-attempt a ..."}}
follow-the-zip-motor-control-unavailab("<small><b>Step 6</b></small><br/>Reference: Follow the watchdog alarm guide for t...")
find-the-alarm-report-aircraft-droid-a --> determine-what-motor-triggered-the-ala
determine-what-motor-triggered-the-ala --> check-firmware-software-for-the-motor
check-firmware-software-for-the-motor --> is-boot-role-boot-role-boot
is-boot-role-boot-role-boot -->|Yes| power-cycle-the-zip-and-re-attempt-a-f
is-boot-role-boot-role-boot -->|No| follow-the-zip-motor-control-unavailab
style find-the-alarm-report-aircraft-droid-a fill:#dcfce7,stroke:#22c55e,color:#14532d
style determine-what-motor-triggered-the-ala fill:#dcfce7,stroke:#22c55e,color:#14532d
style check-firmware-software-for-the-motor fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-boot-role-boot-role-boot fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-the-zip-and-re-attempt-a-f fill:#fef3c7,stroke:#f59e0b,color:#78350f
style follow-the-zip-motor-control-unavailab fill:#f3e8ff,stroke:#a855f7,color:#581c87 Hover or focus a block to preview it. Select the block to keep the preview open.
In the alarm report, check the identifier for the watchdog. Multiple identifiers may be listed. Each identifier corresponds to a motor.
Run the “Retrieve Software Status” Troubleshooting Commands
Find the motor in the software list that corresponds to the identifier from the previous step, and check the boot role:
servo_tail_port_aftFirmware: bbb73bacd0e169086df33ac252b119556d265b8eApps: 5e5672409ec58a1971c6851f729a5938fbe19d46Role: BOOT_ROLE_BOOTResolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.