Software module for working with the engine control unit Bosch MG1/MD1 of BMW F and G series cars.
Module for working via Ethernet diagnostic connector with Bosch MG1 and MD1 control units installed on BMW F and G series cars.
Bosch units based on NXP MPC5777 processor with 7.5Mb internal flash memory and Infineon Aurix TC298 with 8Mb memory are supported.
Which cars and control units are supported by Bitbox BMW Fxx/Gxx Bosch MG1/MD1 ENET module:
FIDs: 160, 161
- BMW Fxx/Gxx Bosch MG1 MPC5777 ENET (FID: 160)
- BMW Fxx/Gxx Bosch MD1 MPC5777 ENET (FID: 161)
- BMW Fxx/Gxx Bosch MG1 TC298 ENET (FID: 162) [TEST]
The module allows:
- Software version identification
- Virtual reading from the server
- Reading from the unit if there is no file on the server (not available for all software versions)
- Writing with checksum and CVN correction
- Reading and clearing errors
Please note the limited support for cars with new software versions.
Attention! New updates for BMW cars with ISTA-P 3.67.0.000 [2019] and ISTA-P 3.66.2.002 [2019] versions are currently not supported by the BitBox software, especially for the Bosch Fxx/Gxx MG1/MD1 E-NET module. If the file is not available on the server and the car is new, do not attempt to write the file to the car. If you have already attempted to do so, immediately press RECOVERY without turning on the ignition and restore the original file using dealer equipment (including E-Sys).
ISTA-P 3.67 version is particularly dangerous as it can permanently damage the ECU, with no possibility of recovery even with BENCH-MODE tools.
The developer is working on adding detection of this protection and prohibiting writing until the ability to write modified files is developed!
Be careful!
The module requires the purchase of a Bitbox protection USB key Bitbox. The key can be purchased in our store. An unlimited number of modules can be purchased for one key.
Module activation takes place within 1 hour on business days (usually 10-15 minutes). Activation may be delayed on weekends and holidays (up to 2 hours).
Module activation requires ONLY the serial number of the key and email.
Attention! This module does not work with J2534 adapters, it requires ENET-to-OBD2 cable. The module also works ONLY on the car (does not work on the bench).
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