BNU.toBinDrive
Open archive
Non-commercial ECU file archive

One archive. Many files, stages and sources.

BinDrive indexes ECU files attributed in their accompanying names or metadata to independent tuning studios and working collections. Search ORI, modified, staged and option-specific files with the available technical context shown for each entry.

Open archive How it works

An archive for finding, comparing and researching files. No storefront or file sales.

01 / CATALOGUE Start with the two main collections. Public Firmware and Trust Firmware in the current Drive.
Current BinDrive catalogue showing Public Firmware and Trust Firmware folders
Archive
ORI / STOCK STAGE 1 STAGE 2 OPTIONS FULL READ BIN / HEX OLS A2L / DCM
Archive coverage

Manufacturers represented in the archive.

A selection drawn from current archive metadata, spanning passenger vehicles, trucks, agriculture and construction equipment. Coverage varies by model, ECU, hardware and software version.

BMW Passenger
Audi Passenger
Ford Passenger
Renault Passenger
Škoda Passenger
Citroën Passenger
Fiat Passenger
Nissan Passenger
Kia Passenger
Mazda Passenger
Jeep Passenger
Chevrolet Passenger
Suzuki Passenger
Chrysler Passenger
Iveco Truck
Scania Truck
John Deere Agriculture
Caterpillar Construction
Volkswagen Passenger
Peugeot Passenger
Opel Passenger
Volvo Passenger
SEAT Passenger
Porsche Passenger
MINI Passenger
Hyundai Passenger
Toyota Passenger
Honda Passenger
Mitsubishi Passenger
Dacia Passenger
Smart Passenger
Subaru Passenger
MAN Truck
DAF Truck
JCB Construction
Hitachi Construction

Vehicle names and marks belong to their respective owners and are used only to identify archive metadata. No affiliation or endorsement is implied.

Open the full manufacturer index
Inside the archive

Different origins. Different stages. One clear index.

The collection is intentionally broad: files labelled as original, full read, modified, staged or option-specific, plus supporting calibration material attributed to many independent sources.

01

Originals and full reads

Files labelled ORI, stock or full read are kept distinct from modified material where the available metadata permits.

02

Stages and options

Stage-labelled and option-specific files organised by the information supplied with them.

03

Independent sources

Files attributed to different tuning studios, contributors and working collections, with source context where available.

04

Projects and definitions

BIN, HEX, OLS, A2L, DCM and related files kept close to their technical metadata.

NOTE Studio names and source labels are reproduced as archive metadata. BNU.to does not claim authorship, affiliation, endorsement or independent verification; third-party rights remain with their respective owners.

File content

Option labels found across the archive.

Uploaded firmware may include one or several calibration options. Availability and naming depend on the metadata supplied with each source.

Common file labels
ORI STAGE 1 STAGE 2 ECO BURBLES LAUNCH CONTROL

ADBLUE / SCR

Exhaust aftertreatment

DPF

Diesel particulate filter

EGR

Gas recirculation

DTC

Diagnostic codes

GPF / OPF

Gasoline particulate filter

LAMBDA / O2

Oxygen sensor

EVAP

Vapour system

SWIRL FLAPS

Intake control

START / STOP

Driveability

SPEED LIMITER

Vehicle speed

TORQUE MONITORING

Torque model

HOT START

Starting strategy

Descriptive labels reproduced from independent source metadata. Inclusion does not imply verification, endorsement, compatibility or legal suitability.

Archive contents

Firmware, projects and definitions in one index.

The archive keeps firmware, projects, definitions and grouped packages legible without pretending that an extension alone tells the whole story.

Always inspect the contents and identifiers. A filename, extension or folder name does not establish provenance or compatibility.

01 ORI / STOCK Reference

Files presented as original or factory references.

02 STAGE / OPTIONS Modified

Staged projects and option-specific variants as labelled by their source.

03 BIN / HEX Firmware

Raw binary or hexadecimal firmware and calibration data.

04 OLS Project

WinOLS projects and related working references.

05 A2L / DCM Definition

Measurement descriptions and structured calibration data.

06 FULL READ ECU read

Files labelled as full ECU reads, retained for technical reference and comparison.

07 ARCHIVES Package

Grouped files, projects and notes kept together when useful.

A practical workflow

Search first. Validate before use.

  1. 01

    Search

    Begin with an ECU, HW or SW identifier; then narrow the results by vehicle, filename, stage or option labels.

  2. 02

    Review

    Compare the available identifiers, size, format, folder, source and notes.

  3. 03

    Validate

    Check the candidate against your own read and a known-good technical reference.

  4. 04

    Use responsibly

    Download or share only where you have permission and a lawful purpose.

Before you use a file

The archive provides context. You make the final check.

BinDrive is a library, not a substitute for professional verification. Confirm ownership and permission, retain an original backup, match the exact ECU, HW and SW identifiers, and follow applicable emissions, road-safety and local legal requirements.

Plain answers

About BNU.to and BinDrive

What is BNU.to?

BNU.to is the home of BinDrive, a cloud library and archive for ECU firmware, calibration files, projects and related metadata.

Is BNU.to a tuning-file shop?

No. BinDrive is a non-commercial file archive and cloud workspace, not a marketplace or tuning-file store.

Where do the files come from?

The archive contains files attributed to independent tuning studios, contributors and working collections. Attribution is reproduced from available file or source metadata and may be incomplete; inclusion does not imply affiliation, endorsement or verification.

What can I search by?

Search by filename, folder path, ECU family, HW or SW number, vehicle, engine and format. Search stage or option terms where they appear in filenames, folders or metadata.

Does an ORI or stage label guarantee a file?

No. Labels describe how a file is organised in the archive. Validate the contents and identifiers, verify file integrity, and compare the available source information with a known-good reference before use.

Can I write an archived file directly to an ECU?

Do not assume any archived file is ready for direct use. First verify the exact ECU, hardware, software, vehicle, file integrity and intended purpose.

Who is responsible for legal use?

Users are responsible for ownership rights, permission, emissions compliance, road safety and all laws that apply in their jurisdiction.

Start with what you know

Start with an ECU, HW or SW number.

Open the archive, search the index and inspect the available context before you download.

Open archive Sign in