Software module for working with Rotax engine control units.
The module is designed for working with various extreme equipment using Rotax engines with Bosch ME17.8.5 and Siemens MSE 3.7x control units. The work is done through the diagnostic connector or on the bench without opening the control unit.
Which vehicles and control units does the Bitbox Rotax Extreme module support:
Siemens MSE 3.7x (FID: 10, 80)
The Siemens MSE 3.7x family allows for software version identification in control units, reading FullFlash, and writing calibration areas via K-line (FID 10) or CANbus (FID 80), as well as automatic checksum correction during writing.
Currently, two types of control units are supported:
- Siemens MSE 3.7 based on the ST10F269 processor with internal flash memory of 256KB
- Siemens MSE 3.71 based on the ST10F269 processor with internal flash memory of 256KB
Older control units based on the Infineon C167 processor and external flash memory 29F200BB are planned to be added. If you have such a control unit, please contact us.
Bosch ME17.8.5 (FID: 11, 31)
Allows for software version identification in Gen1 and Gen2 control units, virtual reading of FullFlash, writing calibration areas via CAN bus, as well as automatic checksum correction during writing.
The control unit operates based on the Infineon Tricore TC1762 processor with internal flash memory of 1504KB.
Bosch ME17.8.5 BSL (FID: 36)
If the file is not available on the server, allows for FullFlash reading with checksum verification in BSL mode. Requires disassembly of the control unit.
Rotax P-TEK (FID:199)
The control unit operates based on the MC9S12D64 processor with internal flash memory of 64KB. It supports reading and writing calibrations via CAN bus with checksum correction.
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). Learn more about J2534 here.
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