Dock Not Waking Up Aircraft
Viewing this guide for
Background
Section titled “Background”The Aircraft is unable to be woken up by the Dock when using the \u201cZip Wakeup\u201d command in Fleetwrangler. In this case, the problem might be in the DeltaQ charger, hardware in the charging connection (fin, pins, sockets, etc.), or the distro board.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
check-the-docks-logs-on-baraza-with-the{"<small><b>Step 1</b></small><br/>Question: Check the Dock’s logs on Baraza with ..."}
check-the-alarm-that-was-set-that-caused["<small><b>Step 2</b></small><br/>Action: Check the alarm that was set that cau..."]
did-the-charger-service-state-go-to-zip{"<small><b>Step 3</b></small><br/>Question: Did the charger service state go to ..."}
the-problem-is-the-relay-failing-close-o["<small><b>Step 4</b></small><br/>Action: The problem is the relay failing clos..."]
did-actual-charge-voltage-rise-above-50v{"<small><b>Step 5</b></small><br/>Question: Check actual_charge_voltage/dock.cha..."}
try-redocking-the-same-aircraft-first["<small><b>Step 6</b></small><br/>Action: Try redocking the same Aircraft. If a..."]
did-redocking-resolve-the-wake-up-issue{"<small><b>Step 7</b></small><br/>Question: Did redocking resolve the wake-up issue?"}
inspect-for-high-resistance-contact["<small><b>Step 8</b></small><br/>Action: Check the previous charging cycle bet..."]
did-contact-inspection-resolve-the-issue{"<small><b>Step 9</b></small><br/>Question: Did inspecting the contact points, re..."}
the-dock-and-aircraft-may-return-to-service("<small><b>Step 10</b></small><br/>Reference: The Dock and Aircraft may return to s...")
are-all-four-4-zip-sockets-and-all-four{"<small><b>Step 11</b></small><br/>Question: Are all four 4 zip sockets and all ..."}
escalate-to-p2-dock-hardware-on-call-att{{"<small><b>Step 12</b></small><br/>Escalation: Escalate to P2 Dock Hardware On Call...."}}
escalate-to-p2-dock-embedded-on-call-att{{"<small><b>Step 13</b></small><br/>Escalation: Escalate to P2 Dock Embedded On Call...."}}
create-a-hardware-discrepancy-ticket-to["<small><b>Step 14</b></small><br/>Action: Create a hardware discrepancy ticket ..."]
check-the-docks-logs-on-baraza-with-the -->|Yes| check-the-alarm-that-was-set-that-caused
check-the-docks-logs-on-baraza-with-the -->|No| did-the-charger-service-state-go-to-zip
did-the-charger-service-state-go-to-zip -->|Yes| the-problem-is-the-relay-failing-close-o
did-the-charger-service-state-go-to-zip -->|No| did-actual-charge-voltage-rise-above-50v
did-actual-charge-voltage-rise-above-50v -->|Yes| try-redocking-the-same-aircraft-first
did-actual-charge-voltage-rise-above-50v -->|No| are-all-four-4-zip-sockets-and-all-four
try-redocking-the-same-aircraft-first --> did-redocking-resolve-the-wake-up-issue
did-redocking-resolve-the-wake-up-issue -->|Yes| the-dock-and-aircraft-may-return-to-service
did-redocking-resolve-the-wake-up-issue -->|No| inspect-for-high-resistance-contact
inspect-for-high-resistance-contact --> did-contact-inspection-resolve-the-issue
did-contact-inspection-resolve-the-issue -->|Yes| the-dock-and-aircraft-may-return-to-service
did-contact-inspection-resolve-the-issue -->|No| escalate-to-p2-dock-hardware-on-call-att
are-all-four-4-zip-sockets-and-all-four -->|Yes| escalate-to-p2-dock-hardware-on-call-att
are-all-four-4-zip-sockets-and-all-four -->|No| create-a-hardware-discrepancy-ticket-to
style check-the-docks-logs-on-baraza-with-the fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style check-the-alarm-that-was-set-that-caused fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-the-charger-service-state-go-to-zip fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-problem-is-the-relay-failing-close-o fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-actual-charge-voltage-rise-above-50v fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style try-redocking-the-same-aircraft-first fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-redocking-resolve-the-wake-up-issue fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style inspect-for-high-resistance-contact fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-contact-inspection-resolve-the-issue fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-dock-and-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style are-all-four-4-zip-sockets-and-all-four fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-p2-dock-hardware-on-call-att fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-to-p2-dock-embedded-on-call-att fill:#fef3c7,stroke:#f59e0b,color:#78350f
style create-a-hardware-discrepancy-ticket-to fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
Check the Dock’s logs on Baraza with the template “Charger Service” at the time the wake up command was sent. Did the charger service state go to
FAULTED when the wake up was attempted? 2 action
Check the alarm that was set that caused the charger service to go to FAULTED and follow the associated guide instead of this one. For example: OTHER_CHARGER_FAULT.
3 question
Did the charger service state go to
ZIP_WAKEUP_WAIT_FOR_RELAY but not ZIP_WAKEUP_ACTIVE? For reference, here is a nominal wake up state flow: 4 action
The problem is the relay failing close on the charger.
Continue troubleshooting by following this guide: MAX_RETRY_ATTEMPTS_FAILED
Continue troubleshooting by following this guide: MAX_RETRY_ATTEMPTS_FAILED
5 question
Check
actual_charge_voltage/dock.charger_status_debug during the wake up attempt. Did it rise above 50 V? 6 action
Try redocking the same Aircraft. If a redocking mission cannot be sent, continue to the connection inspection below.
7 question
Did redocking resolve the wake-up issue?
8 action
Check the previous charging cycle between this Dock and this Zip. Compare
If the Dock-side voltage and Zip-side voltage differ significantly during charging, or if
Inspect the Zip sockets and Dock pins, and make sure they have good contact. If needed, reseat the Zip in the Dock or use a different Dock to wake up the Zip.
actual_charge_voltage/dock.charger_status_debug with ls_zip_charge.voltage/distro_a.power_telemetry. If no previous charging cycle data is available, proceed directly to the physical inspection and reseat steps below.If the Dock-side voltage and Zip-side voltage differ significantly during charging, or if
actual_charge_voltage/dock.charger_status_debug spikes when charging is active, this likely indicates high-resistance contact between the Dock and Zip rather than a charger issue.Inspect the Zip sockets and Dock pins, and make sure they have good contact. If needed, reseat the Zip in the Dock or use a different Dock to wake up the Zip.
9 question
Did inspecting the contact points, reseating the Zip, or using a different Dock resolve the issue?
10 reference
The Dock and Aircraft may return to service.
11 question
Are all four (4) zip sockets and all four (4) Dock pins present and seated?
12 escalation
Escalate to P2 Dock Hardware On Call. Attach logs, findings, and photos.
13 escalation <=2026.15
Escalate to P2 Dock Embedded On Call. Attach logs, findings, and photos.
14 action
Create a hardware discrepancy ticket to replace the broken component.
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.