RX_V2V_ABSENT
Viewing this guide for
Applicable alarms (1)
RX_V2V_ABSENT
Likely outcomes — click to expand
Based on 13,411 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 154 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| CCW HOVER MOTOR ASSY, ZIP, P2 | 19607 | 52 |
| TAIL STBD DEPOP, ZIP, P2 | 21840 | 40 |
| TAIL PORT DEPOP, ZIP, P2 | 31280 | 38 |
| CW HOVER MOTOR ASSY, ZIP, P2 | 33333 | 36 |
| AFT MOTOR ASSY, ZIP, P2 | 23548 | 35 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”RX_V2V_ABSENT is the most severe V2V alarm.
Triage RX_V2V_ABSENT first if it is present before triaging any other V2V alarm.
RX_V2V_ABSENT means this Aircraft’s ability to deconflict with neighbor Zips is likely degraded: at least one of the computes is not hearing any deconfliction messages over WiFi, also called V2V or Vehicle-to-Vehicle, even from itself.
When zip_v2v_agent submits a packet to Intel’s wireless firmware, we also see that packet echoed back as a reception.
We will see RX_V2V_ABSENT if the application is missing these self echoes, indicating critically poor wireless health.
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..."}
troubleshoot-actual-preflight-failure["<small><b>Step 4</b></small><br/>Action: Troubleshoot the alarm that actually ..."]
load-v2v-wireless-rx-debug["<small><b>Step 5</b></small><br/>Telemetry: Load the Triage: RX_V2V_ABSENT log p..."]
are-socket-reads-and-default-queue-zero{"<small><b>Step 6</b></small><br/>Question: On each affected compute, are both ..."}
are-logs-offloaded-and-template-available{"<small><b>Step 7</b></small><br/>Question: Are the failed mission logs offloaded..."}
offload-logs-and-rerun-guide["<small><b>Step 8</b></small><br/>Action: Ensure the Aircraft logs are offloade..."]
confirm-build-before-radio-socket-escalation{"<small><b>Step 9</b></small><br/>Question: Is this zip a nonstandard, new, or ex..."}
confirm-build-before-plot-escalation{"<small><b>Step 10</b></small><br/>Question: Is this zip a nonstandard, new, or ex..."}
escalate-to-test-card-engineers{{"<small><b>Step 11</b></small><br/>Escalation: Escalate to the responsible engineers..."}}
escalate-radio-socket-path{{"<small><b>Step 12</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
escalate-with-plot-and-mission{{"<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...| 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 --> are-socket-reads-and-default-queue-zero
are-socket-reads-and-default-queue-zero -->|Yes| confirm-build-before-radio-socket-escalation
are-socket-reads-and-default-queue-zero -->|No| are-logs-offloaded-and-template-available
are-socket-reads-and-default-queue-zero -->|The plot is missing or inco...| are-logs-offloaded-and-template-available
are-logs-offloaded-and-template-available -->|Yes| confirm-build-before-plot-escalation
are-logs-offloaded-and-template-available -->|No| offload-logs-and-rerun-guide
confirm-build-before-radio-socket-escalation -->|commercial release / daily| escalate-radio-socket-path
confirm-build-before-radio-socket-escalation -->|experimental| escalate-to-test-card-engineers
confirm-build-before-radio-socket-escalation -->|not sure| escalate-radio-socket-path
confirm-build-before-plot-escalation -->|commercial release / daily| escalate-with-plot-and-mission
confirm-build-before-plot-escalation -->|experimental| escalate-to-test-card-engineers
confirm-build-before-plot-escalation -->|not sure| escalate-with-plot-and-mission
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 troubleshoot-actual-preflight-failure fill:#dcfce7,stroke:#22c55e,color:#14532d
style are-socket-reads-and-default-queue-zero fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style are-logs-offloaded-and-template-available fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style offload-logs-and-rerun-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style confirm-build-before-radio-socket-escalation fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style confirm-build-before-plot-escalation fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-test-card-engineers fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-radio-socket-path fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-with-plot-and-mission 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
Troubleshoot the alarm that actually caused the preflight failure before returning the Aircraft to service.
5 telemetry
Load the
Triage: RX_V2V_ABSENT log plots template for the failed mission. Example: Triage: RX_V2V_ABSENT log plots. Use the alarm plots to identify the affected compute or computes. Then inspect (delta) wireless_rx.socket_reads and metrics.iwlwifi:default_queue.total_count on each affected compute. Enter the mission identifier above to load the plot.
6 question
On each affected compute, are both
It is possible for both computes to be affected, but either metric staying at zero for multiple publish cycles is unexpected.
Example where both metrics are zero:
Nominal example:
(delta) wireless_rx.socket_reads and metrics.iwlwifi:default_queue.total_count zero for multiple publish cycles in a row?It is possible for both computes to be affected, but either metric staying at zero for multiple publish cycles is unexpected.
Example where both metrics are zero:
Nominal example:
7 question
Are the failed mission logs offloaded, and does the
Triage: RX_V2V_ABSENT log plots template show the relevant plots for the affected compute or computes? 8 action
Ensure the Aircraft logs are offloaded for the failed mission, then rerun this troubleshooting guide with the
Triage: RX_V2V_ABSENT log plots template. Do not escalate until the template output is available. 9 question
Is this zip a nonstandard, new, or experimental build of hardware or flight software?
10 question
Is this zip a nonstandard, new, or experimental build of hardware or flight software?
11 escalation
Escalate to the responsible engineers for this test card. Include the mission ID and a Baraza share link for the
Triage: RX_V2V_ABSENT log plots plot from the relevant mission failure. 12 escalation
Escalate to P2 Embedded Linux On Call using a Baraza share link for the
Triage: RX_V2V_ABSENT log plots plot from the relevant mission failure. Include the mission ID, and call out that (delta) wireless_rx.socket_reads and metrics.iwlwifi:default_queue.total_count were both zero on each affected compute for multiple publish cycles after the power cycle. Please do not escalate without that Baraza share link. 13 escalation
Escalate to P2 Embedded Linux On Call using a Baraza share link for the
Triage: RX_V2V_ABSENT log plots plot from the relevant mission failure. Include the mission ID. Please do not escalate without that Baraza share link. 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.