Software module for working with Keihin motorcycle engine control unit used in Honda vehicles.
The module is used for working with Keihin control units installed in motorcycles, scooters, ATVs, and other Honda motorcycles.
It allows for software version identification, reading and writing full flash via K-line, verification and checksum calculation, reading and writing EEPROM, and recovery from any state.
Supported control units with numbers 38770-XXX-XXX.
Which engines and control units does the Bitbox Honda Moto Keihin module support:
FIDs: 125, 126, 174, 175, 226, 227
- Honda Moto Keihin K-Line Reader (FID:175) - universal reading of all block types with automatic size detection.
- Honda Moto Keihin M32R/SPC 256KB (FID:125) - R/W/CS
- Honda Moto Keihin H8C 32/56KB (FID:126) - R/W/CS
- Honda Moto Keihin SPC 512KB (FID:174) - R/W/CS
- Honda Moto Keihin SH7058 1MB (FID:227) - R/W/CS
- Honda Moto Keihin R8C/M16C 32/48/64/96/128KB (FID:226) - VR/W/CS
Other block types will be added if possible.
Attention! Some blocks may require manual input in programming mode for writing. This can only be done when connected on the bench. In case such block type is detected, BitBox will prompt you to manually short-circuit contacts on the block connector. Refer to the manual and YouTube for details.
Some Keihin R8C/M16C blocks have limitations on reading, files are read incompletely and cannot be used for writing. If you receive a checksum error during reading, do not use that file, try virtual reading with FID:226. If the file is not available on the server, it needs to be read with the block disassembled using any programmer that supports R8C/M16C processors. The block can also be sent for reading to the developer's office.
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).
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