ابزار Xhorse VVDI

Xhose VVDI نرم افزار برنامه نویس اصلی و سخت افزار

ابزار Xhorse VVDI

Xhose VVDI نرم افزار برنامه نویس اصلی و سخت افزار

Delphi MT62.1 ECU Pinout to Xhorse VVDI Prog

 Both Xhorse VVDI Prog and Multi Prog will read and write Delphi MT62.1 ECU for Changan, BAIC, Dongfeng car brands.

Here is the wiring diagram to this ECU.

The key point to note is that the yellow RESET wire must not be connected to the position marked on the board. The specific correct position has been indicated in the diagram.

Otherwise may fail to read this ECU with vvdi prog.

Xhorse VVDI Prog Pinout to Delphi MT62.1 ECU 1

Xhorse VVDI Prog Pinout to Delphi MT62.1 ECU 2

Xhorse VVDI Prog Pinout to Delphi MT62.1 ECU 3

Xhorse VVDI Prog Pinout to Delphi MT62.1 ECU 4

Xhorse VVDI Prog Pinout to Delphi MT62.1 ECU 5

Xhorse VVDI Prog Pinout to Delphi MT62.1 ECU 6

Xhorse VVDI Prog Pinout to Delphi MT62.1 ECU 7

VVDI Prog or CGPro for BMW 35160WT 35128WT

 When adjusting mileage on BMW instrument clusters equipped with EEPROM chips like the 35160WT, 160D0WTand 35128WT, two popular tools are often considered: Xhorse VVDI PROG and CGPRO. Below is a point-by-point evaluation based on real‑world testing to help you choose the right tool.

Xhorse VVDI PROG vs CGPRO: BMW Mileage Correction 1

Xhorse VVDI PROG vs CGPRO: BMW Mileage Correction 2

FeatureVVDI PROGCGPRO
CompatibilityBroad EEPROM and module support (CAS, FRM, etc.).Covers many BMW chips; includes adapters for 35128WT (mode 2/3).
Mileage CorrectionReliable via chip‑replacement method using dedicated emulator chips (sold separately).Built‑in mileage editor; automatic checksum calculation for supported chips.
Ease of UseRequires third‑party software for data editing; workflow can be complex.More user‑friendly interface with integrated functions.
Cost & AccessoriesHigher initial price (~$419); essential adapters often sold out/extra cost.Lower entry price ($399); most adapters included.
Key LimitationCannot erase 35160WT mileage with standard accessories; chip replacement adds cost.Unreliable erasure on 35160WT; cannot reduce mileage on 35128WT mode 1.
Online RequirementNo mandatory internet connection for basic operations.Requires internet for license validation.
Overall VerdictRobust for chip‑level replacement, but hidden costs and complexity exist.Streamlined for common tasks, yet inconsistent on critical chips.

 

Summary & Recommendations

You need deep chip-level programming capabilities

Regularly perform BMW chip replacement or module cloning

Require reliable 35160WT solutions via chip emulation
(Note: Requires higher expertise and additional investment)

Xhorse VVDI PROG vs CGPRO: BMW Mileage Correction 3

Xhorse VVDI PROG vs CGPRO: BMW Mileage Correction 4

  • Choose CGPRO if:

Your focus is on straightforward mileage adjustment for common BMW models

Prioritize workflow efficiency and user-friendly operation

Need integrated software with automated calculations
(Note: May show inconsistency with specific chips like 35160WT)

Xhorse VVDI PROG vs CGPRO: BMW Mileage Correction 5

Xhorse VVDI PROG vs CGPRO: BMW Mileage Correction 6

Key Reality:
No single tool fully supports all BMW EEPROM chips. The 35160WT series remains particularly challenging.

 

Quick Guide:

Basic shops: CGPRO for cost-efficiency

BMW specialists: VVDI PROG for technical flexibility

 

Final Decision:
Match your choice to actual workflow needs and technical capability. For consistent results across varied BMW chips, a multi-tool approach often outperforms any single device. Always have backup plans for chip-specific limitations.

 

www.vvdishop.com

VVDI2 Program BMW X6 F16 BDC All Keys Lost

 Introduction & Initial Challenge:

The vehicle in question, a BMW X6 F16 BDC system, arrived with a complete key loss (AKL). In such modern BMWs, simply programming a new key via the OBD-II port is not possible without first obtaining critical security data and preparing the vehicle’s central computer. The primary challenge involves two main steps:

Reading the Immobilizer Security Number (ISN) from the Engine Control Unit (DME).

Unlocking and preparing the Body Domain Controller (BDC) to accept new keys.

 

Step 1: Reading the ISN from the DME

Since no keys were present, the first step was to physically access the vehicle’s engine control units.

Remove DME from the vehicle. The specific model was identified as Bosch 0261 S15 497 (MEVD 17.2.h).

You can read ISN code with CG FC200 programmer on bench.

 

 

Step 2: Unlock and Prepare the BDC

With the ISN acquired, the next step was to prepare the BDC, the vehicle’s main security and access module.

Physical Access: The BDC was carefully removed from the vehicle. Its cover was opened to reveal the internal circuit board and the essential M95xxx EPROM chip.

Read and save BDC 95256 eeprom data with vvdi prog and clip adapter.

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 1

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 2

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 3

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 4

Bench Setup: The BDC was placed on a dedicated test bench, where power and necessary connectors were attached to simulate being in the vehicle.

Unlocking via VVDI2: Instead of directly reading and writing the EEPROM, we used the VVDI2. By selecting the “BDC Key Learn” function and choosing to program/unlock the BDC directly via OBD (simulated on the bench), the tool connected to an online server.

Server-Side Unlocking: This process involved the server generating a modified “flash file.” The VVDI2 tool then wrote this file to the BDC, a process that took several minutes. Upon completion, a message confirmed the “FEM BDC update success.”

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 5

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 6

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 7

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 8

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 9

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 10

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 11

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 12

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 13

Step: Programming Key

After the BDC was successfully unlocked, we proceeded to program the first new key.

Key Learning: Back in the VVDI2’s “BDC Key Learn” menu, the “Add Key” function was used. The previously saved ISN was pasted into the tool.

Success with Anomalies: The key was successfully learned, and the car started successfully. The remote functions also worked after a battery was installed in the key fob.

Persistent Fault Code: A diagnostic scan revealed a persistent “SWFL Lost” (Steering Wheel Lock) fault code. Clearing this fault permanently would require a full update of the BDC using BMW’s official ESys software, a step deferred based on the customer’s potential need for only one key.

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 14

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 15

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 16

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 17

VVDI Prog and VVDI2 Program BMW F16 BDC All Keys Lost 18

www.vvdishop.com

Xhorse VVDI Prog Read and Write Renault SIRIUS 32

 Renault Siemens SIRIUS 32 read and write, immo off with Xhorse VVDI Prog.

Xhorse VVDI Prog Read and Write Renault SIRIUS 32 1

Disassemble the Siemens SIRIUS 32 ECU.

Locate and desolder the AM29F400BB chip.

Solder the AM29F400BB chip to the eeprom adapter.

Xhorse VVDI Prog Read and Write Renault SIRIUS 32 2

Xhorse VVDI Prog Read and Write Renault SIRIUS 32 3

In VVDIProg software, select EEPROM-AMD-AM29F400BB-xxS option.

Xhorse VVDI Prog Read and Write Renault SIRIUS 32 4

Read and save immo data.

Xhorse VVDI Prog Read and Write Renault SIRIUS 32 5

Modify immo data with IMMO Bypass program or a tuner.

Write the modified immo data with vvdi prog.

Xhorse VVDI Prog Read and Write Renault SIRIUS 32 6

Xhorse VVDI Prog Read and Write Renault SIRIUS 32 7

Xhorse VVDI Prog Read and Write Renault SIRIUS 32 8

Solder the AM29F400BB chip back to the ECU. Reinstall the ECU and install it on vehicle.

www.vvdishop.com

Xhorse VVDI Prog 5.3.8 adds BMW G Series BDC3 Option

 Xhorse VVDI Prog released new software version V5.3.8 on October, 10th, 2025.

 

VVDIProg v5.3.8 (2025-10-09)
* This version DON’t need update firmware
+ Add BDC03 option in <4-IMMOBILIZER>-><BMW>
* Modify MB91F467D option in <2-MCU>-><FUJITSU-MB9XF>: Erasing failure repair
* Modify CAMRY AC COMPUTER option in <8-OTHER>-><TOYOTA>: Erasing failure repair
* Modify Rover 2017- BCM(MPC5748G)option in <4-IMMOBILIZER>-><LandRover>: Wiring diagram update
* Modify S350-CONTROL-UNIT-PKE option in <4-IMMOBILIZER>-><JMC>: Wiring diagram update
* Modify ZAFIRA-DG128, ASTRA-DG128 options in <4-IMMOBILIZER>-><Opel>: Wiring diagram update
* Fix of other known issues

 

Free download VVDI Prog V5.3.8 software

vvdi prog add bmw bdc3 option

VVDI Prog BMW BDC3 wiring diagram

BMW BDC03 NCF29A1-B

vvdi prog BMW BDC03 NCF29A1-B

BMW BDC03 NCF29A1

BMW BDC03 NCF29A1 wiring

Xhorse multi prog also update BMW BDC3 option on October 9th, 2025.

Collect original BMW BDC3 key data with vvdi prog, then load data to vvdi2/key tool plus/key tool midi to add (copy) key.