> 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/rexgen-series-product-manuals/rexgen-1/rexgen-1-product-manual/hardware-functions-and-accessories/functions/recording-can-data.md).

# Recording CAN Data

The device can effectively field log data on tests and a bench via the 1xCAN interface. The device supports all standard CAN baud rates. ReXdesk software allows users to configure ReXgen1 with custom baud rates and modify advanced bit timings. ReXdesk also enables the user to configure ReXgen1 with CAN & J1939 filters. All logged data is saved to the secure embedded memory. The user can configure triggers based on CAN IDs, parameter values & J1939 DM1 messages to start or stop logging.

For a step-by-step guide, [<mark style="color:blue;">click</mark>](https://docs.influxtechnology.com/support_guides/rexdesk-configuration-software-s/rexdesk-rexgen-series-configuration-software/rexdesk-manual/quick-start-guide/preparation-of-configuration/can-log-all-configuration).

How to configure REXGEN to [<mark style="color:blue;">record CAN</mark>](https://youtu.be/rkKgPTPYI5s?si=1jf-Wyx51TYuxZso) data.


---

# 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/rexgen-series-product-manuals/rexgen-1/rexgen-1-product-manual/hardware-functions-and-accessories/functions/recording-can-data.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.