ابزار Xhorse VVDI

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

ابزار Xhorse VVDI

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

Xhorse VVDI2 All Update Errors in Upgrade Kit

 Here is the working solution to Xhorse VVDI2 key programmer various update error codes via Upgrade Kit.

 

Error Code 1:

Error code (22:03:00:00:00) Read Internal Error

vvdi2 Error code (22:03:00:00:00) Read Internal Error

Error Code 2

Error code (402:03:02:A5:0E) Upgrade Failed

vvdi2 Error code (402:03:02:A5:0E) Upgrade Failed

as well as other update failed error codes,  follow solution below:

1. Change another USB cable, other COM ports or laptop

2. Try to Fix internal error 1 or 2 in Xhorse upgrade kit,

Then update vvdi2 again.

vvdi2 fix internal error

3. If still fails after doing all the above, vvdi2 is damaged, need to send back for repair.

 

www.vvdishop.com

How to Solve VVDI2 Update Error 402?

 Problem:

Hello, I failed to update xhorse vvdi2 full kit to v7.0.0, it displayed error code 402.03.02.A5.0E

xhorse-vvdi2-update-error

VVDISHOP.COM Working Solution:

xhorse-vvdi2-fix-internal-error

Try the Repair function to fix internal error 1 or error 2. 

Then update vvdi2 again using Xhorse upgrade kit.

If still fail to update, change other COM ports or another laptop.

Any questions feel free to contact vvdishop.com customer service.

Program Toyota XM smart key with Xhorse VVDI2

 How-to: generate Xhorse Toyota XM remote (8A) using VVDI2 key programmer.

 

generate-xhorse-xm-smart-key-with-vvdi2-1

The XM smart key does not come with key shell.  key shell is available on ebay or aliexpress.

Insert xhorse smart key into vvdi2.

In xhorse vvdi2 software, select Asia->Toyota->All remote-> 2110 314.35/315.10 type, tick From default database and press Prepare proximity remote

generate-xhorse-xm-smart-key-with-vvdi2-2

Read the following requirement:

The function requires special XM proximity remote and network connection.
It needs some bonus points for each XM proximity first use. (200 points)
Using Toyota proximity remote does not have bonus points.

Insert prox into vvdi2 coil before continue

generate-xhorse-xm-smart-key-with-vvdi2-3

Identify remote information

generate-xhorse-xm-smart-key-with-vvdi2-4

generate-xhorse-xm-smart-key-with-vvdi2-5

Synchronize with server

generate-xhorse-xm-smart-key-with-vvdi2-6

Calculating requires 5 seconds.

generate-xhorse-xm-smart-key-with-vvdi2-7

Preparing XM remote until succeeded

generate-xhorse-xm-smart-key-with-vvdi2-8

 https://www.vvdishop.com/service/xhorse-vvdi2-program-toyota-xm-proximity-remote.html

VVDI2 A2SHB resistor component pinout

Here’s the customer solution to Xhorse VVDI2  not connected by OBD2 problem.

Disclaimer:
You are at your risk.

Problem:
Today my VVDI2 is no longer connected by OBD2, it has been short to negative.
This component was burned (make smoke), I took it and at least UDS protocol is working, I did not test in Kline.
Can you tell me which component to send and replace on the board?
vvdi2-not-connected-obd2-1

vvdi2-not-connected-obd2-2

vvdi2-not-connected-obd2-3
DIY Solution:
A2SHB component should be replaced.
vvdi2-replace-a2shb-resistor
A2SHB Datasheet – Vds=20V, N-Channel MOSFET
Part Number : A2SHB
Function : N-Channel 1.25-W, 2.5-V MOSFET
Package : SOT23 Type
Manufacturers : Vishay, NXP
Image :
a2shb-resistor
Description
N-channel enhancement mode field-effect transistor in a plastic package.

Pinout
a2shb-resistor-pinout
Features
1. Very fast switching
2. Logic level compatible
3. Subminiature surface mount package.
Application
1. Battery management
2. High speed switch
3. Low power DC to DC converter.


Suggestion:
If you have any problem of Xhorse tools, please contact us at any time.

Will VVDI2 do Audi A3 8P 2005 BKC cluster change?

Audi A3 8P 2005 BKC change cluster with VVDI2 OK? If not, how to do?
Question:
Audi A3 8P 2005 BKC, i want to change the cluster, but vvdi2 wouldn’t read the old IC.
vvdi2-audi-a3-8p-change-cluster-1

Answer:
It’s 8P VDO dash with Fujitsu. VVDI does not support them. Read Immodata from ECU (CS, Login, MAC and immo id) get 7th byte from key and transfer to new dash.

Question:
Thanks your reply. I got all data what i need.
From ECU: CS 6 byte, PIN, MAC, VIN, ImmoID, powerclass
From keys: transponder ID and CS 7 byte
After transferred to the new dash, all ok on bench, no SAFE
Installed to the car, SAFE on dash.
vvdi2-audi-a3-8p-change-cluster-2
vvdi2-audi-a3-8p-change-cluster-3
vvdi2-audi-a3-8p-change-cluster-4
I did a short video, no immo fault, strange

Answer:
If you disconnect ECU, does SAFE go away and you get mileage instead?
If so, I guess it is related to powerclass or MAC.
Upload your immoblock from dash and EDC16 eeprom dump or data.

ECU confdata and cluster immoblock here
vvdi2-audi-a3-8p-change-cluster-5

ECU cluster:

Answer:
Your MAC is wrong:
971F1053 is correct one.
Status : 14000051FF is fine

Back to the car and test:
vvdi2-audi-a3-8p-change-cluster-6

Finally, Works fine.
vvdi2-audi-a3-8p-change-cluster-7 
Credits to @exe123 and @ zolee33 from DK forum.

http://blog.vvdishop.com/audi-a3-8p-2005-bkc-change-cluster-with-vvdi2-ok/