> For the complete documentation index, see [llms.txt](https://docs.influxtechnology.com/support_guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.influxtechnology.com/support_guides/dialog-user-guide/appendix-2/can-modes.md).

# CAN Modes

<table data-header-hidden><thead><tr><th width="137"></th><th></th></tr></thead><tbody><tr><td>01</td><td>Current Powertrain Diagnostic Data</td></tr><tr><td>02</td><td>Powertrain Freeze Frame Data</td></tr><tr><td>03</td><td>Emissions-Related Powertrain Diagnostic Trouble Codes</td></tr><tr><td>04</td><td>Clear/Reset Emissions Related Diagnostic Information</td></tr><tr><td>06</td><td>On-Board Monitoring Test Results for Non-Continuously Monitored Systems</td></tr><tr><td>07</td><td>On-Board Monitoring Test Results for Continuously Monitored Data</td></tr><tr><td>09</td><td>Request Vehicle Information</td></tr><tr><td>0A</td><td>Permanent Status Diagnostic Trouble Codes</td></tr><tr><td>10</td><td>Diagnostic Session Control Service</td></tr><tr><td>11</td><td>ECU Reset</td></tr><tr><td>14</td><td>Clear Diagnostic Information</td></tr><tr><td>19</td><td>Read Diagnostic Trouble Codes</td></tr><tr><td>22</td><td>Read Data by Identifier</td></tr><tr><td>23</td><td>Read Memory by Address</td></tr><tr><td>2C</td><td>Dynamically Define by Data Identifier</td></tr><tr><td>2E</td><td>Write Data by Identifier</td></tr><tr><td>31</td><td>Routine Control</td></tr><tr><td>3E</td><td>Tester Present</td></tr><tr><td>27</td><td>Security Access Service</td></tr><tr><td>2A</td><td>Read Data by Periodic Identifier</td></tr></tbody></table>


---

# 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://docs.influxtechnology.com/support_guides/dialog-user-guide/appendix-2/can-modes.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.