Import your I2M Chrome files (.dat)
How to import a native .dat file from an I2M Chrome Lite, Plus 2, Pro 2 or DataLog Pro into Brake Point.
Updated on February 23, 2026
Prerequisites
- Compatible device: I2M Chrome Lite, Chrome Plus 2, Chrome Pro 2, DataLog Pro
- Software: I2M DaS (Data Analysis Software) — to download data from the device
- File format:
.dat(I2M native text format)
Experimental status: this provider has been validated on Chrome Lite and Chrome Plus 2 data (motorcycle). If you encounter issues with a different device or vehicle, contact us.
Step 1 — Download data from the I2M device
- Turn on your I2M Chrome device
- Connect it to your computer:
- WiFi: join the network created by the device (Chrome Plus 2, Pro 2)
- USB: micro-USB cable (Chrome Lite, DataLog Pro)
- Open I2M DaS and download the desired session
- The
.datfile is automatically saved to your computer
Tip: the
.datfile contains all raw session data (GPS, analog sensors, RPM). There is no export step required — this is the device’s native format.
Step 2 — Import into Brake Point
- Log in to app.brakepoint.io
- Click Import a session
- Select your
.datfile (or a.zipcontaining the.datfile) - Brake Point automatically detects the I2M format and starts the analysis
Extracted data
Reliable data
| Data | Source | Frequency |
|---|---|---|
| GPS position (lat/lon) | 10 Hz GPS | 10 Hz |
| GPS speed | GPS | 10 Hz |
| Engine RPM | RPM sensor | 100 Hz |
| Throttle (%) | Analog input (TPS) | 100 Hz |
| Brake (%) | Analog input | 100 Hz |
| Lean angle (motorcycle) | GPS-derived | 10 Hz |
| Rider name | Metadata | — |
| Session date | Metadata | — |
Unique feature: GPS-derived lean angle
I2M Chrome devices have no Inertial Measurement Unit (IMU). Brake Point computes the lean angle from the GPS trajectory and speed, using the cornering equilibrium equation:
lean = atan(v² / (R × g))
where v is the speed, R the turn radius and g the gravitational acceleration. The result is smoothed (0.5 s moving average) and clamped to ±65°. Typical accuracy: ±3-5° compared to an IMU.
Data not available
- Gear: not available in the
.datfile (gear ratio calculation is planned for a future version) - Suspension: analog suspension inputs (fork, shock) are detected but not yet processed
Analog channel configuration
The I2M Chrome device has 8 analog inputs. Brake Point automatically detects throttle (TPS) and brake channels by their name in the device settings ($SETTINGS).
Automatically recognized names:
| Function | Recognized names |
|---|---|
| Throttle | TPS, Throttle, Gas, Acceleratore |
| Brake | Freno, Brake, Front Brake, Frein |
Tip: if your throttle or brake data doesn’t show up, check the channel name in your I2M DaS device settings. The name must match one of the names listed above.
Lap detection
The .dat file does not contain lap markers. Laps are automatically split by GPS start/finish line detection using the circuit coordinates in the Brake Point database.
Compatible I2M devices
| Device | GPS | Analog | CAN | WiFi |
|---|---|---|---|---|
| Chrome Lite | 10 Hz | 8 | No | No |
| Chrome Plus 2 | 10 Hz | 8 | Yes | Yes |
| Chrome Pro 2 | 10 Hz | 8 | Yes | Yes |
| DataLog Pro | 10 Hz | 8 | No | No |
Tips
- Frequency: GPS runs at 10 Hz and analog sensors at 100 Hz. Brake Point resamples traces to 10 Hz for display.
- Multiple sessions: a
.datfile can contain multiple sessions (marked by$NEW SESSION). Brake Point imports the session with the most data. - If lean angle seems incorrect at low speed (< 30 km/h), this is normal — GPS-based calculation is unreliable below that speed.
Don't miss new format support
Get notified when we add support for new telemetry formats.