Software module for working with Bosch engine control unit of Chinese petrol vehicles.
Module for reading and writing flash memory of Bosch engine control units for Chinese petrol vehicles.
Which vehicles and control units does the Bitbox China Bosch Petrol module support:
Bosch M7.9.7 (FID: 239)
The Bosch M7.9.7 engine control unit is based on the C167 processor with external flash memory of 512KB. It supports virtual reading and writing, as well as checksum correction
Bosch ME7.9.7 (FID: 68)
The Bosch ME7.9.7 engine control unit is based on the C167 processor with external flash memory of 1MB. It supports virtual reading and writing, as well as checksum correction.
Bosch M(E)7.9.71 (FID: 232)
The Bosch M(E)7.9.71 engine control unit is based on the ST10F275 processor with internal flash memory of 832KB. It supports virtual reading and writing, as well as checksum correction.
Bosch M7.8 (FID: 57)
The Bosch M7.8 engine control unit is based on the ST10F275 processor with internal working address space of 832KB. It supports virtual reading, writing with auto-protection disabled, as well as checksum correction.
Bosch ME7.8.8 K-line (FID: 63)
The Bosch M7.8.8 engine control unit is based on the ST10F275 processor with internal working address space of 832KB. It supports virtual reading, writing with auto-protection disabled via K-line, as well as checksum correction.
Bosch ME7.8.8 CAN (FID: 76)
The Bosch M7.8.8 engine control unit is based on the ST10F275 processor with internal working address space of 832KB. It supports virtual reading, writing with auto-protection disabled via CAN bus, as well as checksum correction.
Bosch ME17.8.8 (FID: 60)
The Bosch ME17.8.8 engine control unit is based on the Infineon Tricore TC1728 processor with internal flash memory of 1.5MB. It supports reading and writing of calibration area, as well as checksum correction.
Bosch ME17.8.8 Saic (FID: 127)
For Saic vehicles. The Bosch ME17.8.8 engine control unit is based on the Infineon Tricore TC1728 processor with internal flash memory of 1.5MB. It supports reading and writing of calibration area, as well as checksum correction.
Bosch ME17.8.8 Vantage (FID: 166)
For Vantage vehicles. The Bosch ME17.8.8 engine control unit is based on the Infineon Tricore TC1728 processor with internal flash memory of 1.5MB. It supports reading and writing of calibration area, as well as checksum correction.
Bosch ME17.8.8.1 (FID: 82)
The Bosch ME17.8.8.1 engine control unit is based on the Infineon Tricore TC1728 processor with internal flash memory of 1.5MB. It supports reading and writing of calibration area, as well as checksum correction.
Bosch ME17.8.8.1 Geely (FID: 84)
For Geely vehicles. The Bosch ME17.8.8.1 engine control unit is based on the Infineon Tricore TC1728 processor with internal flash memory of 1.5MB. It supports reading and writing of calibration area, as well as checksum correction.
Bosch MED17.8.10 Haval (FID: 122) /TEST/
For Haval vehicles. The Bosch MED17.8.10 engine control unit is based on the Infineon Tricore TC1728 processor with internal flash memory of 1.5MB. It supports reading on the bench and writing via the diagnostic connector, as well as checksum correction.
Bosch MED17.8.10 Geely (FID: 234) /TEST/
For Geely vehicles. The Bosch MED17.8.10 engine control unit is based on the Infineon Tricore TC1728 processor with internal flash memory of 1.5MB. It supports reading on the bench and writing via the diagnostic connector, as well as checksum correction.
BYD TB10 Type1 (FID: 81)
The BYD TB10 engine control unit is based on the Renesas SH72531 processor with internal flash memory of 1.25MB. It supports reading and writing of calibration area, as well as checksum correction.
BYD TB10 Type2 (FID: 148)
The BYD TB10 engine control unit is based on the Renesas SH72531 processor with internal flash memory of 1.25MB. It supports virtual reading and writing of calibration area, as well as checksum correction.
Bosch M7.8/ME7.8.8 BSL K-line (FID: 75)
Allows reading Bosch M7.8/ME7.8.8 K-line blocks based on protected ST10F27X processors in BSL mode. Requires the BITS001 or Powerbox / Combibox adapter. Guaranteed compatibility only with Tactrix Openport 2.0 adapter.
To use the module, you need to purchase a Bitbox USB dongle. You can purchase the dongle in our store. One dongle can be used to activate an unlimited number of modules.
Module activation is done within 1 hour on business days (usually 10-15 minutes). Activation may be delayed during weekends and holidays (up to 2 hours).
Module activation requires ONLY the serial number of the dongle and email.
To work through the OBD2 connector, a J2534 adapter is required (Scanmatik 2, OpenPort 2.0, Dialink, Mongoose, and others). Learn more about J2534 here.
To connect the control unit on the bench, additional equipment is required, any of the following:
Powerbox and Combibox for PCMflash are fully compatible with Bitbox.
1. No Refunds or Modifications for Digital Licenses
Activated modules or licenses cannot be returned or refunded.
If an incorrect key or device number is entered by the customer, the purchase is not eligible for return.
Licenses cannot be modified, transferred, or reissued for another device under any circumstances.
2. Irreversible Order Processing
After the order status changes to “Waiting for activation”, the data has already been sent to the developer.
From this point onward, the order cannot be canceled, edited, corrected, or refunded.
3. Responsibility for Software Functionality
Our store is not responsible for the functionality, performance, or declared features of any software module.
We do not guarantee the listed functions because we are not the developer.
4. Accuracy of Product Information
Module and script descriptions are provided directly by the manufacturer.
IOBD.io is not responsible for any inaccuracies, missing details, or differences between the description and actual operation.
In disputed situations regarding functionality or listed features, the customer must contact the manufacturer.
5. Customer Responsibility for Installation
IOBD.io sells professional automotive diagnostic software and equipment.
Installation, setup, configuration, and compatibility checks must be performed by the customer.
We do not provide remote installation, programming, or setup services unless explicitly stated otherwise.
6. Required Technical Knowledge
These products are intended for users with basic technical knowledge in automotive diagnostics.
The customer is fully responsible for understanding the installation process and using the software and hardware correctly.
7. No Liability for Incorrect Usage
IOBD.IO is not responsible for issues caused by:
incorrect installation
unsupported or incompatible hardware
improper configuration
third-party interference
Important:
This function is available only on certain BMW engines and is NOT applicable to other vehicle brands.
The information below applies only to stock engines with factory ECU software and a standard exhaust system.
What This Parameter Actually Represents
This is NOT a direct measurement of fuel octane and is NOT a direct octane reading calculated by the ECU.
The value is an adaptation factor ranging from 0 to 1, where:
- 0 = no correction
- 1 = maximum correction
According to BMW’s internal definition:
Faktor adaptierte Kraftstoffqualität (0 = ROZ98 / 1.0 = ROZ91)
- 0 corresponds to 98 ROZ
- 1.0 corresponds to 91 ROZ
ROZ is the German equivalent of RON (Research Octane Number).
The device converts this multiplier into a more intuitive octane value for user convenience.
⚠️ The device does not measure anything itself.
It only displays the data provided by the engine control unit (ECU).
How the ECU Evaluates Fuel Quality
Each ECU has different calibration sensitivity:
- Sensitivity to the adaptation factor
- Sensitivity of the knock control system
Fuel quality is evaluated subjectively by the ECU, primarily based on:
- Knock ignition timing corrections
- Overall engine noise levels
BMW G-Series & LCI F-Series (B-Engines)
B38 / N63 / S63 / N74
These engines are highly sensitive to octane adaptation.
- During warm-up and cruising, the displayed octane may frequently drop to 95 or lower.
- This does NOT automatically indicate poor fuel quality.
- Under load, the value should increase.
⚠️ If the value continues to decrease under load, this may indicate a problem.
B46 / B48 / B58
These engines have low sensitivity.
- During cruising, octane will typically display maximum values even with mediocre fuel.
- Under load, the value will decrease if fuel quality is truly poor.
S58
Octane correction is virtually inactive.
- It will typically always show 98.
- If it drops below 98, fuel quality is genuinely very poor.
BMW F-Series (Pre-LCI) with N/S Engines
Most pre-LCI F-series ECUs do not calculate octane adaptation.
Do not expect this parameter to function.
S55
- Octane parameter not used by the system
- Display not supported
- However, display of the last 5 refueling quality events is supported
S63
- Octane parameter not used
- Display not supported
- Refueling quality display not supported
BMW E-Series
Octane parameter not available. Display not supported.
Important Notes About Tuned Vehicles
With modified hardware or custom tuning, behavior may vary significantly. Always consult your tuner regarding expected operation.
Key principles:
- If octane drops under load, it means fuel quality is worse than expected under those conditions.
- This does NOT automatically mean the fuel itself is bad.
Examples:
- If a tuner increases ignition timing and boost pressure, even good fuel may cause knock corrections, and the ECU may interpret it as poor fuel.
- Thin-walled or poorly mounted exhaust systems may create parasitic noise, which the ECU may interpret as engine knock, causing negative correction.
- Conversely, if knock sensitivity is reduced or octane correction is disabled in tuning, readings may appear ideal while actual engine safety is compromised.