0x0010033F ZIP_EXECUTIVE_V4_SECONDARY_CONTROLLER_NOT_IDLE
Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x0010033f) 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 is an intermediate error code indicating that compute B is stuck in a bad state from a prior mission or latent error. In most cases this should be resolved with a reboot mission.
Additional reference: Compute Failover Reference Document.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-there-a-root-cause-error{"<small><b>Step 1</b></small><br/>Question: Is there a terminal or root-cause err..."}
follow-root-cause-guide["<small><b>Step 2</b></small><br/>Action: Follow the troubleshooting guide for ..."]
attempt-reboot-mission-and-retry["<small><b>Step 3</b></small><br/>Action: Attempt a reboot mission, then retry ..."]
did-the-retry-fix-the-issue{"<small><b>Step 4</b></small><br/>Question: Did the reboot mission and retry fix ..."}
return-to-service["<small><b>Step 5</b></small><br/>Action: The Aircraft may return to service."]
check-compute-b-imu-health["<small><b>Step 6</b></small><br/>Telemetry: Enter the failed mission ID to load t..."]
is-compute-b-imu-healthy{"<small><b>Step 7</b></small><br/>Question: Is the IMU_TIMESTAMP_ERROR_HIGH ala..."}
escalate-to-zip-exec{{"<small><b>Step 8</b></small><br/>Escalation: Escalate to Zip Executive On Call."}}
escalate-to-embedded-linux{{"<small><b>Step 9</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call."}}
is-there-a-root-cause-error -->|Yes| follow-root-cause-guide
is-there-a-root-cause-error -->|No| attempt-reboot-mission-and-retry
attempt-reboot-mission-and-retry --> did-the-retry-fix-the-issue
did-the-retry-fix-the-issue -->|Yes| return-to-service
did-the-retry-fix-the-issue -->|No| check-compute-b-imu-health
check-compute-b-imu-health --> is-compute-b-imu-healthy
is-compute-b-imu-healthy -->|Yes, present and false| escalate-to-zip-exec
is-compute-b-imu-healthy -->|No, absent or true| escalate-to-embedded-linux
style is-there-a-root-cause-error fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-root-cause-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style attempt-reboot-mission-and-retry fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-the-retry-fix-the-issue fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-compute-b-imu-healthy fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-zip-exec fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-to-embedded-linux fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
IMU_TIMESTAMP_ERROR_HIGH alarm.IMU_TIMESTAMP_ERROR_HIGH alarm present and set to false?If so, the IMU is healthy:
If the alarm is absent or set to
true, the IMU is unhealthy:
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.