0x00100192 ZIP_EXECUTIVE_V4_DROID_COMMAND_TIMEOUT
Applicable alarms (6)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x00100192) as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Applicable to all hardware versions
Background
Section titled “Background”This Zip Executive alarm indicates that a Droid command timed out.
Lower, raise, paraland, and idle Droid commands that fail may report this alarm instead of a dedicated command-failed alarm.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-aircraft-and-droid["<small><b>Step 1</b></small><br/>Action: Power cycle the Aircraft Power Cycl..."]
did-the-issue-reoccur{"<small><b>Step 2</b></small><br/>Question: Did the issue re-occur?"}
return-to-service["<small><b>Step 3</b></small><br/>Action: Return the Aircraft and Droid to serv..."]
is-there-a-caused-by-error{"<small><b>Step 4</b></small><br/>Question: Is there a caused-by error?"}
follow-caused-by-guide("<small><b>Step 5</b></small><br/>Reference: Follow the guide for the caused-by er...")
escalate-to-p2-droid-on-call{{"<small><b>Step 6</b></small><br/>Escalation: Escalate to P2 Droid On Call."}}
power-cycle-aircraft-and-droid --> did-the-issue-reoccur
did-the-issue-reoccur -->|Yes| is-there-a-caused-by-error
did-the-issue-reoccur -->|No| return-to-service
is-there-a-caused-by-error -->|Yes| follow-caused-by-guide
is-there-a-caused-by-error -->|No| escalate-to-p2-droid-on-call
style power-cycle-aircraft-and-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-the-issue-reoccur fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-there-a-caused-by-error fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-caused-by-guide fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-p2-droid-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
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.