> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/devices-and-settings/device-specific-controls/engine-and-diagnostics/engine-state-detection.md).

# Engine state detection

Configure the Engine state detection block in Navixy so the device reports engine on and off based on on-board voltage levels and durations.

Tells the device how to determine that the engine is running, based on on-board voltage. A running engine raises system voltage above the battery's resting level, typically from around 12 V at rest to 13–14 V when alternator charging.

## Settings

* **Engine-on voltage threshold**: the voltage level above which the engine is considered running. Typical value: 13.0–13.5 V.
* **Engine-on duration**: how long the voltage must stay above the threshold before the engine-on state is confirmed. A short duration (2–3 seconds) prevents false triggers from brief voltage spikes.
* **Engine-off voltage threshold**: the voltage level below which the engine is considered off. Typical value: 12.5 V.
* **Engine-off duration**: how long the voltage must stay below the threshold before the engine-off state is confirmed.

{% hint style="info" %}
Set the engine-off threshold a few tenths of a volt below the engine-on threshold to create a small gap between the on and off thresholds so the engine state doesn't flip back and forth when the voltage wavers at idle.
{% endhint %}

## Availability

Appears on device models that detect engine state from on-board voltage.

## See also

* [Ignition source](/docs/user/guide/devices-and-settings/location-and-movement/ignition-source.md): choose how the Navixy platform interprets ignition.
* [Fuel consumption calculation](/docs/user/guide/devices-and-settings/device-specific-controls/engine-and-diagnostics/fuel-consumption-calculation.md): device-side fuel estimate that depends on engine state.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/user/guide/devices-and-settings/device-specific-controls/engine-and-diagnostics/engine-state-detection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.