17%20Petrol%20CAN-100x100.png)
17%20Petrol%20CAN-1000x1000.png)
Module for reading and writing flash memory of Bosch MED(G)17 control units installed in Ford petrol cars.
Module for reading and writing flash memory of Bosch MED(G)17 control units via CAN bus, installed in Ford diesel cars.
Which cars and control units does the Bitbox Ford Bosch MED(G)17 Petrol CAN module support:
FIDs: 322, 323, 324, 325, 333
Ford Bosch MED17.0 (FID: 322)
This family supports working with Bosch MED17.0 control units based on Infineon Tricore TC1767 with internal flash memory of 2 MB.
Allows software identification, reading, and writing. Checksum correction is done during writing.
Ford Bosch MED17.0.1 (FID: 323)
This family supports working with Bosch MED17.0.1 control units based on Infineon Tricore TC1767 with internal flash memory of 2 MB.
Allows software identification, reading, and writing. Checksum correction is done during writing.
Ford Bosch MED17.0.7 (FID: 323)
This family supports working with Bosch MED17.0.7 control units based on Infineon Tricore TC1782 with internal flash memory of 2.5 MB.
Allows software identification, reading, and writing. Checksum correction is done during writing.
Ford Bosch MEDG17.0 (FID: 323)
This family supports working with Bosch MEDG17.0 control units based on Infineon Tricore TC1797 with internal flash memory of 4 MB.
Allows software identification, reading, and writing. Checksum correction is done during writing.
Ford Bosch ME17.0.3 (FID: 333)
This family supports working with Bosch ME17.0.3 blocks based on Infineon Tricore TC1724 with internal flash memory of 1.5 MB.
It allows software identification, reading, and writing. Checksum correction is done during writing.
To work with the module, you need to purchase USB protection key Bitbox. The key can be purchased in our store. You can purchase an unlimited number of modules for one key.
Module activation is done within 1 hour on business days (usually 10-15 minutes). Activation may be delayed on weekends and holidays (up to 2 hours).
To activate the module, ONLY the serial number of the key and email are required.
To work through the OBD2 connector, a J2534 adapter is required (Scanmatik 2, OpenPort 2.0, Dialink, Mongoose, and others). More about J2534 here.
To connect the control unit on the table, you need to purchase additional equipment, 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
