Import your Pi Research PDS files

Prerequisites

• Compatible loggers: Pi Sigma, Pi Delta, Pi Omega, Cosworth ICD, ICD-Lite, Pi Research systems
• Format: .pds (Pi Data Series — native logger binary format)
• No software required: no need for Pi Toolbox Pro

Context

The PDS format is the native binary format recorded directly by Pi Research / Cosworth loggers. Unlike the MAT export which requires Pi Toolbox Pro (paid subscription), the PDS file can be imported directly into Brake Point without any conversion.

Experimental status: this provider has been validated on ICD-Lite / Porsche GT4 RS Clubsport data. If you encounter issues with a different logger or vehicle type, contact us.

Step 1 — Get the PDS file from your logger

1. Connect your Pi Research logger to your computer
2. Access the logger’s memory card (or use the download software)
3. Locate the .pds file for the desired session
4. Copy it to your computer

Tip: PDS files are typically named with a numeric identifier (e.g. Unknown-001.002.001.pds).

Step 2 — Import into Brake Point

1. Log in to app.brakepoint.io
2. Click Import a session
3. Select your .pds file (or a .zip containing the .pds file)
4. Brake Point decodes the native binary format and extracts data automatically

Extracted data

The PDS provider automatically extracts data using content-based detection:

Reliable data

Data	Source	Accuracy
GPS position (lat/lon)	Logger	Exact
GPS speed	Logger	Exact
GPS altitude	Logger	Exact
ECU speed	Logger	~99% vs MAT
Engine RPM	Logger	~98% vs MAT
Throttle (%)	Derived by Brake Point	~95% vs MAT
Braking (%)	Derived from deceleration	~98% vs MAT
Vehicle name	Metadata	When available
Track name	Metadata	When available

Note on braking: the PDS file does not contain a usable brake pressure channel. Brake Point derives braking percentage from longitudinal deceleration, which accurately captures braking phases (98% correlation with MAT data).

Partial data

Data	Status
Lateral / longitudinal acceleration	Detected, but axes may be swapped depending on the session
Lap splitting	Works on ~50% of sessions — otherwise, GPS-based S/F line splitting takes over

Why? The mapping between channel names and actual data depends on the CAN configuration set up by the user or the engineer who installed the logger. Since every installation is different, the same channel names can carry different data. Brake Point uses content-based detection (value ranges, sample rates, correlations) rather than channel names.

Tip: ask your engineer or technician to configure the logger following the channel mapping below to ensure optimal data detection by Brake Point.

Supported PDS channels

Stable channels (same across all tested sessions):

ch_id	Data	Conversion
502	GPS Latitude	Radians → degrees, CAN filtering
532	GPS Longitude	Radians → degrees, CAN filtering
213	Engine RPM	rad/s → RPM (×9.549)

Content-detected channels (vary per session):

Data	Observed ch_ids
ECU speed	199, 168, 721, 112
GPS speed	281, 305, 304, 119
GPS altitude	185, 151, 152
Acceleration	718, 712
Lap counter	224

Not mapped: throttle (derived), braking (derived), gear ratio (not available).

Data not available

• Gear ratio: not available. In MAT, this data is only available with compatible telemetry hardware.

PDS vs MAT — Which one to choose?

	PDS (native)	MAT (export)
Software required	None	Pi Toolbox Pro (paid)
Ease of use	Copy file from logger	Manual channel-by-channel export
Brake data	Derived from deceleration (~98%)	Direct channel
Throttle	Derived (~95%)	Direct channel
Acceleration	Detected (axes sometimes swapped)	Exact
Laps	~50% of sessions	Complete
Gear ratio	Not available	Available (compatible hardware only)
Status	Experimental	Supported
Recommended	If no Pi Toolbox Pro	For all data

Our recommendation: the PDS file is the simplest solution — no additional software needed. If you need reliable acceleration, complete lap splitting, or gear ratio, use the MAT export.