> 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/functioning-as-a-passthru-device-using-j2534.md).

# Functioning as a PASSTHRU device using J2534:

ReXgen1 is designed to function as a data logging device and a capable pass-thru device. The communication protocols supported by ReXgen1 as a J2534 tool are; ISO14229, ISO14230, CAN (ISO11898), ISO15765, and J1939.

It allows the users to connect to the vehicle CAN Bus using the PassThru API (Application Program Interface), enabling you to create programs that accomplish your vehicle communication needs. Influx Module Analyser, SavvyCAN and K-Cal Software already support the pass-thru feature.

ReXgen J2534 (passthru) installation step-by-step [<mark style="color:blue;">guide</mark>](https://docs.influxtechnology.com/rexgen-series-product-manuals/rexgen-j2534-guide/rexgen-as-pass-thru).

[<mark style="color:blue;">Video tutorial</mark>](https://youtu.be/GNhZeBD5sqc?si=ExN8Ye6vaulxWHmZ)


---

# 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/functioning-as-a-passthru-device-using-j2534.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.