Tools

The bimmerz suite is split across eight projects. Each one tackles a specific slice of what BMW's factory toolchain does — diagnostics, coding, documentation, or bus communication.

Diagnostic & coding

Tool	What it's for
EDIABASX	Read fault codes and run diagnostic jobs against your ECUs.
INPAX	Run BMW's diagnostic scripts — live data, ECU configuration, and the built-in diagnostic procedures.
NCSX	Read and write ECU coding. Tick boxes for the options you want; no hex required.
NFSX	Flash ECU firmware from the CLI — IPO-driven, direct DS2, or C167 bootmode.
TUNEX	Edit ECU firmware in the browser — hex view + structured editor via TunerPro .xdf definitions.

Bus & ECU

Tool	What it's for
XBUSX	Watch and interact with the I-Bus / K-Bus comfort messages — IKE, lights, radio, doors, steering wheel.

Aftersales support

Tool	What it's for
TISX	Read repair procedures and technical bulletins (BMW's Technical Information System, in a modern browser).
ETKX	Look up any part — diagrams, numbers, supersession history.
WDSX	Read wiring diagrams. Trace a circuit, follow pin numbers, find connectors.

Web app vs self-hosted

The diagnostic, coding, and bus tools — EDIABASX, INPAX, NCSX, TUNEX, and XBUSX — run as live web apps. They read the BMW data they need from your own disk via the browser's File System Access API and reach the cable through Web Serial; nothing is uploaded.

NFSX is a Node.js CLI tool. It uses ediabasx for the transport layer (IPO-driven and directmode paths); bootmode talks to the serial port directly.

The aftersales-support tools — TISX, ETKX, and WDSX — need a one-time data-import or migration step that's too heavy for the browser to do alone (InstallShield archives, Transbase migrations, RTF decompression). Those are self-hosted: clone the repo, run the importer, then serve the viewer locally.