CPU_TEMP_UNKNOWN
Applicable alarms (1)
Likely outcomes — click to expand
Based on 86 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 1 ZERP issues filed on these missions)
Frequently co-occurring alarms (% of the 86 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm is triggered when the Zip or Droid has not yet, or is unable to, read the temperature of it\u2019s processor.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
has-the-vehicle-just-powered-on{"<small><b>Step 1</b></small><br/>Question: Has the vehicle just powered on?"}
wait-5-minutes-yes-powered-on["<small><b>Step 2</b></small><br/>Action: Wait 5 minutes"]
power-cycle-the-aircraft-power-cycle-ai["<small><b>Step 3</b></small><br/>Action: Power cycle the Aircraft Power Cycle..."]
wait-5-minutes-no-powered-on["<small><b>Step 4</b></small><br/>Action: Wait 5 minutes"]
has-the-alarm-cleared{"<small><b>Step 5</b></small><br/>Question: Has the alarm cleared?"}
return-aircraft-to-service("<small><b>Step 6</b></small><br/>Reference: Return Aircraft to service")
determine-which-compute-the-alarm-is-ra["<small><b>Step 7</b></small><br/>Action: Determine which compute the alarm is ..."]
journal-logs-from-compute-hardware-metri["<small><b>Step 8</b></small><br/>Action: Check journal logs from compute_hard..."]
escalate-to-embedded-linux-on-call{{"<small><b>Step 9</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
has-the-vehicle-just-powered-on -->|Yes| wait-5-minutes-yes-powered-on
has-the-vehicle-just-powered-on -->|No| power-cycle-the-aircraft-power-cycle-ai
wait-5-minutes-yes-powered-on --> has-the-alarm-cleared
power-cycle-the-aircraft-power-cycle-ai --> wait-5-minutes-no-powered-on
wait-5-minutes-no-powered-on --> has-the-alarm-cleared
has-the-alarm-cleared -->|Yes| return-aircraft-to-service
has-the-alarm-cleared -->|No| determine-which-compute-the-alarm-is-ra
determine-which-compute-the-alarm-is-ra --> journal-logs-from-compute-hardware-metri
journal-logs-from-compute-hardware-metri --> escalate-to-embedded-linux-on-call
style has-the-vehicle-just-powered-on fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style wait-5-minutes-yes-powered-on fill:#dcfce7,stroke:#22c55e,color:#14532d
style power-cycle-the-aircraft-power-cycle-ai fill:#dcfce7,stroke:#22c55e,color:#14532d
style wait-5-minutes-no-powered-on fill:#dcfce7,stroke:#22c55e,color:#14532d
style has-the-alarm-cleared fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-aircraft-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style determine-which-compute-the-alarm-is-ra fill:#dcfce7,stroke:#22c55e,color:#14532d
style journal-logs-from-compute-hardware-metri fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-embedded-linux-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
compute_hardware_metrics.service on the corresponding compute. These may give further information on the reason behind the alarm. Capture the relevant log lines to include in the escalation.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.