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

# CAN et OBDII

Les appareils GPS lisent les données moteur et les codes de défaut via le bus CAN et OBD-II. Couvre le décodage des DTC, les protocoles de communication et les principes fondamentaux des appareils OBD.

Cette section explique comment les appareils GPS communiquent avec l’électronique du véhicule via le bus CAN et les interfaces OBD-II, en couvrant le panorama des protocoles, les appareils OBD prêts à l’emploi et la manière de lire et d’interpréter les codes de défaut de diagnostic.

## Table des matières

* [Communication à l’intérieur du véhicule : CAN, FlexRay et MOST](/docs/expert-center/fr/vehicle-telematics-technology/can-and-obdii/intra-vehicle-communication-can-flexray-and-most.md): Comment les ECU échangent des données via différents protocoles de réseau embarqué.
* [Principes fondamentaux des appareils OBD](/docs/expert-center/fr/vehicle-telematics-technology/can-and-obdii/obd-tracker-fundamentals.md): Comment les appareils OBD prêts à l’emploi se connectent au port de diagnostic et quelles données ils exposent.
* [DTC (codes de défaut de diagnostic)](/docs/expert-center/fr/vehicle-telematics-technology/can-and-obdii/dtc-diagnostic-trouble-codes.md): Comment décoder les structures des codes de défaut, interpréter les catégories d’erreurs et agir sur les données de diagnostic.


---

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