Flex Update Heavy-Duty Software License

 News From Magic Motorsport :

Full Support for Heavy-Duty Vehicles

FLS0.15 out now

Flex goes beyond!

The new FLS0.15 software license is here, designed for those who work with heavy-duty vehicles. A single software package to access all OBD, OBD Full, Bench, and Boot protocols to program ECUs, TCUs, and DCUs installed on trucks, industrial vehicles, agricultural machinery, construction equipment, buses/coaches.

And there’s more: the new Flex software update, version 7.18.0.0, introduces 32 new compatibilities in OBD, Bench, and Boot, as well as 23 new supported electronic units for heavy-duty.

Magic Motorsport has launched a major update to the FLEX tuning platform, introducing the FLS0.15 software licence – a dedicated package for heavy-duty vehicles. This marks a key turning point for professional tuners and commercial vehicle workshops, opening the door to a broader range of high-value vehicle types without the need for separate tools or software add-ons.

From today, FLEX users can access full OBD, Bench, Boot and OBD Full protocols for ECUs, TCUs, and DCUs fitted to:

• Trucks

• Agricultural machinery

• Buses and coaches

• Construction equipment

• Industrial vehicles

This single licence now provides comprehensive coverage for one of the most demanding areas of tuning and ECU management.

A Major Software Expansion: Version 7.18.0.0

Coinciding with the release of the new licence is FLEX software version 7.18.0.0, which brings 32 new protocols specifically tailored to the heavy-duty vehicle market. This includes support for 23 different control units, spanning a wide range of OEMs and applications.

The update includes support across all tuning access methods – OBD, Bench, and Boot – and introduces some exclusive capabilities, such as:

• Cloning via Bench mode for DAF Delphi ETC3 (KWP)

• Exclusive real read access on Bosch DCU17CV51 used in JCB machinery

This significantly broadens the scope of what tuners can achieve with FLEX in the commercial and heavy vehicle sector.

New ECUs Now Supported

Delphi Units

• ETC3 (Bench, Boot)

• DCM3.3, DCM3.3+, DCM2.7AP, DCM7.24 (OBD, Bench)

Bosch Units

• DCU17CV51 (OBD)

• DCU17HD01 (Bench)

Continental Units

• EMS S8 (OBD, Bench)

• CPC3, CPC3 EVO, CPC4 (OBD Full, Bench)

• CPC5 (Bench)

Cummins

• CM2100A, CM2150C, CM2150E, CM2220A/B/C, CM2350A (Bench)

• Beta protocols: CM2200A/B, CM2250, CM2880 (Bench)

Manufacturers Covered in This Release

• DAF

• Scania

• Mercedes (Trucks and Buses)

• Freightliner

• JCB

• Dodge

• Iveco

• Agrale

• Kenworth

This now gives tuners access to an entirely new vehicle category, without needing multiple tool platforms or workarounds. It’s a significant commercial opportunity for workshops already working with light vehicle tuning who are now looking to expand into the heavy-duty space.

Which Software Licences Support This?

The new heavy-duty protocols are included in:

• FLS0.5M – FLEX Full Master

• FLS0.5S – FLEX Full Slave

• FLS0.15M – FLEX Heavy-Duty OBD/Bench/Boot Master

• FLS0.15S – FLEX Heavy-Duty OBD/Bench/Boot Slave

Whether you’re a new FLEX user or already running a Full Master setup, the FLS0.15 licence expands your tuning capabilities without hardware upgrades.

Xhorse Program Toyota Corolla 2020 XM38 Smart Key

 Here we will walk you through how to add a spare 4A smart key to Toyota Corolla 2020 using VVDI key tool plus without pin code.

 

Tools used:

Xhorse VVDI Key Tool Plus

Xhorse XD8ABAGL Toyota 8A AKL adapter

Xhorse XM38 Toyota smart key

Original key

 

 

Procedure:

Step 1: Generate XM38 smart key
Generate remote under Corolla/Levin 2019+ KeylessGo ID4A option

Step 2:

Connect Toyota 8A AKL adapter with smart box.

Go to IMMO Programming-Toyota- select by type- Smart key after 2016- Type 5 (4A 2019-2022).

The smart key box is usually under the passage storage box or above the driver brake pedal.

Check connection diagram. Remove the plug on the smart box and replace it with the BA harness plug. The other two plugs on the smart box need to be retained.

Select Backup smart box eeprom data.

Read and back up eeprom data.

Select Add smart key function.

Turn the ignition on to the ON position.
Key tool plus will read the software number.
Turn off ignition. Turn on emergency indicators.
Select the backup eeprom data

Xhorse will detect key information. 2 keys have been registered and 2 more keys remaining to be registered.

Hit OK to continue.

Put the original smart key close to the Start button and take it away after the buzzer rings.

Close all the smart keys (original key and XM38 key) to be registered to the Start button in turn, each smart key close to the Start button, the buzzer rings twice, then remove the Start button.
Turn the ignition on to the ON position.

Put the programmed smart key close to the Start button and take it away after the buzzer rings.

Programming is completed.

Test the remote control.

Both key work fine.

Done.

AutoTuner Adds Ford EMS2101 EMS2102 EMS2103 OBD Beta

 Exciting news for automotive tuning enthusiasts! The latest AutoTuner BETA release now supports Continental EMS2101, EMS2102, EMS2103, and EMS2106 ECUs for Ford vehicles via OBD. This breakthrough enables direct access to the real calibration data stored in the ECU—whether stock or previously modified—through the vehicle’s OBD port.

 

Key Features of the New AutoTuner BETA

• ECU Type: Continental  EMS2101, EMS2102, EMS2103, and EMS2106 Engine Control Unit (ECU)
• Readout Method: OBD (No Removal Required)
• MCU: C167-based
• Fast Processing:
  • Read Time: ~15 seconds
  • Write Time: ~15 seconds
• Automatic Checksum Correction

Call for Beta Testers!

Since this is a BETA release, user feedback is crucial for refining performance and compatibility. If you work with Ford vehicles equipped with Continental EMS210x ECUs, we encourage you to:

• Test the new OBD read/write functionality
• Report any issues or suggestions
• Share your experience with read/write speeds and stability

Your input will help shape the final, polished version of this powerful tuning tool!

Try the BETA today and push the limits of performance tuning!

Failed to Open 2024 MB SD C4/M6 Xentry Software Solution

 Some users have reported that the MB SD C4 DoIP/Super MB Pro M6 Xentry software (purchased through internal channels) suddenly stopped working on April 1st, 2025. After entering the usual username (Xentry) and password (88888), the program fails to open.

This issue affects different versions of Xentry XDOS OpenShell, 2024.03, 2024.09, 2023.09 etc.

This issue affects specific Mercedes-Benz diagnostic tools:

• MB SD C4 DoIP
• MB SD C5 
• Super MB Pro M6+/M6

 

Note: This issue does not affect users with VXDIAG devices running different software.

 

 

Solution

For C4 and M6 devices where the Mercedes software fails to log in, the offline config file was expired. Follow these steps to solve the problem:

1. Locate the Replacement Files:
   • Download the offline configuration files (offline_properties).
2. Replace the First File:
   • Navigate to: C:\ProgramData\Mercedes-Benz\config\XD_DT
   • Replace the existing file with the new one.
3. Replace the Second File:
   • Navigate to: C:\ProgramData\Mercedes-Benz\config\XD_MB
   • Replace the existing file with the new one.

Important: Both files must be replaced—skipping either one may not resolve the issue.

www.obdii365.com

Flex Update Chrysler GPECx ECUs OBD Solution!!!

 MAGIC MOTORSPORT FLEX NEW RELEASED OBD SOLUTION FOR CHRYSLER JEEP DODGE FIAT CONTINENTAL GPECX ECUS.

Version 7.17.0.0 of Flex Out Now with a Flex OBD Solution for Continental GPECx

 

New release on Flex dedicated to OBD programming: a Flex OBD solution for Continental GPECx, specifically GPEC2, GPEC2A, GPEC3, GPEC4, GPEC4LM engine units.

Just unlock the unit in Boot mode and then proceed with reading and writing the map area directly via the diagnostic port of the vehicle.

Thanks to the newest update of Flex, removing the ECU every time to modify engine parameters is no longer necessary: unlock your control unit in Boot mode and then go for OBD any other time.

 

Some of the supported vehicles:

• Chrysler 200 2.4L 180PS
• Dodge RAM Promaster City 2.4L 180PS
• Fiat Tipo I 1.0L Multiair 120PS
• Fiat Toro 2.4L Multiair II 185PS
• Jeep Compass 2.4L 180PS
• Jeep Renegade 1.3L Multijet 150PS

 

This new protocol is available for the following software packages:

OBD  

• FLS0.1M – SW Flex ECU (car, van, bike) OBD/Bench Master
• FLS0.1S – SW Flex ECU (car, van, bike) OBD/Bench Slave
• FLS0.5M – SW Flex Full Master
• FLS0.5S – SW Flex Full Slave

 

Newly added protocols:  

(OBD)  

• FCA Continental GPEC2 MPC5566 Read/Write/Checksum Calculation Maps, Read External EEPROM
  Reading Time : ~ 7 minutes  Writing Time : ~ 4 minutes
• FCA Continental GPEC2A MPC5674F Read/Write/Checksum Calculation Maps, Read External EEPROM
  Reading Time : ~ 10 minutes  Writing Time : ~ 5 minutes
• FCA Continental GPEC3 MPC5674F Read/Write/Checksum Calculation Maps, Read External EEPROM
  Reading Time : ~ 10 minutes  Writing Time : ~ 5 minutes
• FCA Continental GPEC4 MPC5674F Read/Write/Checksum Calculation Maps, Read External EEPROM
  Reading Time : ~ 10 minutes  Writing Time : ~ 5 minutes
• FCA Continental GPEC4LM MPC5674F Read/Write/Checksum Calculation Maps, Read External EEPROM
  Reading Time : ~ 10 minutes  Writing Time : ~ 5 minutes

 

Bug fixes 

• Fixed writing error in Bosch MG1UA008
• Added new CRC type for All Continental M3C
• Added new CRC type for Tata Delphi DCM7.1AP

 

Software improvements

• Added OBD Support for All Bosch MSE8.0
• Added support for VAG Bosch MG1CS008 SFD2

Clone Renault Getrag DC4 TCU with Yanhua ACDP

 Yanhua Mini ACDP has released a solution for bench cloning of the Getrag DC4 TCUs installed in Renault and Ford DPS6 (Powershift) brand vehicles.

 

Tools required:

Yanhua Mini ACDP2/ACDP1 hots

ACDP Module 26 with License AA00 

 PTCU2 Cable from module 19

 

Procedure:

 

Power on the ACDP.
Run ACDP APP.
Make sure your ACDP device has been bound.
Select Module function- Reanult DC4 (TC1766) clone.

Hit Help to check the connection diagram.

Connect the original DC4 TCU module with ACDP.
Select Reanult DC4 (TC1766) clone function.
Step 1: Connect TCU.
Enable stable network connection and do not disconnect device during the process.
Verify the system information.
Read hardware type and chip ID.
Connect system finished. ACDP will save the system info. automatically.

Step 2: Read/Write data
Full Backup data.
Reading chip data.
Save full data.

Step 3: Disconnect.
Disconnect the original TCU.

Connect a donor Renault DC4 TCU with ACDP2.

Connect TCU.
Verify system info, hardware type and chip ID.

Select Read/Write data
Full Write data.
Select original TCU full data.
Write chip data.
Write data to the donor TCU successfully.

Disconnect the donor TCU.

Install the new TCU back to the vehicle.

 

 

 

FYI: Flex also supports full OBD and Bench programming of the Getrag DC4 TCUs installed in Renault and Ford DPS6 (Powershift) brand vehicles.

 

Xhorse Multi Prog Clone Hyundai SIM2K-242 ECU

 Understanding the Task

Cloning a Hyundai Kia SIM2K-242 ECU, transferring data from an original unit to a donor unit. The ECU in question, identified as a SIM 2K model, integrates both the Powertrain Control Module (PCM) data and transmission data on a single board. Typically, cloning might involve only the ECU chip (in this case, a TC1766 processor), leaving the transmission data untouched if the issue lies solely with the transmission. However, the goal is to transfer the PCM (Powertrain Control Module) data from a donor ECU to an original ECU while preserving the transmission data.

For this clone, only the PCM data is transferred, leaving the transmission data intact. This is useful when the transmission is functioning correctly, but the engine control module needs replacement.

Tools and Preparation

• Xhorse Multi Prog: Used for reading and writing ECU data.
• Donor and Original ECUs: The donor ECU provides the data, while the original ECU is the target for cloning.
• Soldering Equipment: Required for connecting boot mode pins (P1, P2, P3) since the SIM2K-242 lacks a direct boot mode option in Multi-Prog.

Step 1: Back up donor ECU data.

Reading the Donor ECU

The first step was reading the donor ECU.

1. Select the Correct Protocol:
   SIM 2K 242 lacks boot mode support in MultiProg; the SIM2K-241 model provides the necessary pinout (P1, P2, and P3) for soldering and communication.

   (both share the same MCU/processor). Select SIM2K-242 ECU and use pinout of SIM2K-241.

2. Boot Mode Connection: Soldering is required to access the boot mode pins (P1, P2, P3) for communication.
3. Read Process:
   • Connect the donor ECU to Multi-Prog.
   • Read both the internal EEPROM (storing immobilizer data and VIN) and internal flash (storing firmware and VIN).
   • Save the files (e.g., “Donor_PCM”) for later use.

The reading process took approximately 5 minutes and 50 seconds for the flash alone, as reported by MultiProg’s built-in timer. The EEPROM and flash each contain a VIN number, a crucial detail that must be updated during cloning to match the original vehicle.

To locate the VIN, the technician entered specific addresses in the MultiProg hex editor: 1100 for the flash VIN and 7400 for the EEPROM VIN. This revealed the donor ECU’s VIN, ending in “104,” which would later be verified against the cloned unit.

Step 2: Reading the Original ECU

Next, the original ECU was read to capture its EEPROM and flash data. This step ensured that the technician had all the necessary information to overwrite the donor ECU accurately. The process mirrored the donor reading, with the data saved for comparison and writing.

Step 3: Writing the Data

Connect the donor ECU back to the multi prog and initiated the writing process.

1. Load Donor Files: Open the saved donor EEPROM and flash files in Multi-Prog.
2. Write to Original ECU:
   • Transfer the EEPROM data first, followed by the flash data.
   • The VIN from the donor will overwrite the original ECU’s VIN, ensuring compatibility.

To ensure accuracy, we can perform a second write, leveraging MultiProg’s comparison feature. This second pass skipped unchanged sections, completing in just 30 seconds for the EEPROM and 56 seconds for the flash—confirming a successful write.

Step 3: Verification

Post-writing, reread the donor ECU’s EEPROM and flash to verify the VIN. Using the same addresses (7400 for EEPROM and 1100 for flash), the VIN ending in “104” was confirmed, matching the original. This step ensured the cloning process preserved the vehicle’s identity and functionality.

• Perform a second write to confirm data integrity (Multi-Prog skips unchanged sections).
• Check the VIN locations (addresses 1100 for flash and 7400 for EEPROM) to ensure correct cloning.

Step 4: Testing the Cloned ECU

The final test involved installing the cloned donor ECU into the vehicle. After a brief moment with the security light on, the car started successfully, validating the cloning process. tools like OBDStar DC706 could also read SIM2K-241 ECUs, and the 241 protocol might even work for the 242 model due to shared reading and writing protocols.

Challenges and Observations

Internet connectivity is also critical, as the tool communicates with a server during reading and writing; slow connections can disrupt the process. 

Boot Mode is Crucial: Without soldering the boot pins, communication with the ECU is impossible.

VIN Must Match: Both the EEPROM and flash must have the same VIN to avoid issues.

Conclusion

Cloning an ECU is a meticulous process requiring precision, the right tools, and a deep understanding of automotive electronics. This walkthrough demonstrates how the MultiProg, with its boot mode support and hex editing capabilities, can effectively clone a SIM2K 241 ECU for a Kia Optima or Hyundai Sonata. 

http://blog.obdii365.com/2025/03/31/xhorse-multi-prog-clone-hyundai-kia-sim2k-242-ecu/