> 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/quick-start-guide/configure-rebel-data-logger-to-record-raw-can-messages/record-raw-can-bus-data.md).
# Record Raw CAN Bus data
Begin creating a configuration by clicking the 'New Configuration' tab under the 'Configuration' tab.
Name the configuration and then click 'OK'.
While performing this step, check the sleep mode settings to avoid battery drain.
* Use the drop-down menu to select the required mode.
* Ensure that the 'Limit Module Wakeup' is not enabled, and then select 'OK'.
Select the 'New Bus' tab.
Select CAN 0 (HS), and select 'OK'.
Select the drop-down CAN /bus speed menu, allocate the correct bus speed that matches your CAN network requirement, and then select 'OK'.
Click on 'New Protocol'.
Select 'CAN Monitor' from the displayed choices, and click 'OK'.
Enable the check box before 'Log All Channels' to enable full CAN log trace, and click 'OK'.
The configuration has been successfully made.
---
# 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/quick-start-guide/configure-rebel-data-logger-to-record-raw-can-messages/record-raw-can-bus-data.md?ask=&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.
