TurboLamik TunerPro File Types

There are 3 main file types which are key to understand if setting up a TurboLamik TCU. BIN File, XDF File and ADX File

What is a BIN File?

A TunerPro BIN file is a binary file that contains the actual data (calibration/tune) used by a vehicle’s ECU (Engine Control Unit). It is the file that tuners edit using TunerPro to change how the engine or transmission behaves.

In detail, a BIN file:

• Contains raw hex values that define parameters like:

  • shift maps

  • coverter lockup

  • minimum rpm points

  • maximum rpm point

  • torque calculation

  • input calibration

 

• Is interpreted using an XDF file in TunerPro, which gives structure and labels to the raw data.

What is a XDF file?

An XDF file in TunerPro defines the structure of a binary (BIN) file for tuning vehicle ECUs (Engine Control Units). It tells TunerPro how to interpret and modify specific addresses and values in the BIN file, which are otherwise just raw hex data.

Specifically, an XDF file does the following:

1. Defines parameters: It maps human-readable names (like "Fuel Map", "Ignition Timing", or "Rev Limit") to specific memory addresses in the BIN file.

2. Specifies data formats: It tells TunerPro how to interpret the data — whether it's a single value, a 2D table (map), a 3D map, a flag, etc.

3. Adds scaling and units: For example, a raw value of 50 in the BIN might represent 5.0 ms of injector pulse width. The XDF applies that scaling.

4. Groups and organizes data: It makes tuning more user-friendly by grouping similar parameters and adding helpful descriptions.

Without an XDF:

The BIN file would just appear as a long list of hex numbers — impossible to tune unless you already know the structure by heart.

 

What is a ADX File?

A TunerPro ADX file is used to define how real-time data is communicated between TunerPro and a vehicle’s ECU (Engine Control Unit) via a data logging or tuning interface.

In short, an ADX (Acquisition Definition Exchange) file:

• Defines how to connect to the ECU: baud rate, data stream format, commands to initiate logging, etc.

• Specifies what data to log: engine RPM, throttle position, coolant temp, AFR, boost, etc.

• Tells TunerPro how to interpret the incoming data: which bytes mean what, and how to scale/convert them into readable values with proper units.

• Supports dashboards and gauges: by mapping variables to visual instruments in the interface.

Key Differences from XDF:

• XDF = Editing the tune (static memory layout).

• ADX = Viewing live data from the ECU (dynamic data stream).

Summary:

• BIN = the actual tune (raw data).

• XDF = the map that explains the BIN layout.

• ADX = the setup for logging live data from the ECU.