> 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/id/guide/devices-and-settings/device-specific-controls/engine-and-diagnostics/fuel-consumption-calculation.md).

# Perhitungan Konsumsi bahan bakar

Konfigurasikan blok perhitungan Konsumsi bahan bakar di sisi perangkat di Navixy dengan menetapkan jenis bahan bakar, kapasitas mesin, dan pengali untuk perkiraan.

Menetapkan parameter yang digunakan perangkat untuk menghitung Konsumsi bahan bakar sendiri. Ini terpisah dari sisi platform [sensor bahan bakar](/docs/user/id/guide/devices-and-settings/vehicle-sensors/measurement-sensors.md).

## Pengaturan

* **Jenis bahan bakar**: bensin, diesel, atau LPG. Mempengaruhi laju bahan bakar bawaan yang digunakan perangkat untuk memperkirakan konsumsi.
* **Volume mesin**: kapasitas mesin dalam liter (misalnya, 2,0 untuk mesin 2 liter).
* **Pengali**: faktor koreksi yang diterapkan pada hasil estimasi. Gunakan 1,0 jika tidak ada koreksi. Atur di bawah 1,0 jika perangkat mengestimasi konsumsi terlalu tinggi, atau di atas 1,0 jika perangkat mengestimasi terlalu rendah.

## Ketersediaan

Muncul pada model perangkat yang menghitung konsumsi bahan bakar di sisi perangkat.

## Lihat juga

* [sensor bahan bakar](/docs/user/id/guide/devices-and-settings/vehicle-sensors/measurement-sensors/fuel-level-sensor.md): pemantauan bahan bakar di sisi platform dengan kalibrasi.


---

# 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/id/guide/devices-and-settings/device-specific-controls/engine-and-diagnostics/fuel-consumption-calculation.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.