Module for working with petrol, electric and diesel vehicles with Denso control units based on the MPC5746 processor (with processor mask 1N83M).
Work is carried out when connected to the table via the CAN bus. Removing the ECU is necessary for direct connection, no opening is required!
Which vehicles and control units does the Bitbox Denso MPC BENCH-CAN module support:
FIDs: 350, 351, 358, 363, 374
- Ashok Leyland Denso Diesel MPC5746 BENCH-CAN (FID: 374)
- Hino Denso Diesel MPC5746 BENCH-CAN (FID: 358)
- Mazda Denso Petrol/Diesel MPC5746 BENCH-CAN (FID: 351)
- Subaru/Toyota Denso Petrol MPC5746 BENCH-CAN (FID: 350)
- Suzuki Denso Petrol MPC5746 BENCH-CAN (FID: 363)
Reading and writing FullFlash, checksum correction during writing, reading and writing EEPROM are supported.
Other types of control units will be added as possible.
The module requires the purchase of a USB protection key Bitbox. The key can be purchased in our store. An unlimited number of modules can be purchased for one key.
Module activation is carried out within 1 hour on business days (usually 10-15 minutes). Activation may be delayed on weekends and holidays (up to 2 hours).
Only the serial number of the key and email are required to activate the module.
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, additional equipment from the list below must be purchased:
Powerbox and Combibox for PCMflash are fully compatible with Bitbox.
An activated module or license cannot be returned.
If you have entered the wrong key or device number, the return is not valid. It is not possible to modify the license for another device.
After status update to "Waiting for activation", the data has already been sent to the developer for activation. The order cannot be canceled or corrected starting from this status update.
Pay attention to all information specified in the description of modules and scripts taken from the manufacturer. We are not responsible if the information is not correct or there are some differences from the reality. In the disputed situation, it is necessary to look for a solution to the issue to the manufacturer.
Our store is not responsible for the functionality of the software module. We cannot guarantee the declared functions since we are not the developer.
