Skip to content

Degraded AFE Comms

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (2)
AFE_TELEMETRY_TIMEOUTAFE_CONFIGURATION_FAILED
Likely outcomes (44 missions, 41 issues) — click to expand

Based on 44 missions where this alarm fired in the last 90 days (for AFE_TELEMETRY_TIMEOUT) as of 2026-10-13

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

Grounding 12.2% (5 of 41 issues) Discrepancy 87.8% (36 of 41 issues)

Top work orders

  • EV2 Zip Detailed Battery Inspection · TROUBLESHOOTING 22
  • EV2/EV3 Perform Preflight Without Motors · INSPECTION 12

Frequently replaced parts

Part P/N Removals
BATTERY ASSY, ZIP, P2 27158 49
CCW HOVER MOTOR ASSY, ZIP, P2 19607 12
CW HOVER MOTOR ASSY, ZIP, P2 33333 8

Frequently co-occurring alarms (% of the 44 missions above)

BATTERY_UNSAFE_TO_CHARGE 100% of missions

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

These alarms occur when too much time has elapsed since valid AFE telemetry was received or if we never established successful communication with the AFE on the battery pack. This typically indicates a failure with the data connectors from the distro to the AFE.

Select a hardware variant above to start this troubleshooting flow.

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.