> 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/es/vehicle-telematics-technology/can-and-obdii.md).

# CAN y OBDII

Los dispositivos GPS leen datos del motor y códigos de falla a través del bus CAN y OBD-II. Cubre la decodificación de DTC, los protocolos de comunicación y los fundamentos de los dispositivos OBD.

Esta sección explica cómo los dispositivos GPS se comunican con la electrónica del vehículo a través de interfaces CAN bus y OBD-II, y cubre el panorama de protocolos, los dispositivos OBD plug-and-play y cómo leer e interpretar los códigos de falla de diagnóstico.

## Contenido

* [Comunicación intravehicular: CAN, FlexRay y MOST](/docs/expert-center/es/vehicle-telematics-technology/can-and-obdii/intra-vehicle-communication-can-flexray-and-most.md): Cómo intercambian datos las ECU a través de distintos protocolos de red del vehículo.
* [Fundamentos de los dispositivos OBD](/docs/expert-center/es/vehicle-telematics-technology/can-and-obdii/obd-tracker-fundamentals.md): Cómo los dispositivos OBD plug-and-play se conectan al puerto de diagnóstico y qué datos exponen.
* [DTC (códigos de falla de diagnóstico)](/docs/expert-center/es/vehicle-telematics-technology/can-and-obdii/dtc-diagnostic-trouble-codes.md): Cómo decodificar las estructuras de los códigos de falla, interpretar las categorías de error y actuar según los datos 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/es/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.