OBDSTAR ECU Flasher V31.00: IMMO OFF, ISN Writing, and VIN Writing for Legacy Bosch and Siemens ECUs

OBDSTAR's ECU Flasher V31.00 release, dated August 15, 2026, delivers three capabilities that locksmiths and tuners have been requesting for years across a far wider range of vehicles: IMMO OFF, ISN code writing, and VIN writing. The update rolls out to the OBDSTAR DC706 and X300 Classic G3 (with the ECU Clone license) and extends read/write support across dozens of legacy Bosch, Siemens, and Continental engine control units — the kind of modules that still turn up every week in shops handling module swaps, engine conversions, and stubborn immobilizer faults.

What the V31.00 Update Actually Covers

The release is built around bench and boot-mode access to older engine ECUs, grouped into three functional areas. The first is read/write expansion: OBDSTAR added read and write of internal EEPROM and internal flash for Bosch MED17 (TC1782) controllers across a long list of makes, including Changan, Chery, Geely, Great Wall, MG, SAIC, BAIC, JAC, Lifan, and Ford, plus the Ford Continental SID209 (TC1797) and Mahindra Delphi DCM7.1AP (TC277T). It also added write-VIN and read/write support for Dodge Bosch ME17.9.11, Hyundai and Kia Bosch EDC17C08 and ME17.9.11, and read/write of external EEPROM on Volkswagen Bosch ME7.5.30 and several Mercedes-Benz Delphi CRD3 controllers.

The second area is immobilizer work. OBDSTAR added IMMO data read, IMMO data decryption, and INT EEPROM data convert (clone) for Volkswagen, SEAT, and Skoda Bosch ME17.5.22 and ME17.5.24 controllers. It also added IMMO OFF across a large catalogue of older Siemens, Continental, and Bosch systems, including Alfa Romeo, Audi, Citroën, Dacia, Fiat, Ford, Honda, Kia, Lancia, Nissan, Opel, Peugeot, Renault, SEAT, Skoda, and Volkswagen. The third area is serial-number and identity writing: write-ISN for BMW, Mini, and Alpina Bosch MEVD17.2.6 and MEV17.2 controllers, and write-VIN for a broad range of Audi, Seat, Skoda, and Volkswagen Bosch MED17.1 and ME17.5.22 units.

Why IMMO OFF and ISN Writing Matter

For a working locksmith or tuner, these three functions map to three distinct jobs. IMMO OFF disables the engine immobilizer check inside the ECU, which is useful when a fault in the immobilizer is preventing a start, when an engine or ECU is being transplanted into a different vehicle, or for motorsport and bench-testing setups where the factory anti-theft system is no longer part of the build. ISN writing (the ISN, or Individual Serial Number, is BMW's immobilizer identifier stored in the ECU and CAS/DME) lets a technician write the correct ISN into a replacement or donor ECU so it can be matched to the vehicle without a dealership trip. VIN writing is the everyday counterpart: when a used or new ECU goes into a car, the VIN has to match the vehicle for the module to communicate properly and for the paperwork to stay clean.

What makes this update notable is that it brings these functions to the older generation of ECUs that many newer tools have moved past. Late-model vehicles get the headlines, but a large share of real workshop throughput is still these MED17, ME17.9, EDC17, SIMOS, and SID controllers in cars from roughly 2005 to 2015. Shops that can handle those modules in-house — rather than sending them out or referring the customer to a dealer — hold on to the job and the margin.

Hardware and Workflow Requirements

Because most of this work happens in bench or boot mode rather than through the OBD port, the workflow matters as much as the software. Bench reading means the ECU is removed from the vehicle and powered on a bench with the appropriate adapter and boot wiring. OBDSTAR's documentation for this class of work points technicians to the correct boot connections and — for the locked microcontroller families covered in earlier releases — the RH850/V850 adapter kit. Expect to solder a small number of boot wires for boot-mode access, and always verify the ECU is on a stable, current-limited power supply before reading.

The update is delivered over the air to the DC706 and X300 Classic G3 with an active subscription, so the first step is simply making sure the device is connected to Wi-Fi and the ECU Clone license is current. Once updated, the new functions appear in the existing ECU Flasher menus — there is no separate tool to buy. For shops that regularly do this kind of work, a dedicated ECU chip tuning and programming setup is the foundation, ideally paired with a reliable replacement ECU sourcing path for the times a module can't be recovered.

Who Should Update — and What to Watch

The obvious candidates are automotive locksmiths and ECU specialists who already run OBDSTAR hardware and handle key, immobilizer, or module-swap work. For them, the V31.00 release is effectively free added coverage for the older vehicles that make up a reliable share of their backlog. A locksmith with a professional key programmer and the ECU Flasher licence now has a cleaner path from "no start, immobilizer fault" to a running engine, whether the fix is a cloned IMMO data set or a freshly written ISN.

A few caveats are worth stating plainly. First, IMMO OFF removes an anti-theft function, so it should only be used where it is legal and appropriate — motorsport, off-road, bench testing, and legitimate module-replacement scenarios — not to defeat security on a road car. Second, boot-mode and bench work on engine ECUs carries real risk if the power supply or wiring is wrong; a brownout mid-write can brick a module. Finally, this update is about legacy coverage. It is not the locked, late-model TriCore unlock that OBDSTAR has been rolling out separately for BMW B48/B58 and similar units — that work continues under its own coverage roadmap.

What It Means for Your Shop

The bigger story here is about coverage longevity. Every year, a wave of vehicles crosses out of the "new enough to need the dealer" window and into the "old enough that independent tools finally reach it" window. Updates like V31.00 are how diagnostic vendors capture that wave — extending read/write, immobilizer, and identity functions down into the vehicle population that independent shops actually see. For a shop, the practical takeaway is to keep the OBDSTAR device and its subscription current, because the software — not the hardware — is where the usable coverage comes from.

For everyone else, the update is a useful benchmark of what "current" looks like in mid-2026. If your existing diagnostic toolkit still stops at fault-code reading on these older platforms, you are leaving module-swap and immobilizer work on the table. That work tends to command better margins than a simple scan, and it keeps customers with you instead of sending them to the dealer.

OBDSTAR's V31.00 release is not a headline-grabbing platform launch. It is the quieter, higher-value kind of update: more read/write coverage, more immobilizer functions, and more identity writing on the exact ECUs that keep independent shops busy. If that is your market, it is worth updating today.