ابزار Xhorse VVDI

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

ابزار Xhorse VVDI

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

Xhorse Multi Prog Clone Ford Focus MK3 BCM

Need to clone Ford Focus MK3 BCM module. Where can i find the pinout for Xhorse Multi Prog?

Xhorse Multi Prog Pinout to Ford Focus MK3 BCM  1

Xhorse Multi Prog Pinout to Ford Focus MK3 BCM  2

Here it is.

Xhorse Multi-Prog
dv6t-14c094-aj CLONE
Ford BCM 2010
Focus mk3 – C-Max mk2
EEPROM 95320 – C-Shadow
CPU SPC560B647L – CFLASH
Xhorse Multi Prog Pinout to Ford Focus MK3 BCM  3

Xhorse Multi Prog Pinout to Ford Focus MK3 BCM  4

Xhorse Multi Prog Pinout to Ford Focus MK3 BCM  5

 

Yamaha NMax SCU R7F701695 Wiring Diagram to Xhorse Multi Prog

Yamaha NMax 2025 keyless unit pinout to Xhorse Multi Prog.

The keyless unit immo box (SCU) looks like this

Xhorse Multi Prog Pinout to Yamaha Nmax Keyless SCU 1

Xhorse Multi Prog Pinout to Yamaha Nmax Keyless SCU 2

Xhorse Multi Prog Pinout to Yamaha Nmax Keyless SCU 3

In multi prog software, select Yamaha SCU Module R7F701695.
ID53232

Processor: R7F701695

Xhorse Multi Prog Pinout to Yamaha Nmax Keyless SCU 4

Here is the wiring diagram.

Requires MQB RH850/V850 adapter for multi prog.

Xhorse Multi Prog Pinout to Yamaha Nmax Keyless SCU 5

Will Xhorse Super Chip XT57B Clone VAG MQB48 MQB49 Chip

Question:

Will Xhorse vvdi key tool max pro + XT57B super chip clone VAG MQB48 and MQB49 chips?

Xhorse Super Chip XT57B Clone MQB48 MQB49 1

Answer:

No, XT57B cannot clone MQB48/49 chips.

XT57B supports MQB48 and MQB49 chip types. But they are not used for cloning MQB systems. They only be used to generate and program them.

Xhorse Super Chip XT57B Clone MQB48 MQB49 2

NOTE:

The XT57B chip has region limitations. The global version cannot be used with Chinese version device, and vice versa. What we sell is the global version, which can only be used with global version key tools.

XT57B is compatible with mini key tool, key tool max, key tool max pro, key tool plus and key tool MIDI.

VVDI2 and old VVDI Key Tool cannot generate XT57B chip.

Xhorse Gen2 Red Remote Not Working Solution

 What Changed with the Xhorse Gen2 Red PCB Remote?

First, it’s important to understand the upgrade. The new Red PCB remote isn’t just a color change; it represents a significant internal overhaul:

  • In-House Manufacturing: Previously, Xhorse purchased ICs (Integrated Circuits) from external suppliers for the Green PCB. The Red PCB features an IC designed and manufactured by Xhorse itself.
  • Improved Performance: This change results in a higher operating frequency and, crucially, reduced battery consumption. The Red PCB remote will last longer on a standard 2032 battery compared to its Green predecessor.
  • Dual Connectivity: While it retains the programming socket (for wired generation), it now also supports a wireless cloning/generation option, which is the source of both its convenience and the current user confusion.

Some users reported that the cloning function not working using the new red PCB remotes.

When attempting to clone a remote using the standard “Clone” function with a Red PCB, the process fails. This has led to frustration, as the Green PCB method no longer applies.

Xhorse Red PCB Remote Cloning Not Working 1

Solution

The fix is simple but requires following a specific path in the software. Here’s how to successfully clone to the new Red PCB remote:

What You’ll Need:

 

The Correct Procedure:

Enter Clone Mode: On your Xhorse device, navigate to the “Remote Clone” function- “HCS/Fixed Code Clone”.

Read the Original Remote: Follow the on-screen prompts to read the frequency and button data from the original remote. You will typically press buttons like Lock, Unlock, Trunk, etc., as instructed until the device captures the frequency (e.g., 314.98 MHz).

Xhorse Red PCB Remote Cloning Not Working 2

Xhorse Red PCB Remote Cloning Not Working 3

Hit the ‘Clone’ button.

Xhorse Red PCB Remote Cloning Not Working 4

CRITICAL STEP – Do Not Use “Normal Clone”: After reading the original, you will be prompted to place the new Red PCB remote to burn/clone the data.

DO NOT select the standard “Clone” or “Normal Clone” option here.

INSTEAD, you must select the “Wireless Generation” option (only support wire remote gen2).

Xhorse Red PCB Remote Cloning Not Working 5

Initiate the Burn: With the Red PCB remote (battery installed) placed on the device, simply press the Unlock button once. The device will now successfully write the data.

Xhorse Red PCB Remote Cloning Not Working 6

Xhorse Red PCB Remote Cloning Not Working 7

Verification: You should see a “Burn Success” or “Clone Complete” message. Test the newly cloned remote on your central locking tester or the vehicle to confirm Lock/Unlock functionality.

Xhorse Red PCB Remote Cloning Not Working 8

Key Takeaways for Professionals

  • The Green PCB is being phased out. The Xhorse Red PCB Remote is the present and future for Xhorse remotes.
  • The cloning process has changed. The wired socket is no longer necessary for this operation. Success depends on using the “Wireless Generation” sub-option during the clone process.
  • Battery is mandatory. Unlike some wired programming, the Red PCB remote must have a battery connected for wireless cloning to work.

www.vvdishop.com

Xhorse VVDI2 BMW BDC2 Coding Unknown Version Solution

Problem:

Want to add a new key to BMW G31 BDC2 system with xhorse vvdi2 and BMW BDC2 adapter. but I can’t get past reading the code.
VVDI2 gave an error coding unknown version.

VVDI2 BMW BDC2 Coding Unknown Version Error 1

VVDI2 BMW BDC2 Coding Unknown Version Error 2

VVDI2 BMW BDC2 Coding Unknown Version Error 3

VVDI2 BMW BDC2 Coding Unknown Version Error 4

Solution:

Coding file is corrupt. Put it into the car and add coding file with your tool.

The car has a software version from 2021, but the coding data is missing, you can do your work normally, it has to be imported cafd manuel later, but that only works with a coding program, car missin cafd from S15A-21-11-560.

 

User report:

The problem has been solved and VVDI2 handled it very well. The problem was that the client arrived with corrupted CAFD data. Didn’t notice it at first. I put the BDC back in the car and fixed it via obd2 using the X-Diag program and Launch adapter. Then I went back to the previous steps and everything went smoothly.

I changed the BDC coding via OBD and the vvdi2 program accepted the new coding allowing me to program the new key.

VVDI2 BMW BDC2 Coding Unknown Version Error 5

VVDI2 BMW BDC2 Coding Unknown Version Error 6