V2V_SELF_CHECK_SOFTWARE_ISSUE
Viewing this guide for
Applicable alarms (1)
V2V_SELF_CHECK_SOFTWARE_ISSUE
Likely outcomes — click to expand
Based on 1,630 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 32 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| PREPPED HOVER HARNESSING, STBD, ZIP, P2 | 0117583 | 16 |
| ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 | 48477 | 7 |
| WING GEARBOX ASM, LONG WING, ZIP, P2 | 0111424 | 2 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”V2V_SELF_CHECK_SOFTWARE_ISSUE indicates the self-check machinery itself reached an inconsistent or impossible state.
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 ..."]
is-software-new-enough{"<small><b>Step 6</b></small><br/>Question: Which software version is the Aircraf..."}
troubleshoot-every-other-alarm["<small><b>Step 7</b></small><br/>Action: Explicitly troubleshoot every other a..."]
still-blocked-after-other-alarms{"<small><b>Step 8</b></small><br/>Question: After troubleshooting every other ala..."}
is-site-wide-network-pattern-present{"<small><b>Step 9</b></small><br/>Question: Is at least one other vehicle at the ..."}
load-v2v-self-check-software-debug["<small><b>Step 10</b></small><br/>Telemetry: Load the Triage: V2V_SELF_CHECK_SOFT..."]
what-software-symptom-is-present{"<small><b>Step 11</b></small><br/>Question: Which software or integration symptom..."}
escalate-software-integration-bug{{"<small><b>Step 12</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
escalate-site-backing-network-unhealthy{{"<small><b>Step 13</b></small><br/>Escalation: Escalate to IT Networking On Call to ..."}}
escalate-new-software-still-blocked{{"<small><b>Step 14</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
escalate-with-plot-and-mission{{"<small><b>Step 15</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
return-to-service["<small><b>Step 16</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: V2V_SELF...| is-software-new-enough
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-software-new-enough -->|2026.03| is-site-wide-network-pattern-present
is-software-new-enough -->|2026.09| is-site-wide-network-pattern-present
is-software-new-enough -->|2026.15| is-site-wide-network-pattern-present
is-software-new-enough -->|2026.15.1| troubleshoot-every-other-alarm
is-software-new-enough -->|2026.22+| troubleshoot-every-other-alarm
troubleshoot-every-other-alarm --> still-blocked-after-other-alarms
still-blocked-after-other-alarms -->|Yes| escalate-new-software-still-blocked
still-blocked-after-other-alarms -->|No| return-to-service
is-site-wide-network-pattern-present -->|ZIP_ONBOARD_PLANNING_ERROR_...| escalate-site-backing-network-unhealthy
is-site-wide-network-pattern-present -->|V2V_SELF_CHECK_SOFTWARE_ISSUE| escalate-site-backing-network-unhealthy
is-site-wide-network-pattern-present -->|None of the above| load-v2v-self-check-software-debug
load-v2v-self-check-software-debug --> what-software-symptom-is-present
what-software-symptom-is-present -->|Inconsistent delta microsec...| escalate-software-integration-bug
what-software-symptom-is-present -->|Not Present / 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 use-rx-v2v-absent-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style troubleshoot-actual-preflight-failure fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-software-new-enough fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style troubleshoot-every-other-alarm fill:#dcfce7,stroke:#22c55e,color:#14532d
style still-blocked-after-other-alarms fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style is-site-wide-network-pattern-present fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style what-software-symptom-is-present fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-software-integration-bug fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-site-backing-network-unhealthy fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-new-software-still-blocked 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
Use the RX_V2V_ABSENT guide instead. Troubleshoot the broader publishable self-V2V receive failure before treating this as a software self-check issue.
5 action
Troubleshoot the alarm that actually caused the preflight failure before returning the Aircraft to service.
6 question
Which software version is the Aircraft running?
7 action
Explicitly troubleshoot every other alarm present on the vehicle. On
2026.15.1, 2026.22, and newer software, V2V_SELF_CHECK_SOFTWARE_ISSUE is no longer preflight blocking, so another alarm should be responsible for the block. 8 question
After troubleshooting every other alarm present on the vehicle, is mission preflight still blocked?
9 question
Is at least one other vehicle at the same site also showing a V2V self-check alarm or rejections due to
ZIP_ONBOARD_PLANNING_ERROR_CODES_MOTION_CHECK_MAP_MANAGER_REJECTED? 10 telemetry
Load the
Example of a time-inconsistent cause of
Triage: V2V_SELF_CHECK_SOFTWARE_ISSUE log plot template for the failed mission. Example: Triage: V2V_SELF_CHECK_SOFTWARE_ISSUE.Example of a time-inconsistent cause of
V2V_SELF_CHECK_SOFTWARE_ISSUE: Enter the mission identifier above to load the plot.
11 question
Which software or integration symptom is visible in the plot?
12 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and a Baraza share link for the
Triage: V2V_SELF_CHECK_SOFTWARE_ISSUE plot from the relevant mission failure. We have a previously never before seen software issue cause. 13 escalation
Escalate to IT Networking On Call to triage the site's backing network. Include the mission ID, site, affected vehicles, the Baraza share link for the
Triage: V2V_SELF_CHECK_SOFTWARE_ISSUE plot, and this reference: ISS-140093. Example: networking escalation case. We see this failure mode when the site's backing network is unhealthy. This is a bug in the 2026.15 and earlier implementation of the zip_v2v_agent, where we effectively crash if GPS time moves during preflight. We see this symptom only persists at commercial sites with nonstandard networking infrastructure, particularly if the networking is saturated by many Zips. The specific V2V alarm is nonblocking on 2026.15.1, 2026.22, and newer software, but on older software this needs IT Networking triage. 14 escalation
Escalate to P2 Embedded Linux On Call. Include the software version, mission ID, the list of other alarms that were present, and what was done to troubleshoot each one. Call out that the vehicle is still preflight blocked even though
V2V_SELF_CHECK_SOFTWARE_ISSUE should not be preflight blocking on this software. 15 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and a Baraza share link for the
Triage: V2V_SELF_CHECK_SOFTWARE_ISSUE plot from the relevant mission failure. 16 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.