RX_NONWARNING_SELF_V2V_ABSENT
Viewing this guide for
Applicable alarms (1)
RX_NONWARNING_SELF_V2V_ABSENT
Likely outcomes — click to expand
Based on 859,368 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 5,704 ZERP issues filed on these missions)
Top work orders
- EV3: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 210
- Troubleshoot Hover Motor Resistance on Aircraft · INSPECTION 77
- EV2: Troubleshoot Electrical Contacts on Aircraft and Droid · INSPECTION 71
- Reset Droid Lid · TROUBLESHOOTING 57
- EV2: ZCO-2026-08-03 Lower Foam Wear Pad Retrofit (FRCO-286 / SB-2026-023) · UPGRADE_RETROFIT 35
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| SERVO, ASSY, UNIVERSAL, P2 | 20398 | 983 |
| CW/CCW HOVER MOTOR ASSY, ZIP, P2 | 19607 | 822 |
| ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 | 48477 | 762 |
| PRE-PREG TAIL ASSY STBD(RH), ZIP, P2 | 21840 | 644 |
| TAIL PORT, ZIP, P2 | 31280 | 613 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”RX_NONWARNING_SELF_V2V_ABSENT means the V2V agent is not receiving publishable nonwarning self V2V from the local aircraft.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-the-aircraft["<small><b>Step 1</b></small><br/>Action: Power cycle the Aircraft. For steps, ..."]
run-mission-preflight-again["<small><b>Step 2</b></small><br/>Action: Run mission preflight once more."]
what-happened-after-preflight-retry{"<small><b>Step 3</b></small><br/>Question: After the power cycle and preflight r..."}
use-rx-v2v-absent-guide["<small><b>Step 4</b></small><br/>Action: Use the RX_V2V_ABSENT guide/topics..."]
troubleshoot-actual-preflight-failure["<small><b>Step 5</b></small><br/>Action: Troubleshoot the alarm that actually ..."]
load-v2v-wireless-rx-debug["<small><b>Step 6</b></small><br/>Telemetry: Load the Triage: RX_NONWARNING_SELF_..."]
what-does-the-nonwarning-plot-show{"<small><b>Step 7</b></small><br/>Question: What does the Triage: RX_NONWARNING_..."}
how-are-nav-transforms-absent-presenting{"<small><b>Step 8</b></small><br/>Question: How is the missing nav transform symp..."}
exhaust-all-other-preflight-alarms["<small><b>Step 9</b></small><br/>Action: Explicitly troubleshoot every other p..."]
escalate-metrics-period-embedded-linux{{"<small><b>Step 10</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
escalate-nav-transforms-zip-autonomy{{"<small><b>Step 11</b></small><br/>Escalation: Escalate to P2 Zip Autonomy On Call. ..."}}
escalate-planner-location-context-zip-autonomy{{"<small><b>Step 12</b></small><br/>Escalation: Escalate to P2 Zip Autonomy On Call. ..."}}
escalate-inconclusive-embedded-linux-avionics{{"<small><b>Step 13</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
return-to-service["<small><b>Step 14</b></small><br/>Action: The alarm did not reproduce after the..."]
power-cycle-the-aircraft --> run-mission-preflight-again
run-mission-preflight-again --> what-happened-after-preflight-retry
what-happened-after-preflight-retry -->|Preflight Failure: RX_V2V_A...| use-rx-v2v-absent-guide
what-happened-after-preflight-retry -->|Preflight Failure: RX_NONWA...| load-v2v-wireless-rx-debug
what-happened-after-preflight-retry -->|Preflight Failure: None of ...| troubleshoot-actual-preflight-failure
what-happened-after-preflight-retry -->|No Preflight Failure| return-to-service
load-v2v-wireless-rx-debug --> what-does-the-nonwarning-plot-show
what-does-the-nonwarning-plot-show -->|metrics publish period is i...| escalate-metrics-period-embedded-linux
what-does-the-nonwarning-plot-show -->|nav transforms are absent| how-are-nav-transforms-absent-presenting
what-does-the-nonwarning-plot-show -->|planner location context is...| escalate-planner-location-context-zip-autonomy
what-does-the-nonwarning-plot-show -->|none of these / inconclusive| escalate-inconclusive-embedded-linux-avionics
how-are-nav-transforms-absent-presenting -->|preflight failure| exhaust-all-other-preflight-alarms
how-are-nav-transforms-absent-presenting -->|in flight and repeatedly ca...| escalate-nav-transforms-zip-autonomy
how-are-nav-transforms-absent-presenting -->|not sure| escalate-nav-transforms-zip-autonomy
exhaust-all-other-preflight-alarms --> escalate-nav-transforms-zip-autonomy
style power-cycle-the-aircraft fill:#dcfce7,stroke:#22c55e,color:#14532d
style run-mission-preflight-again fill:#dcfce7,stroke:#22c55e,color:#14532d
style what-happened-after-preflight-retry fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style use-rx-v2v-absent-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style troubleshoot-actual-preflight-failure fill:#dcfce7,stroke:#22c55e,color:#14532d
style what-does-the-nonwarning-plot-show fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style how-are-nav-transforms-absent-presenting fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style exhaust-all-other-preflight-alarms fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-metrics-period-embedded-linux fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-nav-transforms-zip-autonomy fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-planner-location-context-zip-autonomy fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-inconclusive-embedded-linux-avionics fill:#fef3c7,stroke:#f59e0b,color:#78350f
style return-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
1 action
Power cycle the Aircraft. For steps, see Power Cycle Aircraft.
2 action
Run mission preflight once more.
3 question
After the power cycle and preflight retry, what happened? Pick the first option that applies.
4 action
Use the RX_V2V_ABSENT guide instead.
5 action
Troubleshoot the alarm that actually caused the preflight failure before returning the Aircraft to service.
6 telemetry
Load the
Example of the plotting state:
Triage: RX_NONWARNING_SELF_V2V_ABSENT log plot template for the failed mission. Example: Triage: RX_NONWARNING_SELF_V2V_ABSENT.Example of the plotting state:
Enter the mission identifier above to load the plot.
7 question
What does the
Triage: RX_NONWARNING_SELF_V2V_ABSENT plot show? 9 action
Explicitly troubleshoot every other preflight alarm present on the vehicle first. After all other preflight alarms have been exhausted, continue to Zip Autonomy escalation.
10 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and a Baraza share link for the
Triage: RX_NONWARNING_SELF_V2V_ABSENT plot, and call out that the metrics publish period is inconsistent. 12 escalation
Escalate to P2 Zip Autonomy On Call. Include the mission ID and a Baraza share link for the
Triage: RX_NONWARNING_SELF_V2V_ABSENT plot, and call out that planner location context is absent. 13 escalation
Escalate to P2 Embedded Linux On Call and Avionics On Call. Include the mission ID and a Baraza share link for the
Triage: RX_NONWARNING_SELF_V2V_ABSENT plot, and call out that the plotted symptom was none of the listed cases or was inconclusive. 14 action
The alarm did not reproduce after the power cycle and preflight retry. The Aircraft may return to service.
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.