Droid Executive Responses Wired Unavailable
Viewing this guide for
Applicable alarms (2)
DROID_EXECUTIVE_RESPONSES_WIRED_UNAVAILABLETimed Droid Paraland ARM_FOR_FLIGHT Command timed out after 10 seconds: Timed out
Likely outcomes — click to expand
Based on 567,235 missions where this alarm fired in the last
90 days
(for DROID_EXECUTIVE_RESPONSES_WIRED_UNAVAILABLE) as of 2026-10-13
Grounding vs discrepancy (of 5,282 ZERP issues filed on these missions)
Top work orders
- EV2: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 633
- Inspect Droid after Droid Left Behind (DLB) · MAINTENANCE_ACTION 424
- EV3: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 328
- Reset Droid after DLB · REPAIR 294
- V4 Zipping Point: Inspect Zipping Point after Droid Left Behind (DLB) - Ranger · MAINTENANCE_ACTION 159
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| SERVO, ASSY, UNIVERSAL, P2 | 20398 | 1,229 |
| ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 | 48477 | 1,193 |
| CCW HOVER MOTOR ASSY, ZIP, P2 | 19607 | 999 |
| TRIAX WING ASM, PORT(LH), DEPOP, ZIP, P2 | 24762 | 648 |
| WING ASM FULL, TRIAX, AL, STRBRD(RH), ZIP, P2 | 25266 | 648 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”The DROID_EXECUTIVE_RESPONSES_WIRED_UNAVAILABLE alarm occurs when Zip Executive has lost Droid executive responses over the wired response path.
This guide also applies when the error chain includes Timed Droid Paraland ARM_FOR_FLIGHT Command timed out after 10 seconds: Timed out. That timeout means Zip Executive did not receive the expected response from the Droid executive while arming the Droid paraland system, so use the same wired response troubleshooting flow.
There are several possible reasons why this could happen:
- Droid comms issues with the Ethernet connection
- A Droid power issue (the Droid is off because it is not receiving power)
- Droid software issues:
- Droid stack is down
- Droid executive has crashed
- Entire Droid software stack is unhealthy, perhaps because of Droid kernel panic
Covered alarm and timeout signature
Section titled “Covered alarm and timeout signature”- DROID_EXECUTIVE_RESPONSES_WIRED_UNAVAILABLE
- Timed Droid Paraland ARM_FOR_FLIGHT Command timed out after 10 seconds: Timed out
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-a-droid-installed-before-power-cycle{"<small><b>Step 1</b></small><br/>Question: Is a Droid installed?"}
power-cycle-droid-first["<small><b>Step 2</b></small><br/>Action: Power cycle the Droid Power Cycle D..."]
is-the-issue-resolved-after-initial-power-cycle{"<small><b>Step 3</b></small><br/>Question: Is the issue resolved?"}
return-the-droid-to-service-after-initial-power-cycle["<small><b>Step 4</b></small><br/>Action: Return the Droid to service."]
ev2-zip-droid-apply-this-template-droid["<small><b>Step 5</b></small><br/>Action: EV2 Zip-Droid: Apply this template: ..."]
is-droid-detected-via-load-switch-true{"<small><b>Step 6</b></small><br/>Question: Is droid_detected_via_load_switch T..."}
a-droid-is-installed["<small><b>Step 7</b></small><br/>Action: A Droid is installed. Continue to the..."]
there-is-no-droid-installed-which-is-the["<small><b>Step 8</b></small><br/>Action: There is no Droid installed which is ..."]
is-link-status-solidly-link-up-and-stable{"<small><b>Step 9</b></small><br/>Question: Is link_status solidly LINK_UP wh..."}
the-droid-is-on-and-connected["<small><b>Step 10</b></small><br/>Action: The Droid is ON and connected. Contin..."]
is-the-link-status-intermittently-toggl{"<small><b>Step 11</b></small><br/>Question: Is the link_status intermittently t..."}
the-droid-has-intermittent-wired-comms-i["<small><b>Step 12</b></small><br/>Action: The Droid has intermittent wired comm..."]
aircraft-and-droid-may-return-to-service("<small><b>Step 13</b></small><br/>Reference: Aircraft and Droid may return to serv...")
if-the-link-status-is-solidly-down-the["<small><b>Step 14</b></small><br/>Action: If the link_status is solidly DOWN, t..."]
is-the-issue-resolved{"<small><b>Step 15</b></small><br/>Question: Is the issue resolved?"}
the-aircraft-may-return-to-service("<small><b>Step 16</b></small><br/>Reference: The Aircraft may return to service.")
send-the-droid-to-maintenance-for-matin["<small><b>Step 17</b></small><br/>Action: Send the Droid to maintenance for mat..."]
are-there-messages-from-the-droids-main{"<small><b>Step 18</b></small><br/>Question: Are there messages from the Droid mai..."}
the-droid-firmware-nodes-are-powered-on["<small><b>Step 19</b></small><br/>Action: The Droid firmware nodes are powered ..."]
droid-power-is-not-in-a-good-state["<small><b>Step 20</b></small><br/>Action: Droid power is not in a good state. 1..."]
are-there-messages-from-the-droid-brain{"<small><b>Step 21</b></small><br/>Question: Are there messages from the Droid brain?"}
the-droid-connection-status-is-healthy-a["<small><b>Step 22</b></small><br/>Action: Although the Droid appears online and..."]
is-the-issue-resolved-after-power-cycling-healthy-droid{"<small><b>Step 23</b></small><br/>Question: Is the issue resolved?"}
return-the-droid-to-service["<small><b>Step 24</b></small><br/>Action: Return the Droid to service."]
follow-jp6-droid-unprovisioned-after-healthy-droid["<small><b>Step 25</b></small><br/>Action: Follow JP6 Droid Unprovisioned/top..."]
is-the-issue-resolved-after-jp6-droid-unprovisioned-healthy-droid{"<small><b>Step 26</b></small><br/>Question: Is the issue resolved?"}
return-the-droid-to-service-after-jp6-droid-unprovisioned-healthy-droid["<small><b>Step 27</b></small><br/>Action: Return the Droid to service."]
escalate-unresolved-droid-executive-response{{"<small><b>Step 28</b></small><br/>Escalation: Escalate to P2 Embedded Platform On C..."}}
the-droid-brain-is-unhealthy["<small><b>Step 29</b></small><br/>Action: The Droid brain is unhealthy. Power c..."]
is-the-issue-resolved-after-power-cycling-unhealthy-droid-brain{"<small><b>Step 30</b></small><br/>Question: Is the issue resolved?"}
return-the-droid-to-service-after-unhealthy-droid-brain["<small><b>Step 31</b></small><br/>Action: Return the Droid to service."]
follow-jp6-droid-unprovisioned-after-unhealthy-droid-brain["<small><b>Step 32</b></small><br/>Action: Follow JP6 Droid Unprovisioned/top..."]
is-the-issue-resolved-after-jp6-droid-unprovisioned-unhealthy-droid-brain{"<small><b>Step 33</b></small><br/>Question: Is the issue resolved?"}
return-the-droid-to-service-after-jp6-droid-unprovisioned-unhealthy-droid-brain["<small><b>Step 34</b></small><br/>Action: Return the Droid to service."]
escalate-unresolved-unhealthy-droid-brain{{"<small><b>Step 35</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call."}}
is-a-droid-installed-before-power-cycle -->|Yes| power-cycle-droid-first
is-a-droid-installed-before-power-cycle -->|No| there-is-no-droid-installed-which-is-the
power-cycle-droid-first --> is-the-issue-resolved-after-initial-power-cycle
is-the-issue-resolved-after-initial-power-cycle -->|Yes| return-the-droid-to-service-after-initial-power-cycle
is-the-issue-resolved-after-initial-power-cycle -->|No| ev2-zip-droid-apply-this-template-droid
ev2-zip-droid-apply-this-template-droid --> is-droid-detected-via-load-switch-true
is-droid-detected-via-load-switch-true -->|Yes| a-droid-is-installed
is-droid-detected-via-load-switch-true -->|No| there-is-no-droid-installed-which-is-the
a-droid-is-installed --> is-link-status-solidly-link-up-and-stable
is-link-status-solidly-link-up-and-stable -->|Yes| the-droid-is-on-and-connected
is-link-status-solidly-link-up-and-stable -->|No| is-the-link-status-intermittently-toggl
the-droid-is-on-and-connected --> are-there-messages-from-the-droids-main
is-the-link-status-intermittently-toggl -->|Yes| the-droid-has-intermittent-wired-comms-i
is-the-link-status-intermittently-toggl -->|No| if-the-link-status-is-solidly-down-the
the-droid-has-intermittent-wired-comms-i --> send-the-droid-to-maintenance-for-matin
if-the-link-status-is-solidly-down-the --> is-the-issue-resolved
is-the-issue-resolved -->|Yes| the-aircraft-may-return-to-service
is-the-issue-resolved -->|No| send-the-droid-to-maintenance-for-matin
are-there-messages-from-the-droids-main -->|Yes| the-droid-firmware-nodes-are-powered-on
are-there-messages-from-the-droids-main -->|No| droid-power-is-not-in-a-good-state
the-droid-firmware-nodes-are-powered-on --> are-there-messages-from-the-droid-brain
are-there-messages-from-the-droid-brain -->|Yes| the-droid-connection-status-is-healthy-a
are-there-messages-from-the-droid-brain -->|No| the-droid-brain-is-unhealthy
the-droid-connection-status-is-healthy-a --> is-the-issue-resolved-after-power-cycling-healthy-droid
is-the-issue-resolved-after-power-cycling-healthy-droid -->|Yes| return-the-droid-to-service
is-the-issue-resolved-after-power-cycling-healthy-droid -->|No| follow-jp6-droid-unprovisioned-after-healthy-droid
follow-jp6-droid-unprovisioned-after-healthy-droid --> is-the-issue-resolved-after-jp6-droid-unprovisioned-healthy-droid
is-the-issue-resolved-after-jp6-droid-unprovisioned-healthy-droid -->|Yes| return-the-droid-to-service-after-jp6-droid-unprovisioned-healthy-droid
is-the-issue-resolved-after-jp6-droid-unprovisioned-healthy-droid -->|No| escalate-unresolved-droid-executive-response
the-droid-brain-is-unhealthy --> is-the-issue-resolved-after-power-cycling-unhealthy-droid-brain
is-the-issue-resolved-after-power-cycling-unhealthy-droid-brain -->|Yes| return-the-droid-to-service-after-unhealthy-droid-brain
is-the-issue-resolved-after-power-cycling-unhealthy-droid-brain -->|No| follow-jp6-droid-unprovisioned-after-unhealthy-droid-brain
follow-jp6-droid-unprovisioned-after-unhealthy-droid-brain --> is-the-issue-resolved-after-jp6-droid-unprovisioned-unhealthy-droid-brain
is-the-issue-resolved-after-jp6-droid-unprovisioned-unhealthy-droid-brain -->|Yes| return-the-droid-to-service-after-jp6-droid-unprovisioned-unhealthy-droid-brain
is-the-issue-resolved-after-jp6-droid-unprovisioned-unhealthy-droid-brain -->|No| escalate-unresolved-unhealthy-droid-brain
style is-a-droid-installed-before-power-cycle fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-droid-first fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved-after-initial-power-cycle fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-the-droid-to-service-after-initial-power-cycle fill:#dcfce7,stroke:#22c55e,color:#14532d
style ev2-zip-droid-apply-this-template-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-droid-detected-via-load-switch-true fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style a-droid-is-installed fill:#dcfce7,stroke:#22c55e,color:#14532d
style there-is-no-droid-installed-which-is-the fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-link-status-solidly-link-up-and-stable fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-droid-is-on-and-connected fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-link-status-intermittently-toggl fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-droid-has-intermittent-wired-comms-i fill:#dcfce7,stroke:#22c55e,color:#14532d
style aircraft-and-droid-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style if-the-link-status-is-solidly-down-the fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style send-the-droid-to-maintenance-for-matin fill:#dcfce7,stroke:#22c55e,color:#14532d
style are-there-messages-from-the-droids-main fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-droid-firmware-nodes-are-powered-on fill:#dcfce7,stroke:#22c55e,color:#14532d
style droid-power-is-not-in-a-good-state fill:#dcfce7,stroke:#22c55e,color:#14532d
style are-there-messages-from-the-droid-brain fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-droid-connection-status-is-healthy-a fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved-after-power-cycling-healthy-droid fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-the-droid-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style follow-jp6-droid-unprovisioned-after-healthy-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved-after-jp6-droid-unprovisioned-healthy-droid fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-the-droid-to-service-after-jp6-droid-unprovisioned-healthy-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-unresolved-droid-executive-response fill:#fef3c7,stroke:#f59e0b,color:#78350f
style the-droid-brain-is-unhealthy fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved-after-power-cycling-unhealthy-droid-brain fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-the-droid-to-service-after-unhealthy-droid-brain fill:#dcfce7,stroke:#22c55e,color:#14532d
style follow-jp6-droid-unprovisioned-after-unhealthy-droid-brain fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved-after-jp6-droid-unprovisioned-unhealthy-droid-brain fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-the-droid-to-service-after-jp6-droid-unprovisioned-unhealthy-droid-brain fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-unresolved-unhealthy-droid-brain fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
Is a Droid installed?
2 action
Power cycle the Droid (Power Cycle Droid).
3 question
Is the issue resolved?
4 action
Return the Droid to service.
5 action
EV2 Zip-Droid: Apply this template: droid-connection-health-checking
EV3 Zip-Droid: Apply this: EV3-Zip-Droid-Ethernet-Link along with the EV2 template (above).
Add padding to the mission if necessary, it may be 0 seconds long in some cases.
Example View
EV3 Zip-Droid: Apply this: EV3-Zip-Droid-Ethernet-Link along with the EV2 template (above).
Add padding to the mission if necessary, it may be 0 seconds long in some cases.
Example View
6 question
Is
droid_detected_via_load_switch TRUE? [Allowing a minor blip in RunPreMotorChecks] 7 action
A Droid is installed.
Continue to the next step.
Continue to the next step.
8 action
There is no Droid installed which is the reason that the watchdog is failing.
1. Install a Droid.
2. Return the Aircraft to service.
1. Install a Droid.
2. Return the Aircraft to service.
9 question
Is
Sometimes link status can be masked due to low rate of publishing.
Make sure to check that the link toggle counts are also constant except for when the Droid is being lowered.
link_status solidly LINK_UP while link_toggle_count / link_state_toggle_count remains constant?Sometimes link status can be masked due to low rate of publishing.
Make sure to check that the link toggle counts are also constant except for when the Droid is being lowered.
10 action
The Droid is ON and connected.
Continue to the next step.
Continue to the next step.
11 question
Is the
OR is the
link_status intermittently toggling between UP and DOWN?OR is the
link_state_toggle_count / link_toggle_count steadily increasing? 12 action
The Droid has intermittent wired comms issues.
13 reference
Aircraft and Droid may return to service.
14 action
If the link_status is solidly DOWN, the Droid is either completely OFF or has been completely disconnected over Ethernet from the Aircraft.
1. Power cycle the Droid (Power Cycle Droid).
1. Power cycle the Droid (Power Cycle Droid).
15 question
Is the issue resolved?
16 reference
The Aircraft may return to service.
17 action
Send the Droid to maintenance for mating connector issues. See Droid to Aircraft Electrical Contacts Debugging.
18 question
Are there messages from the Droid main thruster node?
19 action
The Droid firmware nodes are powered on and working.
Continue to the next step.
Continue to the next step.
20 action
Droid power is not in a good state.
1. Power cycle the Droid (Power Cycle Droid).
2. Return the Droid to service.
3. If the issue is not resolved, escalate to P2 Firmware Power On Call.
1. Power cycle the Droid (Power Cycle Droid).
2. Return the Droid to service.
3. If the issue is not resolved, escalate to P2 Firmware Power On Call.
21 question
Are there messages from the Droid brain?
22 action
Although the Droid appears online and its connection status is healthy, an underlying connection issue may still be preventing communication.
Power cycle the Droid (Power Cycle Droid).
Power cycle the Droid (Power Cycle Droid).
23 question
Is the issue resolved?
24 action
Return the Droid to service.
25 action
Follow JP6 Droid Unprovisioned.
26 question
Is the issue resolved?
27 action
Return the Droid to service.
28 escalation
Escalate to P2 Embedded Platform On Call.
29 action
The Droid brain is unhealthy.
Power cycle the Droid (Power Cycle Droid).
Power cycle the Droid (Power Cycle Droid).
30 question
Is the issue resolved?
31 action
Return the Droid to service.
32 action
Follow JP6 Droid Unprovisioned.
33 question
Is the issue resolved?
34 action
Return the Droid to service.
35 escalation
Escalate to P2 Embedded Linux On Call.
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.