Two CAN FD channels, a LIN bus and four configurable inputs at 164 g. The optional IMU variant adds motion and GPS position, so you capture what the vehicle did and where it did it.
Trigger on a CAN signal, CAN ID, J1939 DM1 counter or digital input, with pre-trigger capture.
Open API. Open-source REXLIBRARY toolkit, a device API library, and free RXD conversion utilities.
Set up logging, filtering, triggering, signal decoding. Supports CAN, CAN FD, LIN, J1939, UDS/CCP, DBC files, sensor channels and non-standard CAN bit rates.
Use REXGEN 2 as a pass-through USB device to connect CAN networks to compatible software tools. Supports J2534 workflows and third-party tools such as SavvyCAN.
CAN error logging. Error frames recorded on the same timeline as the data.
Seed and key encryption, set up through the Encryption Manager in REXDESK, keeps log files unreadable without the key.
Full specifications, including storage, inputs, real-time clock, USB and IP65, in the spec sheet below.
Connector options
REXGEN 2 is provided with a 9 Way D-Sub as standard or can be requested as a Deutsch connector or free-wired for your custom configurations. If you are looking for a specific custom config for a volume order get in touch for a quote.
Vibration and CAN, correlated automatically into a custom diagnostic tool.
By installing the REXGEN we were able to log simultaneously the vibrations of the ship with the internal accelerometer and the CAN bus. By connecting the datalogger to our diagnostic computer and leveraging the open REXLIBRARY of Influx Technology, we were able to make a custom diagnostic tool that automatically finds the diagnostic fault messages on the CAN bus and correlates it with the accelerometer data. Furthermore the data is exported to a time related database and visualized for easy interpretation by our engineers and the customer.
Preconfigured setups
Our preconfigured bundles are the quickest way to get going.
DurabilityTwo CAN FD buses plus temperature from K-TC, all on one synchronised timeline.
Fleet loggingConfigure once, deploy the same black-box build across every vehicle.
Battery & powertrainTemperature, voltage and PWM together with K-BOX, recorded over CAN.
Whether you need a single CAN bus data logger for bench testing or a fleet-scale deployment with cloud connectivity, our engineering team can help you find the right approach.
Documentation
Step by step guides on the Influx Technology docs, from first connection to pinouts and the full manual.
Getting started
Learn the basics of your device, connect the signals and create your first log.
Pinout details
Connector pinouts for REXGEN 2 and the IMU variant.
Product manual
The complete REXGEN 2 and IMU manual and reference.
Configure with REXDESK
Set up the logger and export your data with the free software.
Specifications
Sourced from the REXGEN 2 technical documentation.
Download spec sheet ↓Frequently asked questions
The IMU variant adds 6-axis inertial sensing and GNSS, plus more storage, 16 GB versus 8 or 16 GB on the standard REXGEN 2. Everything else is shared.
Yes. Both variants run two CAN / CAN FD channels up to 8 Mbit/s, plus a LIN channel.
No. It logs to soldered eMMC, so there is no card to lose or corrupt.
No. It is 100% power safe. Files are not corrupted on disconnect or in sleep.
Yes. Two analogue and two digital inputs at up to 1 kHz.
Yes. Fitted to a vehicle and left running, REXGEN 2 records CAN FD, LIN and sensor data to its own soldered eMMC, so it works as a black box data logger for unattended event and fleet logging. You pull the data when the vehicle returns.
Yes. Triggers can be set on CAN signals or the IMU variant's motion channels, and motion, position and bus data share one timeline, so an impact can be reconstructed after the event. Files are power safe, so the record survives even if power is lost at the moment of impact.
