Skip to content

Battery Status Unavailable

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
ZIP_BATTERY_STATUS_UNAVAILABLE
Likely outcomes (71 missions, 21 issues) — click to expand

Based on 71 missions where this alarm fired in the last 90 days as of 2026-10-13

Grounding vs discrepancy (of 21 ZERP issues filed on these missions)

Grounding 19% (4 of 21 issues) Discrepancy 81% (17 of 21 issues)

Frequently replaced parts

Part P/N Removals
LEFT DOOR ASSY, DROID, P2 21830 18
RIGHT DOOR ASSY, DROID, P2 21827 18
PARALAND ASSY, DROID, P2 18427 14
BATTERY, DROID, P2 24544 12
BRAIN, LRU, DROID, P2 31920 10

Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.

This alarm triggers if the zip executive does not receive a battery message reported by the distro within the watchdog timeout.

Often this alarm is caused by a distro a or battery status reporter crashing, running at too slow of a rate, or publishing too infrequently. This alarm can also be caused by compute performance issues and IPC issues (these cases often see multiple watchdog alarms). If this persists throughout preflight and causes a mission failure, follow the steps below.

  • ZIP_BATTERY_STATUS_UNAVAILABLE
1 escalation
Try resending a mission. If this problem persists, escalate to P2 Firmware Power On Call.

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.