> 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/device-specific-controls/engine-and-diagnostics/obd-data-acquisition.md).

# OBD data acquisition

Configure the OBD data acquisition block in Navixy to enable PID reports on an OBD device and set the collection interval and upload batch size.

Controls how an OBD device collects and uploads PID (Parameter ID) diagnostic data from the vehicle's OBD-II port. PID data includes standard engine diagnostics such as RPM, vehicle speed, coolant temperature, and fuel level, parameters not transmitted over GPS, but available through the vehicle's CAN bus.

## Settings

* **Enable PID reports**: turn OBD data collection on or off.
* **PID data collection interval**: how often the device samples a new PID reading (for example, every 10 seconds). Shorter intervals give more granular data but increase data consumption.
* **Upload records count**: how many records the device accumulates before sending a batch to the Navixy platform. For example, a value of 10 with a 10-second interval means data uploads roughly every 100 seconds.

## Availability

Appears on OBD device models that support PID data acquisition.

## See also

* [Engine state detection](/docs/user/guide/devices-and-settings/device-specific-controls/engine-and-diagnostics/engine-state-detection.md): configure voltage-based engine on/off detection on the same device family.


---

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