REQUIRED_NODES_DUPLICATED
Applicable alarms (1)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last 90 days 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 alarm means the distro hover configuration checker associated more than one hover identity with a single expected hover corner.
This is commonly accompanied by one or more *_DUPLICATED alarms that identify the affected corner.
This usually indicates that the hover installation, wiring, or role / provisioning information does not match the expected one-hover-per-corner configuration.
See DISTRO HOVER CONFIGURATION CHECKER for a description of how the diagnostic works.
Troubleshooting Steps
Section titled “Troubleshooting Steps”Related pages
Section titled “Related pages”graph TD
is-draft-required-nodes-duplicated-act{"<small><b>Step 1</b></small><br/>Question: Is REQUIRED_NODES_DUPLICATED active..."}
power-cycle-the-vehicle-and-send-a-pre{"<small><b>Step 2</b></small><br/>Question: Power cycle the vehicle and send a pr..."}
the-aircraft-may-return-to-service["<small><b>Step 3</b></small><br/>Action: The aircraft may return to service."]
identify-the-affected-hover-corner-fr["<small><b>Step 4</b></small><br/>Action: Identify the affected hover corner fr..."]
verify-that-only-one-hover-motor-unit["<small><b>Step 5</b></small><br/>Action: Verify that only one hover motor unit..."]
verify-the-hover-motor-units-are-inst["<small><b>Step 6</b></small><br/>Action: Verify the hover motor units are inst..."]
run-an-ota-to-update-firmware-and-hov["<small><b>Step 7</b></small><br/>Action: Run an OTA to update firmware and hov..."]
send-a-preflight-mission-again-did-pr{"<small><b>Step 8</b></small><br/>Question: Send a preflight mission again. Did p..."}
the-aircraft-may-return-to-service-2["<small><b>Step 9</b></small><br/>Action: The aircraft may return to service."]
escalate-to-p2-firmware-motors-on-cal{{"<small><b>Step 10</b></small><br/>Escalation: Escalate to P2 Firmware Motors On Call."}}
continue-troubleshooting-using-the-ala["<small><b>Step 11</b></small><br/>Action: Continue troubleshooting using the al..."]
is-draft-required-nodes-duplicated-act -->|Yes| power-cycle-the-vehicle-and-send-a-pre
is-draft-required-nodes-duplicated-act -->|No| continue-troubleshooting-using-the-ala
power-cycle-the-vehicle-and-send-a-pre -->|Yes| the-aircraft-may-return-to-service
power-cycle-the-vehicle-and-send-a-pre -->|No| identify-the-affected-hover-corner-fr
identify-the-affected-hover-corner-fr --> verify-that-only-one-hover-motor-unit
verify-that-only-one-hover-motor-unit --> verify-the-hover-motor-units-are-inst
verify-the-hover-motor-units-are-inst --> run-an-ota-to-update-firmware-and-hov
run-an-ota-to-update-firmware-and-hov --> send-a-preflight-mission-again-did-pr
send-a-preflight-mission-again-did-pr -->|Yes| the-aircraft-may-return-to-service-2
send-a-preflight-mission-again-did-pr -->|No| escalate-to-p2-firmware-motors-on-cal
style is-draft-required-nodes-duplicated-act fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-the-vehicle-and-send-a-pre fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style identify-the-affected-hover-corner-fr fill:#dcfce7,stroke:#22c55e,color:#14532d
style verify-that-only-one-hover-motor-unit fill:#dcfce7,stroke:#22c55e,color:#14532d
style verify-the-hover-motor-units-are-inst fill:#dcfce7,stroke:#22c55e,color:#14532d
style run-an-ota-to-update-firmware-and-hov fill:#dcfce7,stroke:#22c55e,color:#14532d
style send-a-preflight-mission-again-did-pr fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service-2 fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-firmware-motors-on-cal fill:#fef3c7,stroke:#f59e0b,color:#78350f
style continue-troubleshooting-using-the-ala fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
REQUIRED_NODES_DUPLICATED active on /distro_a.power_status?*_DUPLICATED alarm.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.