> 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/location-and-movement/engine-hours.md).

# Engine hours

Engine hours is a tool that allows owners of vehicles and special machinery to monitor engine running time and schedule [maintenance works](/docs/user/guide/fleet-management/maintenance.md) based on this data.

To activate Engine hours:

1. Open [Devices and settings](/docs/user/guide/devices-and-settings.md), choose the object you need, and proceed to the **Engine hours** block.
2. Click the **Add engine hours** button.
3. Choose a data source: ignition or engine hours from the CAN bus.
4. Set the initial value for engine hours (0 to 99,999,999 hours, up to 2 decimal places).
5. Click **Save**.

{% hint style="warning" %}
To receive data from the ignition sensor, create it [beforehand](/docs/user/guide/devices-and-settings/vehicle-sensors/discrete-sensors/ignition-source.md) as a discrete sensor.
{% endhint %}

{% hint style="info" %}
Unlike the [Odometer](/docs/user/guide/devices-and-settings/location-and-movement/odometer.md), engine hours has **no correction multiplier**.
{% endhint %}

To display engine hours data in the **Tracking** module, add the **Engine hours widget** to the widget bar at the bottom of the screen. Just click the **+** button at the upper-right corner of the widget bar and add the **Engine hours widget**.

## Availability

Appears on device models that report ignition or CAN-bus engine hours data.

## See also

* [Odometer](/docs/user/guide/devices-and-settings/location-and-movement/odometer.md): the equivalent counter for distance traveled, with correction multiplier support.
* [Fleet maintenance](/docs/user/guide/fleet-management/maintenance.md): schedule service intervals by engine hours.
* [Ignition source sensor](/docs/user/guide/devices-and-settings/vehicle-sensors/discrete-sensors/ignition-source.md): the discrete sensor required when using ignition as the data source.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/user/guide/devices-and-settings/location-and-movement/engine-hours.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.