FUSION_ENGINE_CRASHED
Applicable alarms (2)
Likely outcomes — click to expand
Based on 3 missions where this alarm fired in the last
90 days
(for FUSION_ENGINE_CRASHED) 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 is set when the positioning engine in the GNSS driver crashes. This alarm does not directly block preflight or cause DockASAPs. It is set as an indicator for the cause behind other alarms such as GNSS_X_DEGRADED set by navigation.
Troubleshooting Steps
Section titled “Troubleshooting Steps”For steps, see Power Cycle Aircraft.
Engineering Guidance
Section titled “Engineering Guidance”Look at log output from the GNSS service on the node that the alarm was set on. Output from the Fusion Engine should be shown.
Check log files for a file that ends with point_one_logs.tar.gz. This is an archive of the positioning engine s logs at the time of failure. This can be provided to Point One for further diagnosis.
graph TD
the-alarm-may-clear-itself-if-the-vehic["<small><b>Step 1</b></small><br/>Action: The alarm may clear itself if the veh..."]
wait-up-to-10-minutes-for-the-alarm-to["<small><b>Step 2</b></small><br/>Action: Wait up to 10 minutes for the alarm t..."]
did-the-alarm-clear{"<small><b>Step 3</b></small><br/>Question: Did the alarm clear?"}
return-vehicle-to-service["<small><b>Step 4</b></small><br/>Action: Return vehicle to service"]
did-that-resolve-the-issue{"<small><b>Step 5</b></small><br/>Question: Did that resolve the issue?"}
return-vehicle-to-service-2["<small><b>Step 6</b></small><br/>Action: Return vehicle to service"]
escalate-to-embedded-linux{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to Embedded Linux"}}
the-alarm-may-clear-itself-if-the-vehic --> wait-up-to-10-minutes-for-the-alarm-to
wait-up-to-10-minutes-for-the-alarm-to --> did-the-alarm-clear
did-the-alarm-clear -->|Yes| return-vehicle-to-service
did-the-alarm-clear -->|No| did-that-resolve-the-issue
did-that-resolve-the-issue -->|Yes| return-vehicle-to-service-2
did-that-resolve-the-issue -->|No| escalate-to-embedded-linux
style the-alarm-may-clear-itself-if-the-vehic fill:#dcfce7,stroke:#22c55e,color:#14532d
style wait-up-to-10-minutes-for-the-alarm-to fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-the-alarm-clear fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-vehicle-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-that-resolve-the-issue fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-vehicle-to-service-2 fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-embedded-linux fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
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.