ZIP_MIXED_MOTOR_TEMPERATURE_UNINITIALIZED
Applicable alarms (1)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last 90 days 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 the motors have never received a transmitted feedback message from the mixed motor
This is expected to happen on boot or Zip Exec restart until we start preflight after the motors are turned on.
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-al["<small><b>Step 1</b></small><br/>Action: Find the alarm report: Aircraft/Droi..."]
determine-which-fwd-motor-triggered-the["<small><b>Step 2</b></small><br/>Action: Determine which fwd motor triggered t..."]
check-firmware-software-for-the-motor-v["<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-aircraft-power-cycle-ai["<small><b>Step 5</b></small><br/>Action: Power cycle the Aircraft Power Cycl..."]
re-attempt-a-flight["<small><b>Step 6</b></small><br/>Action: Re-attempt a flight."]
if-the-issue-persists-escalate-to-p2-fi{{"<small><b>Step 7</b></small><br/>Escalation: If the issue persists, escalate to P2..."}}
follow-the-zip-aft-motor-temperature-un("<small><b>Step 8</b></small><br/>Reference: Follow the MOTOR_TEMP_MIXED_UNAVAILA...")
find-the-alarm-report-aircraft-droid-al --> determine-which-fwd-motor-triggered-the
determine-which-fwd-motor-triggered-the --> check-firmware-software-for-the-motor-v
check-firmware-software-for-the-motor-v --> is-boot-role-boot-role-boot
is-boot-role-boot-role-boot -->|Yes| power-cycle-the-aircraft-power-cycle-ai
is-boot-role-boot-role-boot -->|No| follow-the-zip-aft-motor-temperature-un
power-cycle-the-aircraft-power-cycle-ai --> re-attempt-a-flight
re-attempt-a-flight --> if-the-issue-persists-escalate-to-p2-fi
style find-the-alarm-report-aircraft-droid-al fill:#dcfce7,stroke:#22c55e,color:#14532d
style determine-which-fwd-motor-triggered-the fill:#dcfce7,stroke:#22c55e,color:#14532d
style check-firmware-software-for-the-motor-v fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-boot-role-boot-role-boot fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-the-aircraft-power-cycle-ai fill:#dcfce7,stroke:#22c55e,color:#14532d
style re-attempt-a-flight fill:#dcfce7,stroke:#22c55e,color:#14532d
style if-the-issue-persists-escalate-to-p2-fi fill:#fef3c7,stroke:#f59e0b,color:#78350f
style follow-the-zip-aft-motor-temperature-un 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_aft
Firmware: bbb73bacd0e169086df33ac252b119556d265b8e
Apps: 5e5672409ec58a1971c6851f729a5938fbe19d46
Role: 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.