V2V_SELF_CHECK_FAILED_MISSING_TRANSMISSIONS, V2V_SELF_CHECK_FAILED_MISSING_BROADCAST_RECEPTIONS, and V2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS
Viewing this guide for
Applicable alarms (3)
V2V_SELF_CHECK_FAILED_MISSING_TRANSMISSIONSV2V_SELF_CHECK_FAILED_MISSING_BROADCAST_RECEPTIONSV2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS
Likely outcomes — click to expand
Based on 799,618 missions where this alarm fired in the last
90 days
(for V2V_SELF_CHECK_FAILED_MISSING_TRANSMISSIONS) as of 2026-10-13
Grounding vs discrepancy (of 5,464 ZERP issues filed on these missions)
Top work orders
- EV3: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 203
- Troubleshoot Hover Motor Resistance on Aircraft · INSPECTION 73
- EV2: Troubleshoot Electrical Contacts on Aircraft and Droid · INSPECTION 66
- Reset Droid Lid · TROUBLESHOOTING 53
- EV3: Replace Stbd Prepped Hover Harness on Aircraft · MAINTENANCE_ACTION 33
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| SERVO, ASSY, UNIVERSAL, P2 | 20398 | 884 |
| CW/CCW HOVER MOTOR ASSY, ZIP, P2 | 19607 | 793 |
| ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 | 48477 | 740 |
| TAIL ASSY STBD(RH), PRE-EV2, 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”These alarms cover missing V2V self-check transmissions or missing/insufficient V2V broadcast self-check receptions. This guide first rules out higher-priority related alarms, then routes missing transmissions or checks end-to-end V2V broadcast performance between computes A and B.
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..."]
use-missing-cellular-guide["<small><b>Step 5</b></small><br/>Action: Use the V2V_SELF_CHECK_FAILED_MISSIN..."]
use-wireless-regdomain-guide["<small><b>Step 6</b></small><br/>Action: Use the WIRELESS_REGDOMAIN_INCORRECT..."]
troubleshoot-actual-preflight-failure["<small><b>Step 7</b></small><br/>Action: Troubleshoot the alarm that actually ..."]
is-this-an-experimental-build{"<small><b>Step 8</b></small><br/>Question: Is this Zip using experimental antenn..."}
escalate-to-test-requester{{"<small><b>Step 9</b></small><br/>Escalation: Escalate to the test requester. Inclu..."}}
which-alarm-are-you-triaging{"<small><b>Step 10</b></small><br/>Question: Which alarm are you triaging?"}
escalate-missing-transmissions{{"<small><b>Step 11</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
load-v2v-self-check-broadcast-debug["<small><b>Step 12</b></small><br/>Telemetry: Load the V2V_SELF_CHECK_FAILED_INSUF..."]
what-does-the-broadcast-triage-show{"<small><b>Step 13</b></small><br/>Question: What does the V2V_SELF_CHECK_FAILED_..."}
how-many-reception-ratios-below-80{"<small><b>Step 14</b></small><br/>Question: How many of the four compute A/B rece..."}
escalate-inconsistent-publish-period{{"<small><b>Step 15</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
escalate-inconclusive-broadcast-triage{{"<small><b>Step 16</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
escalate-none-of-these-broadcast-triage{{"<small><b>Step 17</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
escalate-one-ratio-below-80{{"<small><b>Step 18</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
escalate-two-ratios-below-80{{"<small><b>Step 19</b></small><br/>Escalation: Escalate to P2 Avionics Hardware On C..."}}
escalate-three-ratios-below-80{{"<small><b>Step 20</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
escalate-four-ratios-below-80{{"<small><b>Step 21</b></small><br/>Escalation: Escalate to P2 Avionics Hardware On C..."}}
return-to-service["<small><b>Step 22</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: WIRELESS...| use-wireless-regdomain-guide
what-happened-after-preflight-retry -->|Preflight Failure: V2V_SELF...| use-missing-cellular-guide
what-happened-after-preflight-retry -->|Preflight Failure: V2V_SELF...| is-this-an-experimental-build
what-happened-after-preflight-retry -->|Preflight Failure: V2V_SELF...| is-this-an-experimental-build
what-happened-after-preflight-retry -->|Preflight Failure: V2V_SELF...| is-this-an-experimental-build
what-happened-after-preflight-retry -->|Preflight Failure: None of ...| troubleshoot-actual-preflight-failure
what-happened-after-preflight-retry -->|No Preflight Failure| return-to-service
is-this-an-experimental-build -->|experimental antennas| escalate-to-test-requester
is-this-an-experimental-build -->|experimental compute board ...| escalate-to-test-requester
is-this-an-experimental-build -->|experimental software| escalate-to-test-requester
is-this-an-experimental-build -->|none of these| which-alarm-are-you-triaging
which-alarm-are-you-triaging -->|missing transmissions| escalate-missing-transmissions
which-alarm-are-you-triaging -->|insufficient receptions| load-v2v-self-check-broadcast-debug
which-alarm-are-you-triaging -->|missing receptions| load-v2v-self-check-broadcast-debug
load-v2v-self-check-broadcast-debug --> what-does-the-broadcast-triage-show
what-does-the-broadcast-triage-show -->|inconsistent v2v_metrics pu...| escalate-inconsistent-publish-period
what-does-the-broadcast-triage-show -->|one or more reception ratio...| how-many-reception-ratios-below-80
what-does-the-broadcast-triage-show -->|inconclusive / I'm not sure| escalate-inconclusive-broadcast-triage
what-does-the-broadcast-triage-show -->|None of these| escalate-none-of-these-broadcast-triage
how-many-reception-ratios-below-80 -->|1/4| escalate-one-ratio-below-80
how-many-reception-ratios-below-80 -->|2/4| escalate-two-ratios-below-80
how-many-reception-ratios-below-80 -->|3/4| escalate-three-ratios-below-80
how-many-reception-ratios-below-80 -->|4/4 signals below 80%| escalate-four-ratios-below-80
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 use-missing-cellular-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style use-wireless-regdomain-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style troubleshoot-actual-preflight-failure fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-this-an-experimental-build fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-test-requester fill:#fef3c7,stroke:#f59e0b,color:#78350f
style which-alarm-are-you-triaging fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-missing-transmissions fill:#fef3c7,stroke:#f59e0b,color:#78350f
style what-does-the-broadcast-triage-show fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style how-many-reception-ratios-below-80 fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-inconsistent-publish-period fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-inconclusive-broadcast-triage fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-none-of-these-broadcast-triage fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-one-ratio-below-80 fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-two-ratios-below-80 fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-three-ratios-below-80 fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-four-ratios-below-80 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. Triage
RX_V2V_ABSENT before the broadcast self-check alarm. 5 action
Use the V2V_SELF_CHECK_FAILED_MISSING_CELLULAR_RECEPTIONS guide before continuing with this broadcast reception guide.
6 action
Use the WIRELESS_REGDOMAIN_INCORRECT guide before continuing with this broadcast reception guide.
7 action
Troubleshoot the alarm that actually caused the preflight failure before returning the Aircraft to service.
8 question
Is this Zip using experimental antennas, compute board / avionics hardware, or software?
9 escalation
Escalate to the test requester. Include the mission ID, the experimental configuration selected in this guide, and the exact V2V self-check alarm.
10 question
Which alarm are you triaging?
11 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and call out that
V2V_SELF_CHECK_FAILED_MISSING_TRANSMISSIONS reproduced after the power cycle and higher-priority alarm checks. 12 telemetry
Load the
For missing or insufficient broadcast self-checks, we check end-to-end V2V broadcast performance between computes A and B. Inspect the reception ratio plots for compute A and compute B.
V2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS log plot template for the failed mission. Example: V2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS.For missing or insufficient broadcast self-checks, we check end-to-end V2V broadcast performance between computes A and B. Inspect the reception ratio plots for compute A and compute B.
Enter the mission identifier above to load the plot.
13 question
What does the
V2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS triage plot show? 14 question
How many of the four compute A/B reception ratio signals are below 80%?
15 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and a Baraza share link for the
V2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS plot, and call out that the v2v_metrics publish period is inconsistent. 16 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and a Baraza share link for the
V2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS plot, and call out that the plot was inconclusive. 17 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and a Baraza share link for the
V2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS plot, and call out that none of the listed triage cases matched. 18 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and a Baraza share link for the
V2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS plot, and call out that 1 of 4 reception ratio signals is below 80%. 19 escalation
Escalate to P2 Avionics Hardware On Call to confirm whether to swap a compute and antenna assembly, and to help identify which compute assembly to swap. Include the mission ID and a Baraza share link for the
V2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS plot, and call out that 2 of 4 reception ratio signals are below 80%. 20 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and a Baraza share link for the
V2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS plot, and call out that 3 of 4 reception ratio signals are below 80%. 21 escalation
Escalate to P2 Avionics Hardware On Call to confirm whether to swap compute boards, possibly both. Include the mission ID and a Baraza share link for the
V2V_SELF_CHECK_FAILED_INSUFFICIENT_BROADCAST_RECEPTIONS plot, and call out that all 4 reception ratio signals are below 80%. 22 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.