> 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/vehicle-telematics-technology.md).

# Vehicle telematics technology

CAN/OBD protocols, MQTT connectivity, fuel management, device certification, positioning techniques, vehicle sensors, and video telematics guides.

This section covers the hardware, protocols, and methods that underpin modern fleet telematics, from in-vehicle communication buses and positioning alternatives to fuel monitoring, video integration, and device certification.

## Contents

* [CAN and OBDII](/docs/expert-center/vehicle-telematics-technology/can-and-obdii.md): In-vehicle communication protocols, OBD device fundamentals, and diagnostic trouble code decoding.
* [Connectivity](/docs/expert-center/vehicle-telematics-technology/connectivity.md): MQTT fundamentals and other connectivity references.
* [Positioning techniques](/docs/expert-center/vehicle-telematics-technology/positioning-techniques.md): Cell-based and Wi-Fi positioning as GPS alternatives.
* [Sustainable fleet management](/docs/expert-center/vehicle-telematics-technology/sustainable-fleet-management.md): EV fleet monitoring, State of Charge tracking, and battery optimization.
* [Vehicle sensors](/docs/expert-center/vehicle-telematics-technology/vehicle-sensors.md): Wireless BLE and UHF sensors for TPMS, temperature, and other fleet data.
* [Fuel management](/docs/expert-center/vehicle-telematics-technology/fuel-management.md): Sensor selection, installation, calibration, and platform-side fuel analysis.
* [Legislation](/docs/expert-center/vehicle-telematics-technology/legislation.md): GPS device certification requirements by region.
* [Video telematics](/docs/expert-center/vehicle-telematics-technology/video-telematics.md): Dashcam integration, driver safety monitoring, and device configuration guides.


---

# 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/vehicle-telematics-technology.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.