> 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/expert-center/es/vehicle-telematics-technology/fuel-management/fuel-control-in-navixy/analyzing-fuel-data.md).

# Análisis de datos de combustible

Navixy almacena lecturas del sensor de nivel de combustible con opciones flexibles de reconstrucción. Los reportes, widgets y alertas ayudan a monitorear el consumo y detectar anomalías.

La plataforma captura y almacena al instante las lecturas del sensor de nivel de combustible de Dispositivos conectados. Los datos se guardan solo después de crear un sensor de combustible dentro del sistema.

Los filtros para los valores mínimos y máximos, las tablas de calibración y otros ajustes del sensor se aplican durante la salida de datos. Como resultado, usted tiene la libertad de modificar los ajustes en cualquier momento y reconstruir Reportes para observar el impacto en los datos guardados. Esta flexibilidad de configuración garantiza que sus datos siempre estén sincronizados con los ajustes más recientes, manteniéndolos siempre actualizados.


---

# 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/expert-center/es/vehicle-telematics-technology/fuel-management/fuel-control-in-navixy/analyzing-fuel-data.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.