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

# Análise de dados de Combustível

A Navixy armazena leituras de sensores de Combustível com opções flexíveis de reconstrução. Relatórios, widgets e Alertas ajudam a monitorar o consumo e detectar anomalias.

A plataforma captura e armazena instantaneamente as leituras do sensor de combustível de Dispositivos conectados. Os dados são salvos somente após a criação de um sensor de combustível dentro do sistema.

Filtros para valores mínimos e máximos, tabelas de calibração e outras configurações do sensor são aplicados durante a saída dos dados. Como resultado, você tem a liberdade de modificar as configurações a qualquer momento e reconstruir os Relatórios para observar o impacto nos dados salvos. Essa flexibilidade de configuração garante que seus dados estejam sempre sincronizados com as configurações mais recentes, mantendo-os sempre atualizados.


---

# 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/pt-br/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.