ابزار Xhorse VVDI



Xhorse VVDI PROG programmer latest software version V4.8.1 update:

VVDIProg v4.8.1 (2018-3-19)
* This version DON’t need update firmware
+ Add VVDI PROG USER MUNUAL 4.8.1 version in Doc folder
+ Add D80XX, D160XX, M35080XX, M35160XX options in <1-EEPROM&FLASH>-><SPECIAL-FUNCTION>
+ Add XF-RFA(2013) options in <4-IMMOBILIZER>-><JAGUAR>
+ Add CX70(2018) options in <4-IMMOBILIZER>-><CHANGAN>
+ Add KARRY(2015) options in <5-DASHBOARD>-><CHERY>
+ Add BJ20(2016) options in <5-DASHBOARD>-><BAICMOTOR>
+ Add EQUINOX(2018) options in <7-AIRBAG>-><CHEVROLET>

Xhorse 35160DW Chip is used to work with VVDI Prog programmer to read chip M35080, M35080-3, M35080-6, M35080V6, M35080VP, D80D0WQ, 160D0WQ,36160WT,35128WT The manual can be applied to ST chip type: 35080XXX,35160XXX,95XXX.
35160dw-chip
Procedure:
Step 1. read and backup data of 3 areas (memory, LONGID, IDLOCATION) from the original dashboard IC
how-to-use-35160dw-chip
Step 2. write the backup-data to 3 areas on the chip
if the first two lines of the chip need change mileages, pls click on Erase INC” on the bop right corner and then read out data
if the first two lines display all zeros, manually enter a new mileage for change
directly click on Write” then done!

Step 3. solder the fixed chip on the dashboard to check if it starts or not, with or without a red dot


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.
condor-mini-volvo-hu56-error
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.

Note: Contact Xhorse engineer to get the define key data, skype: Xhorse-Support2.

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.
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.
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
vvdi2-audi-a6-q7-kessy-1
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.

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.
vvdi2-audi-a6-q7-kessy-2

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


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:
vvdi-mini-key-tool-toyota-h-chip
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.

Question:
2016 7-Series (BDC system) trying to backup coding by obd using Xhorse VVDI2 BMW and never saw that screen any suggestions?
Error:
Please use BMW E-sys software to read/restore coding!!!
Coding1: Unknown version- SWFL:00005FA8, BDFL:000064F8
unknown G012 type”
vvdi2-bmw-use-eeys-to-code-error-1

vvdi2-bmw-use-eeys-to-code-error-2
 Cause & Solution:
G-Series BDC is not supported with any tool at the moment.
What it means is that you will require another tool to carry out coding. Bmw e-sys dealer kit is an example. Maybe vvdi bmw will be able to help soon.

Xhorse launched new Xhorse app for VVDI Mini Key Tool ,VVDI Key ToolCondor Dolphin, VVDI2 and VVDI MB tools.
new-xhorse-app

1)
How to Combine VVDI Mini Key Tool/Condor Dolphin/VVDI Key Tool in Xhorse App?
Login Xhorse APP, connect device by Bluetooth, enter ‘Device & History’ to combine.
2)
How to combine VVDI2 and VVDI MB TOOL in Xhorse App?
Run upgrade kit, device connect to PC by USB cable
Read device, select’Binding’, customer will get QR code automatically,
Login Xhorse APP, enter ‘Account’–‘Combine device’,
Then scan the QR code to combine to account.



Xhorse VVDI2 BMW VAG PSA key programmer software update to V6.5.0 on April 23th, 2019.
VVDI2 Version: 6.5.0
*** 2019-04-23
*** Require firmware V6.5.0
************************************************** **********************
!!! VVDI super chip is released, require V6.5.0 software !!!
New:
===== VAG V6.5.0 =====
1. Improvement for Audi A6/Q7(IMM4) adapt Gearbox
2. Bugfix for MQB35xx write immo data
3. Improvement for autodetect VAG immobilizer system
4. Bugfix
===== BMW V6.5.0 =====
1. Improvement for FEM/BDC key learning
2. ECU/CAS ISN: Support load and decode B38/B48 ISN with EEPROM dump
3. KM repair: Support ALL eeprom read by VVDIProg M35080, 35160, 35128
4. Bugfix
===== Porsche V6.5.0 =====
1. Bugfix
===== PSA V6.5.0 =====
1. Bugfix
===== Transponder Programmer V6.5.0 =====
1. Support VVDI super chip, you can change to any type in the list:
11, 12, 13, PCF7935, PCF7936, PCF7937, PCF7938, PCF7939, PCF7946, 48, 4C, 4D, 4D(80), 4E, 8A, 8C, 8E 
2. Special transponder: Supprt use VVDI super transponder, it can use reusable, never lock
3. Copy transponder: Support clone 4D transponder
4. Copy transponder: Support clone 4E transponder
5. Copy transponder: Support clone Ford ID83, Kiv ID70
6. Copy transponder: Support clone Toyota H transponder – Require use VVDI super chip
7. Copy transponder: Support clone 8C/4C transponder – Require use VVDI super chip
8. Immobilizer data tool: Euro->Renault->Duster->2010- 95040
9. Immobilizer data tool: Euro->Chevrolet->Silverado->2011 9S08
10. Immobilizer data tool: Asia->Toyota->Corolla->2004 93C66(ID4C)
11. Immobilizer data tool: Asia->SAIC->Roewe 360 95160
12. Bugfix for electronic monitor key
13. Bugfix
===== Copy 48 (96 bits) V6.5.0 =====
1. Bugfix
===== J2534 V6.5.0 =====
1. Bugfix
===== Online Upate Tool V6.5.0 =====
1. Bugfix
===== Quick Start V6.5.0 =====
1. Bugfix

vvdi2-v650



Report: Read + write Renault Megane Power Steering Unit ( ST10F269 ) with Xhorse VVDI Prog programmer success.
vvdiprog-renault-megane-st10f269-1

vvdiprog-renault-megane-st10f269-2

vvdiprog-renault-megane-st10f269-3

vvdiprog-renault-megane-st10f269-4
ST10F269
Log:
Change to 2-MCU–>ST-ST10F–>ST10F269
Check Device…
12V Power Adaptor unconnected
Initialization device…
Initialization success!
Initialization chip…
ID PIC18F4423 0X10D0/ST10F269 0X10D0
Start communication…
Read length:0x40000
Reading…(0%)
Reading…(1%)
Reading…(3%)
Reading…(4%)
Reading…(6%)
Reading…(7%)
Reading…(9%)
Reading…(10%)
Reading…(12%)
Reading…(14%)
Reading…(15%)
Reading…(17%)
Reading…(18%)
Reading…(20%)
Reading…(21%)
Reading…(23%)
Reading…(25%)
Reading…(26%)
Reading…(28%)
Reading…(29%)
Reading…(31%)
Reading…(32%)
Reading…(34%)
Reading…(35%)
Reading…(37%)
Reading…(39%)
Reading…(40%)
Reading…(42%)
Reading…(43%)
Reading…(45%)
Reading…(46%)
Reading…(48%)
Reading…(50%)
Reading…(51%)
Reading…(53%)
Reading…(54%)
Reading…(56%)
Reading…(57%)
Reading…(59%)
Reading…(60%)
Reading…(62%)
Reading…(64%)
Reading…(65%)
Reading…(67%)
Reading…(68%)
Reading…(70%)
Reading…(71%)
Reading…(73%)
Reading…(75%)
Reading…(76%)
Reading…(78%)
Reading…(79%)
Reading…(81%)
Reading…(82%)
Reading…(84%)
Reading…(85%)
Reading…(87%)
Reading…(89%)
Reading…(90%)
Reading…(92%)
Reading…(93%)
Reading…(95%)
Reading…(96%)
Reading…(98%)
Reading…(100%)
End communication…
Operation success

Problem:
I have not been able to read Porsche Cayenne BCM with Xhorse VVDI Prog programmer, followed the wiring diagram to connect BCM and selected chip BCM 5M48H R/W/UNLOCK to read data. vvdi failed me and gave crack error:
Incorrect crack. Please confirm the type of chip. Check the connection and try again”
Photo attached:
vvdi-prog-read-cayenne-5m48h-1

vvdi-prog-read-cayenne-5m48h-2

vvdi-prog-read-cayenne-5m48h-3

vvdi-prog-read-cayenne-5m48h-4

vvdi-prog-read-cayenne-5m48h-5
VVDISHOP solution:
When read Porsche Cayenne 5M48H, don’t select BCM 5M48H R/W/UNLOCK option but CAS4-5M48H-BACKUP instead
VVDI-PROG-5M48H-backup
It reads safe and won’t lost data.

Post starts with VVDI KEY TOOL issues and followed with solution, and finally solved.

I’m having issues here.
could not calculate on line 4d70 on line I tried and tried and tried. So I deleted the app and reinstalled it and cannot remember my username for the life of me. I have tried everything possible. So with the link above complaints I’m having issues again. I can’t send an email because I’m getting the below wrong  <br></div> </div><div class=

تبلیغات

محل تبلیغات شما
محل تبلیغات شما محل تبلیغات شما

آخرین وبلاگ ها

آخرین جستجو ها

Julie Kwame وکیل محمود گنجوی ، وکیل پایه یک دادگستری دانلود مقاله فارسی (¯´ماندگارم`¯) سایت تفریحی و سرگرمی تاپ ناز Christopher شعبان نوروزی