DROID_FW_NODE_UNHEALTHY
Applicable alarms (1)
Likely outcomes — click to expand
Based on 337 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 101 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| CCW HOVER MOTOR ASSY, EV3 ZIP, P2 | 19607 | 5 |
| CW HOVER MOTOR ASSY, EV3 ZIP, P2 | 33333 | 5 |
| BRAIN, LRU, DROID, P2 | 31920 | 4 |
| ASSY, SPOOL AND LINE, DOCKING FIN | 48477 | 3 |
| CCW HOVER PROPELLER BLADE, ZIP, P2 | 29857 | 3 |
Frequently co-occurring alarms (% of the 337 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm occurs when there are issues with Droid power. That is, the firmware nodes are not publishing any data. This indicates a power issue and in this state, any missions involving the Droid (delivery, lower, raise, and so on) are likely to fail; therefore, the recommended maintenance action should be taken.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-the-droid-power-cycle-droi["<small><b>Step 1</b></small><br/>Action: Power cycle the Droid Power Cycle Dr..."]
wait-for-a-minimum-of-60-seconds["<small><b>Step 2</b></small><br/>Action: Wait for a minimum of 60 seconds."]
is-the-alarm-still-set{"<small><b>Step 3</b></small><br/>Question: Is the alarm still set?"}
escalate-to-embedded-linux-on-call{{"<small><b>Step 4</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call."}}
the-aircraft-may-return-to-service("<small><b>Step 5</b></small><br/>Reference: The Aircraft may return to service.")
power-cycle-the-droid-power-cycle-droi --> wait-for-a-minimum-of-60-seconds
wait-for-a-minimum-of-60-seconds --> is-the-alarm-still-set
is-the-alarm-still-set -->|Yes| escalate-to-embedded-linux-on-call
is-the-alarm-still-set -->|No| the-aircraft-may-return-to-service
style power-cycle-the-droid-power-cycle-droi fill:#dcfce7,stroke:#22c55e,color:#14532d
style wait-for-a-minimum-of-60-seconds fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-alarm-still-set fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-embedded-linux-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87 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.