> 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/can-and-obdii.md).

# CAN e OBDII

Dispositivos GPS leem dados do motor e códigos de falha por meio do barramento CAN e OBD-II. Abrange decodificação de DTC, protocolos de comunicação e fundamentos de dispositivos OBD.

Esta seção explica como os dispositivos GPS se comunicam com a eletrônica do veículo por meio das interfaces CAN bus e OBD-II, cobrindo o panorama de protocolos, os dispositivos OBD plug-and-play e como ler e interpretar códigos de falha de diagnóstico.

## Conteúdo

* [Comunicação intra-veicular: CAN, FlexRay e MOST](/docs/expert-center/pt-br/vehicle-telematics-technology/can-and-obdii/intra-vehicle-communication-can-flexray-and-most.md): Como as ECUs trocam dados por meio de diferentes protocolos de rede veicular.
* [Fundamentos dos dispositivos OBD](/docs/expert-center/pt-br/vehicle-telematics-technology/can-and-obdii/obd-tracker-fundamentals.md): Como os dispositivos OBD plug-and-play se conectam à porta de diagnóstico e quais dados eles expõem.
* [DTC (Códigos de falha de diagnóstico)](/docs/expert-center/pt-br/vehicle-telematics-technology/can-and-obdii/dtc-diagnostic-trouble-codes.md): Como decodificar estruturas de códigos de falha, interpretar categorias de erro e agir com base nos dados de diagnóstico.


---

# 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/can-and-obdii.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.