UNSAFE_TO_OPERATE - /thruster_main.droid_battery_status
Viewing this guide for
Applicable alarms (1)
UNSAFE_TO_OPERATE
Likely outcomes — 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 is a summary alarm that indicates an off-nominal condition is blocking the droid battery from operating.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
in-the-thruster-main-droid-battery-stat{"<small><b>Step 1</b></small><br/>Question: In the **thruster_main.droid_battery_..."}
sw-overtemp-critical-or-hw-overtemp-cri{"<small><b>Step 2</b></small><br/>Question: Use baraza to check: droid_battery_st..."}
overtemp-yes-reboot-the-droid["<small><b>Step 3</b></small><br/>Action: Reboot the droid. Re-check **thruster..."]
overtemp-no-allow-the-pack-to-cool["<small><b>Step 4</b></small><br/>Action: Allow the pack to cool. Complete one ..."]
sw-undertemp-critical{"<small><b>Step 5</b></small><br/>Question: Use baraza to check: droid_battery_st..."}
undertemp-yes-reboot-the-droid["<small><b>Step 6</b></small><br/>Action: Reboot the droid. Re-check **thruster..."]
undertemp-no-allow-the-pack-to-warm["<small><b>Step 7</b></small><br/>Action: Allow the pack to warm. Complete one ..."]
sw-brick-undervoltage-critical-or-hw-br{"<small><b>Step 8</b></small><br/>Question: Use baraza to check: droid_battery_st..."}
undervoltage-yes-reboot-the-droid["<small><b>Step 9</b></small><br/>Action: Reboot the droid. Re-check **thruster..."]
undervoltage-no-escalate-to-p2-firmware{{"<small><b>Step 10</b></small><br/>Escalation: Escalate to P2 Firmware Power On Call."}}
sw-brick-overvoltage-critical-or-hw-bri{"<small><b>Step 11</b></small><br/>Question: Use baraza to check: droid_battery_st..."}
overvoltage-yes-reboot-the-droid["<small><b>Step 12</b></small><br/>Action: Reboot the droid. Re-check **thruster..."]
overvoltage-no-escalate-to-p2-firmware{{"<small><b>Step 13</b></small><br/>Escalation: Escalate to P2 Firmware Power On Call."}}
hw-overcurrent-discharge-hw-persistent-{{"<small><b>Step 14</b></small><br/>Escalation: Escalate to P2 Firmware Power On Call."}}
in-the-thruster-main-droid-battery-stat -->|SW_OVERTEMP_CRITICAL or HW_...| sw-overtemp-critical-or-hw-overtemp-cri
in-the-thruster-main-droid-battery-stat -->|SW_UNDERTEMP_CRITICAL| sw-undertemp-critical
in-the-thruster-main-droid-battery-stat -->|SW_BRICK_UNDERVOLTAGE_CRITI...| sw-brick-undervoltage-critical-or-hw-br
in-the-thruster-main-droid-battery-stat -->|SW_BRICK_OVERVOLTAGE_CRITIC...| sw-brick-overvoltage-critical-or-hw-bri
in-the-thruster-main-droid-battery-stat -->|HW_OVERCURRENT_DISCHARGE, H...| hw-overcurrent-discharge-hw-persistent-
sw-overtemp-critical-or-hw-overtemp-cri -->|Yes, it is below 80 degC| overtemp-yes-reboot-the-droid
sw-overtemp-critical-or-hw-overtemp-cri -->|No, it is above 80 degC| overtemp-no-allow-the-pack-to-cool
sw-undertemp-critical -->|Yes, it is above -35 degC| undertemp-yes-reboot-the-droid
sw-undertemp-critical -->|No, it is below -35 degC| undertemp-no-allow-the-pack-to-warm
sw-brick-undervoltage-critical-or-hw-br -->|Yes, it is above 2.4 V| undervoltage-yes-reboot-the-droid
sw-brick-undervoltage-critical-or-hw-br -->|No, it is below 2.4V| undervoltage-no-escalate-to-p2-firmware
sw-brick-overvoltage-critical-or-hw-bri -->|Yes, it is below 4.3 V| overvoltage-yes-reboot-the-droid
sw-brick-overvoltage-critical-or-hw-bri -->|No, it is above 4.3 V| overvoltage-no-escalate-to-p2-firmware
style in-the-thruster-main-droid-battery-stat fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style sw-overtemp-critical-or-hw-overtemp-cri fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style overtemp-yes-reboot-the-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style overtemp-no-allow-the-pack-to-cool fill:#dcfce7,stroke:#22c55e,color:#14532d
style sw-undertemp-critical fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style undertemp-yes-reboot-the-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style undertemp-no-allow-the-pack-to-warm fill:#dcfce7,stroke:#22c55e,color:#14532d
style sw-brick-undervoltage-critical-or-hw-br fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style undervoltage-yes-reboot-the-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style undervoltage-no-escalate-to-p2-firmware fill:#fef3c7,stroke:#f59e0b,color:#78350f
style sw-brick-overvoltage-critical-or-hw-bri fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style overvoltage-yes-reboot-the-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style overvoltage-no-escalate-to-p2-firmware fill:#fef3c7,stroke:#f59e0b,color:#78350f
style hw-overcurrent-discharge-hw-persistent- fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
In the thruster_main.droid_battery_status message, check which off_nominal bits are set and follow the instructions below.
2 question
Use baraza to check: droid_battery_status.max_temperature.
Is max_temperature below 80 degC?
Is max_temperature below 80 degC?
3 action
Reboot the droid.
Re-check thruster_main.droid_battery_status.
- If UNSAFE_TO_OPERATE is cleared, the asset is back in service.
- If the alarm persists, escalate to P2 Firmware Power On Call.
Re-check thruster_main.droid_battery_status.
- If UNSAFE_TO_OPERATE is cleared, the asset is back in service.
- If the alarm persists, escalate to P2 Firmware Power On Call.
4 action
Allow the pack to cool.
Complete one of the following actions:
- If max_temperature is still >= 80 degC after 10 minutes, escalate to P2 Firmware Power On Call.
- When the max_temperature is below 80 degC, reboot the droid. If the alarm persists, escalate to P2 Firmware Power On Call.
Complete one of the following actions:
- If max_temperature is still >= 80 degC after 10 minutes, escalate to P2 Firmware Power On Call.
- When the max_temperature is below 80 degC, reboot the droid. If the alarm persists, escalate to P2 Firmware Power On Call.
5 question
Use baraza to check: droid_battery_status.min_temperature.
Is min_temperature above -35 degC?
Is min_temperature above -35 degC?
6 action
Reboot the droid.
Re-check thruster_main.droid_battery_status.
- If UNSAFE_TO_OPERATE is cleared, the asset is back in service.
- If the alarm persists, escalate to P2 Firmware Power On Call.
Re-check thruster_main.droid_battery_status.
- If UNSAFE_TO_OPERATE is cleared, the asset is back in service.
- If the alarm persists, escalate to P2 Firmware Power On Call.
7 action
Allow the pack to warm.
Complete one of the following actions:
- If min_temperature is still <= -35 degC after 10 minutes, escalate to P2 Firmware Power On Call.
- When the min_temperature is above -35 degC, reboot the droid. If the alarm persists, escalate to P2 Firmware Power On Call.
Complete one of the following actions:
- If min_temperature is still <= -35 degC after 10 minutes, escalate to P2 Firmware Power On Call.
- When the min_temperature is above -35 degC, reboot the droid. If the alarm persists, escalate to P2 Firmware Power On Call.
8 question
Use baraza to check: droid_battery_status.min_brick_voltage_filtered.
Is min_brick_voltage_filtered above 2.4 V?
Is min_brick_voltage_filtered above 2.4 V?
9 action
Reboot the droid.
Re-check thruster_main.droid_battery_status.
- If UNSAFE_TO_OPERATE is cleared, the asset is back in service.
- If the alarm persists, escalate to P2 Firmware Power On Call.
Re-check thruster_main.droid_battery_status.
- If UNSAFE_TO_OPERATE is cleared, the asset is back in service.
- If the alarm persists, escalate to P2 Firmware Power On Call.
10 escalation
Escalate to P2 Firmware Power On Call.
11 question
Use baraza to check: droid_battery_status.max_brick_voltage_filtered.
Is max_brick_voltage_filtered below 4.3 V?
Is max_brick_voltage_filtered below 4.3 V?
12 action
Reboot the droid.
Re-check thruster_main.droid_battery_status.
- If UNSAFE_TO_OPERATE is cleared, the asset is back in service.
- If the alarm persists, escalate to P2 Firmware Power On Call.
Re-check thruster_main.droid_battery_status.
- If UNSAFE_TO_OPERATE is cleared, the asset is back in service.
- If the alarm persists, escalate to P2 Firmware Power On Call.
13 escalation
Escalate to P2 Firmware Power On Call.
14 escalation
Escalate to P2 Firmware Power On Call.
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.