V2V_SELF_CHECK_FAILED_MISSING_CELLULAR_RECEPTIONS
Viewing this guide for
Applicable alarms (1)
V2V_SELF_CHECK_FAILED_MISSING_CELLULAR_RECEPTIONS
Likely outcomes — click to expand
Based on 876,454 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 6,230 ZERP issues filed on these missions)
Top work orders
- EV3: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 258
- Reset Droid after DLB · REPAIR 144
- Troubleshoot Hover Motor Resistance on Aircraft · INSPECTION 75
- EV2: Troubleshoot Electrical Contacts on Aircraft and Droid · INSPECTION 69
- Offload Droid Logs after DLB · ADMINISTRATIVE 67
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| SERVO, ASSY, UNIVERSAL, P2 | 20398 | 1,078 |
| ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 | 48477 | 932 |
| CCW HOVER MOTOR ASSY, EV3 ZIP, P2 | 19607 | 932 |
| TAIL STBD, ZIP, P2 | 21840 | 684 |
| TAIL, FIXED WING, PORT, ZIP, P2 | 31280 | 651 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm covers missing cellular receptions in the V2V self-check.
This guide first rules out RX_V2V_ABSENT, WIRELESS_REGDOMAIN_INCORRECT, and other cellular health alarms, then uses the missing cellular receptions triage plot.
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-wireless-regdomain-guide["<small><b>Step 5</b></small><br/>Action: Use the WIRELESS_REGDOMAIN_INCORRECT..."]
triage-other-cellular-health-alarm["<small><b>Step 6</b></small><br/>Action: Triage that cellular health alarm bef..."]
troubleshoot-actual-preflight-failure["<small><b>Step 7</b></small><br/>Action: Troubleshoot the alarm that actually ..."]
load-v2v-self-check-cellular-debug["<small><b>Step 8</b></small><br/>Telemetry: Load the Triage: V2V_SELF_CHECK_FAIL..."]
what-does-the-cellular-plot-show{"<small><b>Step 9</b></small><br/>Question: Which symptom is visible in the Tria..."}
escalate-inconsistent-publish-period{{"<small><b>Step 10</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
escalate-cellular-reception-count-zero{{"<small><b>Step 11</b></small><br/>Escalation: Escalate to P2 Embedded Platform On C..."}}
escalate-inconclusive-cellular-triage{{"<small><b>Step 12</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
return-to-service["<small><b>Step 13</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: Other ce...| triage-other-cellular-health-alarm
what-happened-after-preflight-retry -->|Preflight Failure: V2V_SELF...| load-v2v-self-check-cellular-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-self-check-cellular-debug --> what-does-the-cellular-plot-show
what-does-the-cellular-plot-show -->|inconsistent v2v_metrics pe...| escalate-inconsistent-publish-period
what-does-the-cellular-plot-show -->|this_compute_selfcheck.cell...| escalate-cellular-reception-count-zero
what-does-the-cellular-plot-show -->|inconclusive / not sure| escalate-inconclusive-cellular-triage
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-wireless-regdomain-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style triage-other-cellular-health-alarm fill:#dcfce7,stroke:#22c55e,color:#14532d
style troubleshoot-actual-preflight-failure fill:#dcfce7,stroke:#22c55e,color:#14532d
style what-does-the-cellular-plot-show fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-inconsistent-publish-period fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-cellular-reception-count-zero fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-inconclusive-cellular-triage 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 missing cellular reception alarm. 5 action
Use the WIRELESS_REGDOMAIN_INCORRECT guide before continuing with the missing cellular reception alarm.
6 action
Triage that cellular health alarm before continuing with this guide.
7 action
Troubleshoot the alarm that actually caused the preflight failure before returning the Aircraft to service.
8 telemetry
Load the
Example of the plotting state:
Triage: V2V_SELF_CHECK_FAILED_MISSING_CELLULAR_RECEPTIONS log plot template for the failed mission. Example: Triage: V2V_SELF_CHECK_FAILED_MISSING_CELLULAR_RECEPTIONS.Example of the plotting state:
Enter the mission identifier above to load the plot.
9 question
Which symptom is visible in the
Triage: V2V_SELF_CHECK_FAILED_MISSING_CELLULAR_RECEPTIONS plot? 10 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and a Baraza share link for the
Triage: V2V_SELF_CHECK_FAILED_MISSING_CELLULAR_RECEPTIONS plot, and call out that the v2v_metrics period is inconsistent. 11 escalation
Escalate to P2 Embedded Platform On Call. Include the mission ID and a Baraza share link for the
Triage: V2V_SELF_CHECK_FAILED_MISSING_CELLULAR_RECEPTIONS plot, and call out that this_compute_selfcheck.cellular_reception_count reports 0. 12 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and a Baraza share link for the
Triage: V2V_SELF_CHECK_FAILED_MISSING_CELLULAR_RECEPTIONS plot, and call out that the plot was inconclusive or the symptom was unclear. 13 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.