0x000A0051: CAPABILITY_DIAGNOSTIC_PACKAGE_PRESENT
Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x000A0051) as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”Use this workflow to clear a CAPABILITY_DIAGNOSTIC_PACKAGE_PRESENT alarm on a Zip.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
perform-a-wfh-flight-to-remove-the-package["<small><b>Step 1</b></small><br/>Action: Perform a WFH flight to remove the pa..."]
did-the-error-clear-after-the-flight{"<small><b>Step 2</b></small><br/>Question: Did the error clear?"}
return-the-zip-to-service["<small><b>Step 3</b></small><br/>Action: Return the Zip to service."]
restart-the-droid-target["<small><b>Step 4</b></small><br/>Action: Restart the droid target. a. SSH into..."]
did-the-error-clear-after-restarting-the-droid-target{"<small><b>Step 5</b></small><br/>Question: Did the error clear?"}
return-the-zip-to-operations["<small><b>Step 6</b></small><br/>Action: Return the Zip to operations."]
escalate-to-p2-droid-autonomy-on-call{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to P2 Droid Autonomy On Call."}}
perform-a-wfh-flight-to-remove-the-package --> did-the-error-clear-after-the-flight
did-the-error-clear-after-the-flight -->|Yes| return-the-zip-to-service
did-the-error-clear-after-the-flight -->|No| restart-the-droid-target
restart-the-droid-target --> did-the-error-clear-after-restarting-the-droid-target
did-the-error-clear-after-restarting-the-droid-target -->|Yes| return-the-zip-to-operations
did-the-error-clear-after-restarting-the-droid-target -->|No| escalate-to-p2-droid-autonomy-on-call
style perform-a-wfh-flight-to-remove-the-package fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-the-error-clear-after-the-flight fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-the-zip-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style restart-the-droid-target fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-the-error-clear-after-restarting-the-droid-target fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-the-zip-to-operations fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-droid-autonomy-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
a. SSH into the Droid through Dock, then run:
ssh_droid.b. Restart the base.target:
sudo systemctl restart base.target.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.