Software module for working with Mazda SkyActiv-G petrol engine control units.
Module for reading and writing Denso and Mitsubishi control units installed in Mazda petrol vehicles with SkyActiv-G engines.
Which vehicles and control units does the Bitbox Mazda SkyActiv-G Petrol CAN module support:
FIDs: 240, 241, 243, 244, 249
Mazda Denso Gen3 (D02) (FID: 244)
The control unit is based on the Renesas SH72543 processor with 2.0Mb internal flash memory.
Allows reading and writing via CAN bus with checksum correction.
Mazda Denso Gen3 (D03) (FID: 243)
Alternative name for the control unit type is Denso Gen3 Crypto. The control unit is based on the Renesas SH72543 processor with 2.0Mb internal flash memory.
Allows reading and writing via CAN bus with checksum correction.
Mazda Denso Gen4 (D08) (FID: 249)
The control unit is based on the NXP MPC5746 processor with 4.0Mb internal flash memory.
Allows reading and writing via CAN bus with checksum correction.
Mazda Denso Gen4 (D11) (FID: 247)
The control unit is based on the NXP MPC5746 processor with 4.0Mb internal flash memory.
Allows virtual reading and writing via CAN bus with checksum correction.
Mazda Mitsubishi Gen3 (M03/M04) (FID: 240)
The control unit is based on the MH8501 processor with 2.0Mb internal flash memory.
Allows reading and writing via CAN bus with checksum correction.
Mazda Mitsubishi Gen3 (M09) (FID: 241)
The control unit is based on the MH8501 processor with 2.0Mb internal flash memory.
Allows reading and writing via CAN bus with checksum correction.
Mazda Mitsubishi Gen4 (M13/M16/M41) (FID: 248)
The control unit is based on the NXP MPC5746 processor with 4.0Mb internal flash memory.
Allows reading and writing via CAN bus with checksum correction.
The module requires the purchase of a USB dongle for protection. The dongle can be purchased from our store. An unlimited number of modules can be activated on one dongle.
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).
To activate the module, ONLY the dongle's serial number and email are required.
To work through the OBD2 connector, a J2534 adapter is required (Scanmatik 2, OpenPort 2.0, Dialink, Mongoose, etc.). More information about J2534 can be found here.
To connect the control unit on the bench, additional equipment needs to be purchased, 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