Skip to content
Zipline Zipline Service Documentation

    CHARGER_MCU_INITIALIZATION_FAILED

    published Last Updated: Oct 9, 2026 HW: all
    Applicable alarms (1)
    CHARGER_MCU_INITIALIZATION_FAILED
    Likely outcomes (0 missions) — click to expand

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

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

    Background

    Section titled “Background”

    This alarm happens if the DeltaQ charger controller is unable to initialize. In this case, the charger needs to be replaced.

    Troubleshooting Steps

    Section titled “Troubleshooting Steps”
    1 action
    This is a persistent DeltaQ charger processor initialization error. Create a work order with the notes "this charger should be RMA'd to DeltaQ".

    Did this guide help you get unblocked?

    Open suggestions

    There are no open suggestions.

    Open pull requests

    There are no open pull requests.

    Edit this page on GitHub
    Topic history
    1. 2026-10-07 Susan Minne Bulk/mechanical change
      Replace individual guide ownership with system technical contacts
      Commit dca5a1a
    2. 2026-09-24 Susan Minne Bulk/mechanical change
      chore: backfill asset and dock owner identities
      Commit c82f87b
    3. 2026-09-13 Susan Minne Bulk/mechanical change
      feat: add MX approval metadata to topics
      Commit 406a785
    Baseline import
    Initial import into service_docs
    Imported by kkuwatani on 2026-08-12
    Add charger MCU initialization alarm topic
    Commit d4a6afe
    Suggest a change