BUSBAR_TELEMETRY_INSUFFICIENT
Applicable alarms (8)
Likely outcomes — click to expand
Based on 850,418 missions where this alarm fired in the last
90 days
(for BUSBAR_TELEMETRY_INSUFFICIENT) as of 2026-10-13
Grounding vs discrepancy (of 4,468 ZERP issues filed on these missions)
Top work orders
- EV2: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 229
- EV3: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 215
- Inspect Droid after Droid Left Behind (DLB) · MAINTENANCE_ACTION 185
- Reset Droid after DLB · REPAIR 116
- Troubleshoot Hover Motor Resistance on Aircraft · INSPECTION 78
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| SERVO, ASSY, UNIVERSAL, P2 | 20398 | 1,041 |
| PRE-PREG TAIL ASSY STBD(RH), ZIP, P2 | 21840 | 826 |
| CCW HOVER MOTOR ASSY, EV3 ZIP, P2 | 19607 | 825 |
| PRE-PREG TAIL ASSY, AL, PORT(LH), ZIP, P2 | 31280 | 786 |
| ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 | 48477 | 782 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm indicates whether or not there is sufficient telemetry to determine whether or not the following in-alarms should be set or clear:
In Flight:
- ERROR_VBAT_POS_PHASE_RESISTANCE- ERROR_VBAT_NEG_PHASE_RESISTANCEdepends on Battery, Distro A, and Distro B telemetry.
Prior to flight:
- ERROR_VBAT_POS_PHASE_RESISTANCE- ERROR_VBAT_NEG_PHASE_RESISTANCE- ERROR_HOVER_PORT_AFT_RESISTANCE- ERROR_HOVER_PORT_FWD_RESISTANCE- ERROR_HOVER_STBD_AFT_RESISTANCE- ERROR_HOVER_STBD_FWD_RESISTANCE- ERROR_MIXED_MOTOR_RESISTANCEdepends on Battery, Distro A, Distro B, and Propulsion Motor telemetry.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
when-did-the-failure-occur{"<small><b>Step 1</b></small><br/>Question: When did the failure occur?"}
before-preflight-motor-spins-expected["<small><b>Step 2</b></small><br/>Action: This alarm is expected to be set unti..."]
after-preflight-other-system-issue{"<small><b>Step 3</b></small><br/>Question: Is there an issue with any other syst..."}
after-preflight-secondary-continue-triaging["<small><b>Step 4</b></small><br/>Action: This alarm is secondary to the other ..."]
after-preflight-raise-to-firmware-motors{{"<small><b>Step 5</b></small><br/>Escalation: Raise to P2-firmware-motors-on-call"}}
in-flight-other-system-issue{"<small><b>Step 6</b></small><br/>Question: Is there an issue with any other syst..."}
in-flight-secondary-continue-triaging["<small><b>Step 7</b></small><br/>Action: This alarm is secondary to the other ..."]
in-flight-raise-firmware-motors{{"<small><b>Step 8</b></small><br/>Escalation: Raise P2-firmware-motors-on-call"}}
when-did-the-failure-occur -->|Before preflight motor spins.| before-preflight-motor-spins-expected
when-did-the-failure-occur -->|After preflight motor spins...| after-preflight-other-system-issue
when-did-the-failure-occur -->|In flight.| in-flight-other-system-issue
after-preflight-other-system-issue -->|Yes| after-preflight-secondary-continue-triaging
after-preflight-other-system-issue -->|No| after-preflight-raise-to-firmware-motors
in-flight-other-system-issue -->|Yes| in-flight-secondary-continue-triaging
in-flight-other-system-issue -->|No| in-flight-raise-firmware-motors
style when-did-the-failure-occur fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style before-preflight-motor-spins-expected fill:#dcfce7,stroke:#22c55e,color:#14532d
style after-preflight-other-system-issue fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style after-preflight-secondary-continue-triaging fill:#dcfce7,stroke:#22c55e,color:#14532d
style after-preflight-raise-to-firmware-motors fill:#fef3c7,stroke:#f59e0b,color:#78350f
style in-flight-other-system-issue fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style in-flight-secondary-continue-triaging fill:#dcfce7,stroke:#22c55e,color:#14532d
style in-flight-raise-firmware-motors fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
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.