> 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/rebel-series/rebel-series/rebel-lt-and-ct-user-documentation/the-rebel-ct-data-logger.md).

# The Rebel CT Data Logger

<figure><img src="https://888960721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FenX58y5hTu5O8sufLoOA%2Fuploads%2FquJPx4BfLvdZmzXOHgCV%2Fimage.png?alt=media&amp;token=7ce7c146-9c53-4956-82fb-eefdeba09346" alt=""><figcaption><p>Rebel CT</p></figcaption></figure>

* Up to 7x CAN 2.0 buses
* Up to 2x CAN FD buses
* Up to 3x LIN buses
* Up to 2x FlexRay channels
* 3x digital I/O
* 4x analog input (each channel can be calibrated independently)
* 18Hz GNSS with 1KHz xyz Accelerometer
* Supports protocols CCP, XCPOnCAN and XCPOnFlexRay, UDS (ISO14229), J1939, CAN FD (ISO Standard or Non-ISO Standard)\*
* SDXC card data storage (up to 128GB)
* Galvanic isolation (USB, enclosure)
* IP65 dust and splash-proof cover– SD card securely housed behind a flip panel
* Low power consumption in sleep mode and WakeOnCAN or WakeOnSignal feature

#### Options:

* Internal GNSS module (up to 30Hz refresh rate, socket for external antenna)
* Internal 3D 1kHz accelerometer and 3D Gyro module
* Internal 4G LTE CAT 1 module
* Internal Wi-Fi module
* Larger capacity data storage SDXC cards available (up to 128GByte)
* Dialog Standard is required for data analysis/live data
* Dialog Plus is required for XCP/CCP or to connect to StreamLog
* Dialog Gateway for configuring CAN 2.0 gateway functions
* Extension cable to connect CAN 0/PWR to vehicle OBD Port (9-way D-Sub to OBD)

  &#x20;


---

# 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/rebel-series/rebel-series/rebel-lt-and-ct-user-documentation/the-rebel-ct-data-logger.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.