ابزار Xhorse VVDI
Xhose VVDI نرم افزار برنامه نویس اصلی و سخت افزارابزار Xhorse VVDI
Xhose VVDI نرم افزار برنامه نویس اصلی و سخت افزارQ: Will Xhorse VVDI clone Toyota H transponder?
Q: Does the Mini Key Tool support Toyota H Transponder copy/cloning?
A: No. VVDI Mini Key Tool supports Toyota H chip generation but not copy/cloning.
Q: What chip can be used to generate Toyota H transponder?
A: Please use the Xhorse Toyota H chip here to generate:
Q: Will Xhorse VVDI2 clone Toyota H transponder?
A: No, VVDI2 can only generate Toyota H chip. You need to activate Vvdi2 H chip generation authorization.
Condor Dolphin XP005 Cut VW HU66 Key
How-to: decode and cut VW Polo HU66 using Xhorse Condor Dolphin XP005 key cutting machine.
1.Decode HU66
In Xhorse App, select Vehicle Database->Volkswagen->Polo->HU66
Align M2 Clamp
Press Decode Key
Decoding key in process
Condor Dolphin decode key success
2. Cut HU66
Press Find Bitting
Bitting is correct
Bitting is correct
Press key 1 bitting
Select Cutting Key
Cutting key in process
Cut key success
Test the new key. It works!
Done.
Program Audi A6 Q7 Allroad Dealer Key with VVDI2
Here’s the solution for Xhorse VVDI2 prepares Audi A6/Q7/Allroad 4th immobilizer dealer key successfully but fail to star car.
Reason: The step for key learning is skipped/wrong.
Solution:
please check guides below to to learn the key correctly.
Solution:
please check guides below to to learn the key correctly.
Audi 4th Immobilizer system- Audi A6/Q7/Allroad
This type use MEGAMOS 8E transponder
If you want prepare a new dealer key, you must know the total 12 bytes CS.
But there’s only 6 bytes CS in ECU, so we need read the whole J518 EEPROM dump.
This type use MEGAMOS 8E transponder
If you want prepare a new dealer key, you must know the total 12 bytes CS.
But there’s only 6 bytes CS in ECU, so we need read the whole J518 EEPROM dump.
Read CS from ECU, only read 6 bytes CS and PIN. With 6 bytes CS and PIN help, VVDI2 can use OBD standard method to read/write EZS-Kessy EEPROM (J518), read/write VIN etc
Step 1: Autodetect from engine ECU
Step 2: Read and save EZS-Kessy EEPROM (J518)
Step 3: Load J518 eeprom dump file
Step 4: Make dealer key
Step 5: Key Learning
Step 2: Read and save EZS-Kessy EEPROM (J518)
Step 3: Load J518 eeprom dump file
Step 4: Make dealer key
Step 5: Key Learning
Note: OBD standard method only support 9S12DT128 type.
In J518 use 9S12DT128 chip (most cars before 2009 use this type).
But does not support J518 with 9S12DT(G)256 chip (most cars after 2009 use this type.)
That means 9S12DT(G)256 type doesn’t support prepare a dealer key with this method.
In J518 use 9S12DT128 chip (most cars before 2009 use this type).
But does not support J518 with 9S12DT(G)256 chip (most cars after 2009 use this type.)
That means 9S12DT(G)256 type doesn’t support prepare a dealer key with this method.
VVDI2 also can read J518 dump as service model what is only used for make normal dealer key, need to make sure which is chip model, VVDI will read wrong data if is no match, so first make sure what chip it is.
Remark:
Read dump with working key is only can be used for make normal dealer key, not for OEM key, neither for write back to KESSY.
Step 1: Read J518 EEPROM Dump with working key
Step 2: Load J518 eeprom dump file
Step 3: Make dealer key
Step 4: Key Learning
VVDI Key Tool copy Ford ID83 chip with Xhorse App
Xhorse app runs faster than old VVDI Key Tool App. The KeyTool registration procedure is the same as Mini Key Tool and Condor Dolphin.
Check here:
VVDI Key Tool 70/83 Online Calculation
Transponder Clone->70/83 Online Calculation
Put original key into Key Tool coil to recognize
Identified Ford ID83 transponder
Uploading to server
Query calculation result
Put new key into VVDI keytool and write data
Write key success
Ford ID83 transponder clone success.
Condor XC-Mini Volvo HU56R Thickness problem solution
Q:
I just bought condor mini key cutter for one month, and already update to latest firmware, v2.1.1. Volvo HU56 thickness setting wrongly, it should be 2.5mm, and cutting thickness should be 1mm. volvo v40 key eats like 0.6 or more mm deeper than it should. it ate the clamp!!! and not very accurate.
A:
About Volvo HU56R condor machine database the key thickness is 3mm and cutting depth is 1.25mm
but if fact,users key is different, thickness is 2.5mm and cutting depth is 1mm.
so users can use define key data first ,named ‘HU56R-1_U’,later Xhorse will find a better solution.
1.connect PC to Condor machine
2.use attached software, sync’HU56R-1_U’ to condor xc-mini key cutting machine
3.select ‘cut by bitting’—enter ‘HU56R’ you will find HU56R-1_U,then cutting.
but if fact,users key is different, thickness is 2.5mm and cutting depth is 1mm.
so users can use define key data first ,named ‘HU56R-1_U’,later Xhorse will find a better solution.
1.connect PC to Condor machine
2.use attached software, sync’HU56R-1_U’ to condor xc-mini key cutting machine
3.select ‘cut by bitting’—enter ‘HU56R’ you will find HU56R-1_U,then cutting.
Note: Contact Xhorse engineer to get the define key data, skype: Xhorse-Support2.