> 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/obd-data-acquisition.md).

# Akuisisi data OBD

Konfigurasikan blok pengambilan data OBD di Navixy untuk mengaktifkan laporan PID pada perangkat OBD dan menetapkan interval pengumpulan serta ukuran batch unggahan.

Mengontrol bagaimana perangkat OBD mengumpulkan dan mengunggah data diagnostik PID (Parameter ID) dari port OBD-II kendaraan. Data PID mencakup diagnostik mesin standar seperti RPM, kecepatan kendaraan, suhu cairan pendingin, dan level bahan bakar, parameter yang tidak ditransmisikan melalui GPS, tetapi tersedia melalui bus CAN kendaraan.

## Pengaturan

* **Aktifkan laporan PID**: aktifkan atau nonaktifkan pengumpulan data OBD.
* **Interval pengumpulan data PID**: seberapa sering perangkat mengambil sampel pembacaan PID baru (misalnya, setiap 10 detik). Interval yang lebih pendek memberikan data yang lebih terperinci, tetapi meningkatkan konsumsi data.
* **Jumlah catatan unggahan**: berapa banyak catatan yang dikumpulkan perangkat sebelum mengirimkan satu kumpulan ke platform Navixy. Misalnya, nilai 10 dengan interval 10 detik berarti data diunggah kira-kira setiap 100 detik.

## Ketersediaan

Muncul pada model perangkat OBD yang mendukung pengambilan data PID.

## Lihat juga

* [Deteksi status mesin](/docs/user/id/guide/devices-and-settings/device-specific-controls/engine-and-diagnostics/engine-state-detection.md): konfigurasikan deteksi hidup/mati mesin berbasis tegangan pada keluarga perangkat yang sama.


---

# 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/obd-data-acquisition.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.