# Technical Specifications

<table data-full-width="true"><thead><tr><th width="218">Functions</th><th width="595">ReXgen 1</th></tr></thead><tbody><tr><td><strong>CAN Interfaces</strong></td><td><p>1 x CAN </p><p>ISO 11898-1: Compliant with CAN (up to 1 Mbit/s)</p><p>Conforms to CAN protocol version 2.0 - part A, B Max 20000 MPs</p><p>Meets the requirements of ISO 11898-2:2016 &#x26; ISO 11898-5:2007 physical  layer standards</p></td></tr><tr><td><strong>Identifiers</strong></td><td>Compliant with CAN specifications 2.0A (11-Bit ID) and 2.0B (29-Bit ID)</td></tr><tr><td><strong>CAN Error Frames</strong></td><td>Support for logging CAN error frames (bit-stuffing, form, CRC, bit, acknowledgement)</td></tr><tr><td><strong>Retransmission</strong></td><td>Configurable retransmission of frames that have lost arbitration or been disturbed by errors</td></tr><tr><td><strong>Prescaling</strong></td><td>Pre-scale CAN frames to record e.g., by time (per X ms) or by data (e.g., if byte X or Y changes)</td></tr><tr><td><strong>Transmit</strong></td><td>Transmit lists of CAN frames per channel (periodic) - e.g., for OBD2 requests- Capability to link multiple CAN messages</td></tr><tr><td><strong>PC Interfaces</strong></td><td>Rugged Micro USB 2.0 (Datalogger mode and J2534)</td></tr><tr><td><strong>J2534</strong></td><td>Yes/Pass-Thru Enabled</td></tr><tr><td><strong>Data Storage Capability</strong></td><td>8 GB Inbuilt eMMC storage (uses FIFO logic once the eMMC is full)</td></tr><tr><td><strong>Supported Protocols</strong></td><td>CAN Monitoring (RAW CAN signals, SAE J1939 support)</td></tr><tr><td><strong>Identifiers</strong></td><td>Compliant with CAN specifications 2.0A (11-Bit ID) and 2.0B (29-Bit ID)</td></tr><tr><td><strong>Bit-Rate Auto-Detect</strong></td><td>Bit rate can be auto-detected or set manually</td></tr><tr><td><strong>Real-Time Clock</strong></td><td>Sync RTC using CAN Message and ReXdesk Software</td></tr><tr><td><strong>File Split</strong></td><td>Configurable log file split size (by size: 10-512 MB and/or by time period)</td></tr><tr><td><strong>Unique Device ID</strong></td><td>Each device has a globally unique ID ensuring unique log file naming</td></tr><tr><td><strong>Signed Firmware</strong></td><td>Firmware updates are digitally signed to verify that they are from a trusted source</td></tr><tr><td><strong>Cyclic Logging</strong></td><td>Enabled by default</td></tr><tr><td><strong>LEDs</strong></td><td>1</td></tr><tr><td><strong>Triggering</strong></td><td>Trigger on a CAN ID, Trigger on Parameter Value, and Trigger on DM1 counter.</td></tr><tr><td><strong>Filters</strong></td><td> 200* regular/extended ID filters per channel (range, acceptance)</td></tr><tr><td><strong>Data Storage format</strong></td><td>FAT32, Log files accessible via ReXdesk software</td></tr><tr><td><strong>File Format Supported</strong></td><td>ASAM MDF (.mf4), CSV, MATLAB, ASC, BLF, TRC</td></tr><tr><td><strong>Warranty</strong></td><td>12 months from the date of invoice.</td></tr><tr><td><strong>Support</strong></td><td>Yes, during the warranty period</td></tr><tr><td><strong>Origin</strong></td><td>UK</td></tr><tr><td><strong>Data Logger Configuration</strong></td><td>Supplied with Influx ReXdesk configuration software, XML based</td></tr></tbody></table>

[<mark style="color:blue;">Electrical Data</mark>](/support_guides/rexgen-series-product-manuals/rexgen-1/rexgen-1-product-manual/overview-of-the-device/electrical-data.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.influxtechnology.com/support_guides/rexgen-series-product-manuals/rexgen-1/rexgen-1-product-manual/overview-of-the-device/technical-specifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
