ZIP_EXECUTIVE_CODE_PRE_MOTOR_CHECKS_MOTORS_TOO_HOT
Viewing this guide for
Applicable alarms (7)
ZIP_EXECUTIVE_CODE_PRE_MOTOR_CHECKS_MOTORS_TOO_HOTZIP_EXECUTIVE_V4_MIXED_TEMPS_EXCEED_PREFLIGHT_THRESHOLDZIP_EXECUTIVE_V4_MOTOR_TEMPS_EXCEED_PREFLIGHT_THRESHOLDZIP_EXECUTIVE_V4_PORT_AFT_TEMPS_EXCEED_PREFLIGHT_THRESHOLDZIP_EXECUTIVE_V4_PORT_FWD_TEMPS_EXCEED_PREFLIGHT_THRESHOLDZIP_EXECUTIVE_V4_STBD_AFT_TEMPS_EXCEED_PREFLIGHT_THRESHOLDZIP_EXECUTIVE_V4_STBD_FWD_TEMPS_EXCEED_PREFLIGHT_THRESHOLD
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for ZIP_EXECUTIVE_CODE_PRE_MOTOR_CHECKS_MOTORS_TOO_HOT) as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”Motor board temperatures need to be below 65C prior to spinning motors for the first time. If either the board or motor temp is above this 65C threshold then preflight will fail.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
apply-template-motor-temps-preflight-to["<small><b>Step 1</b></small><br/>Action: Apply template Motor Temps Preflight..."]
are-any-motors-above-65c{"<small><b>Step 2</b></small><br/>Question: Are any motors above 65C?"}
are-any-temperatures-missing{"<small><b>Step 3</b></small><br/>Question: Are any temperatures missing?"}
use-actuator-faults-due-to-missing-feedback("<small><b>Step 4</b></small><br/>Reference: Use the missing-feedback guide for th...")
power-off-the-aircraft["<small><b>Step 5</b></small><br/>Action: Power OFF the Aircraft."]
wait-5-minutes-for-the-motors-to-cool["<small><b>Step 6</b></small><br/>Action: Wait 5 minutes for the motors to cool..."]
escalate-to-p2-zip-exec{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to P2 Exec On Call."}}
resend-a-health-checks-mission-is-the{"<small><b>Step 8</b></small><br/>Question: Resend a Health Checks Mission. Is th..."}
release-zip-back-into-service["<small><b>Step 9</b></small><br/>Action: Release zip back into service"]
load-mission-and-check-motor-thermistors["<small><b>Step 10</b></small><br/>Telemetry: Load the failed mission and inspect t..."]
are-there-signs-of-thermistor-damage{"<small><b>Step 11</b></small><br/>Question: Are there signs of thermistor damage ..."}
if-the-issue-is-not-resolved-escalate{{"<small><b>Step 12</b></small><br/>Escalation: If the issue is not resolved, escalat..."}}
replace-the-failing-hover-motor["<small><b>Step 13</b></small><br/>Action: Replace the failing hover motor on th..."]
escalate-mixed-motor-overtemperature{{"<small><b>Step 14</b></small><br/>Escalation: Escalate the repeated mixed-motor ove..."}}
apply-template-motor-temps-preflight-to --> are-any-motors-above-65c
are-any-motors-above-65c -->|Yes| power-off-the-aircraft
are-any-motors-above-65c -->|No| are-any-temperatures-missing
are-any-temperatures-missing -->|Yes| use-actuator-faults-due-to-missing-feedback
are-any-temperatures-missing -->|No| escalate-to-p2-zip-exec
power-off-the-aircraft --> wait-5-minutes-for-the-motors-to-cool
wait-5-minutes-for-the-motors-to-cool --> resend-a-health-checks-mission-is-the
resend-a-health-checks-mission-is-the -->|Yes, the Aircraft passes pr...| release-zip-back-into-service
resend-a-health-checks-mission-is-the -->|No, it fails with ZIP_EXEC...| load-mission-and-check-motor-thermistors
load-mission-and-check-motor-thermistors --> are-there-signs-of-thermistor-damage
are-there-signs-of-thermistor-damage -->|Yes — hover motor shows the...| replace-the-failing-hover-motor
are-there-signs-of-thermistor-damage -->|No — hover motor does not s...| if-the-issue-is-not-resolved-escalate
are-there-signs-of-thermistor-damage -->|The repeated alarm is for t...| escalate-mixed-motor-overtemperature
style apply-template-motor-temps-preflight-to fill:#dcfce7,stroke:#22c55e,color:#14532d
style are-any-motors-above-65c fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style are-any-temperatures-missing fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style use-actuator-faults-due-to-missing-feedback fill:#f3e8ff,stroke:#a855f7,color:#581c87
style power-off-the-aircraft fill:#dcfce7,stroke:#22c55e,color:#14532d
style wait-5-minutes-for-the-motors-to-cool fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-zip-exec fill:#fef3c7,stroke:#f59e0b,color:#78350f
style resend-a-health-checks-mission-is-the fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style release-zip-back-into-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style are-there-signs-of-thermistor-damage fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style if-the-issue-is-not-resolved-escalate fill:#fef3c7,stroke:#f59e0b,color:#78350f
style replace-the-failing-hover-motor fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-mixed-motor-overtemperature fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 action
Apply template Motor Temps Preflight to your log.
2 question
Are any motors above 65C?
3 question
Are any temperatures missing?
4 reference
Use the missing-feedback guide for the affected actuator family:
- Hover Motor Missing Feedback
- Mixed Motor Missing Feedback
- Roll/Tilt Missing Feedback
- Tail Missing Feedback
- Wing Missing Feedback
- Hover Motor Missing Feedback
- Mixed Motor Missing Feedback
- Roll/Tilt Missing Feedback
- Tail Missing Feedback
- Wing Missing Feedback
5 action
Power OFF the Aircraft.
6 action
Wait 5 minutes for the motors to cool down.
7 escalation
Escalate to P2 Exec On Call.
8 question
Resend a Health Checks Mission. Is the issue resolved?
9 action
Release zip back into service
10 telemetry
Load the failed mission and inspect the
motor_thermistor_check Baraza plot. Use the alarm name and plot to identify whether the repeated failure is for a hover motor or the mixed motor. For a hover motor, check whether the temperature delta between hover motors exceeds 10°C, which can indicate thermistor damage. Do not apply the hover-motor delta check to a mixed-motor alarm. Use the example in the next step as a reference if needed. Enter the mission identifier above to load the plot.
11 question
Are there signs of thermistor damage on a hover motor, or is the repeated alarm for the mixed motor?
Thermistor Damage Example
12 escalation
If the issue is not resolved, escalate to P2 Firmware Motors On Call with the information above.
13 action
Replace the failing hover motor on the Aircraft. Be sure to note the location of the hover motor to replace. Assign one of the following work orders:
- EV2: Work Order Template 95: EV2: Replace Hover Motor on Aircraft
- EV3: Work Order Template 651: EV3: Replace Hover Motor on Aircraft
- EV2: Work Order Template 95: EV2: Replace Hover Motor on Aircraft
- EV3: Work Order Template 651: EV3: Replace Hover Motor on Aircraft
14 escalation
Escalate the repeated mixed-motor overtemperature to P2 Firmware Motors On Call. Include the mission ID and the
motor_thermistor_check plot, and identify the mixed motor as the affected motor family.Resolution 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.