Basics
What is Beemuu?
Free, open-source BMW diagnostic tool for Windows. Reads fault memory, live data, runs service functions over K+DCAN (E-series) or ENET/DoIP (F/G-series). The hosted API at api.beemuu.com serves a DTC catalog and a schematic lookup.
Is Beemuu really free?
Yes. GPL-3.0-or-later. No paid Pro tier, no account requirement, no telemetry. Source on GitHub.
Does Beemuu work on my car?
BMW from 2002 onwards. E-series use K+DCAN; F/G-series use ENET/DoIP. Vehicle and ECU coverage varies — check the documentation for your chassis. See the adapters guide.
Is Beemuu affiliated with BMW?
No. Beemuu is an independent, open-source project. Not affiliated with, endorsed by, or sponsored by BMW AG. BMW is a trademark of its respective owner.
What’s the difference between Beemuu and ISTA?
ISTA is BMW’s dealer-level diagnostic tool. Closed-source, requires online activation, expensive subscription. Beemuu is the open-source alternative — covers the most-used diagnostic operations but doesn’t replicate every ISTA feature. See the Beemuu vs ISTA comparison.
Can I use Beemuu for coding?
Yes — for the operations the project supports. Coding operations are write paths and require real-car validation. See the service resets and the project’s contributing guide for the procedure.
Cables & hardware
What cable do I need?
E-series: USB K+DCAN cable based on FTDI. F/G-series: ENET cable. See the adapters guide for what to buy.
Why does my K+DCAN cable time out?
The FTDI latency timer. The default is 16 ms; BMW sequential block reads need 1 ms. Set it in the FTDI driver on Windows and reconnect. See the hardware deep-dive.
Does the $5 AliExpress ENET cable actually work?
Yes. Same wiring as the official BMW cable. Works with Beemuu, E-Sys, ISTA. See the hardware deep-dive and the ENET pinout doc.
Does Beemuu work on Mac or Linux?
The Windows installer is the primary supported platform. The codebase (Tauri 2 + Rust) is portable; community reports of macOS and Linux builds exist but the project doesn’t ship them as release artifacts.
Fault codes & live data
What fault codes does Beemuu know?
444 codes — 220 BMW-specific (4-hex-digit) plus the standard SAE J2012 P/U/B/C codes. See the DTC index and the live lookup.
How do I read fault codes with Beemuu?
Connect, run a vehicle test (or targeted module scan), read the fault list. Beemuu preserves the code, description and freeze frame before you clear anything. See the fault codes guide.
What is a freeze frame?
A snapshot of the engine state at the moment the code triggered. Includes RPM, load, coolant temperature, fuel trim, and other context. See the fault codes guide.
Does Beemuu work with VCDS?
Beemuu reads the same fault codes as VCDS but uses its own TOML knowledge base rather than VCDS’s labels file. The fault-codes themselves are SAE-standardised; the description strings are what differs.
Service functions
What service functions does Beemuu support?
Six: CBS reset, battery registration, steering-angle calibration, DPF regeneration, Valvetronic adaptation, EGS adaptation. All are documented in detail; the routine IDs are currently marked unverified per the project’s service-function audit.
Why are the routine IDs unverified?
BMW service-function identifiers are not published. The project does not have chassis-validated routine IDs for any procedure. The audit moved every ID to verified: false; the UI renders that honestly.
Do I do CBS reset or battery registration first?
Battery registration first if you replaced the battery. CBS reset for the specific service you performed. See the comparison.
Contributing
What is the easiest way to contribute?
Adding a community TOML file (DTC, opinion, profile, freeze schema). Pure data; reviewed in a regular Tier A PR. See the contributing guide.
Do I need to know Rust?
No. Most contributions are TOML data files. Rust PRs are welcome for engine profiles and decoders.
How do I file a verification report?
Use the docs/validation/ harness docs. PR the report; a maintainer reviews and flips the verification label.
Troubleshooting
Beemuu won’t connect to my car.
Check the cable, the latency timer (K+DCAN), the IP assignment (ENET/DoIP), and the car’s ignition state. The K+DCAN guide and the ENET guide walk through the troubleshooting steps.
Beemuu connects but the scan returns no modules.
Confirm ignition is on (engine not running is fine), the cable is fully seated, the COM port is correct, and your car’s chassis is supported. For E-series, double-check the K-line vs D-CAN bridge setting if the cable has one.
Some modules respond, others don’t.
Normal. Equipment varies by chassis and options. A module that times out may not be installed, may be on a different bus, or may be in a low-power state. Cross-check with another known-good tool before drawing conclusions.
Reads are slow or incomplete.
Verify the FTDI latency timer (1 ms for K+DCAN). Avoid USB hubs. If using ENET/DoIP, verify the laptop’s Ethernet adapter has the correct IP and the cable is firmly seated at both ends.