0x0003011D ZIP_EXECUTIVE_CODE_DOCK_MOTION_NOT_COMPLETED
Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x0003011D) 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 error occurs when the Aircraft has commanded the Droid to idle, but it has not received a response confirming the command has been received.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-0x0003011e-zip-executive-code-dock-la{"<small><b>Step 1</b></small><br/>Question: Is 0x0003011E ZIP_EXECUTIVE_CODE_DOC..."}
follow-0x0003011e-zip-executive-code-do["<small><b>Step 2</b></small><br/>Action: Follow the corresponding guide for th..."]
check-if-shut-off-props-exist-in-the-gn["<small><b>Step 3</b></small><br/>Action: Check if “SHUT_OFF_PROPS” exist in th..."]
does-shut-off-props-exist-in-the-data-t{"<small><b>Step 4</b></small><br/>Question: Does “SHUT_OFF_PROPS” exist in the da..."}
escalate-to-aircraft-executive-on-call{{"<small><b>Step 5</b></small><br/>Escalation: Escalate to P2 Exec On Call."}}
escalate-to-p2-zip-controls-on-call{{"<small><b>Step 6</b></small><br/>Escalation: Escalate to P2 Zip Controls On Call"}}
is-0x0003011e-zip-executive-code-dock-la -->|Yes| follow-0x0003011e-zip-executive-code-do
is-0x0003011e-zip-executive-code-dock-la -->|No| check-if-shut-off-props-exist-in-the-gn
check-if-shut-off-props-exist-in-the-gn --> does-shut-off-props-exist-in-the-data-t
does-shut-off-props-exist-in-the-data-t -->|Yes| escalate-to-aircraft-executive-on-call
does-shut-off-props-exist-in-the-data-t -->|No| escalate-to-p2-zip-controls-on-call
style is-0x0003011e-zip-executive-code-dock-la fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-0x0003011e-zip-executive-code-do fill:#dcfce7,stroke:#22c55e,color:#14532d
style check-if-shut-off-props-exist-in-the-gn fill:#dcfce7,stroke:#22c55e,color:#14532d
style does-shut-off-props-exist-in-the-data-t fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-aircraft-executive-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-to-p2-zip-controls-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
0x0003011E ZIP_EXECUTIVE_CODE_DOCK_LATCH_NOT_RETRACTED also present?gnc.commander.status.control_mode message. Follow the video below.Video demonstrating how to check the
gnc.commander.status.control_mode message has the SHUT_OFF_PROPS status.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.