Problem:

I need to program a Ford Focus keylessgo id41 using vvdi key tool plus and xhorse smart watch sw-007. Remote flashing doesn’t work, keytool plus ask to use Prox key. need to replace battery inside or what?

Solution:

Resolved. So there is two battery one for remote one for watch Battery remote is dead.

Have replaced new battery, remote flashing work.

Have to try now. It works perfectly.

If not still not working, update your key tool plus.

 Xhorse vvdi prog programmer software released to V5.2.0 on Sep. 29th, 2022.

VVDIProg v5.2.0 (2022-09-29)
* This version DON’t need update
firmware
+ Add D78F0400,
D78F0401,
D78F0402,
D78F0403,
D78F0410,
D78F0411,
D78F0412,
D78F0413,
D78F0420,
D78F0421,
D78F0422,
D78F0423,
D78F0430,
D78F0431,
D78F0432,
D78F0433
options in
<2-MCU>-><RENESAS-78K>

Free download vvdi prog V5.2.0 software

https://mega.nz/file/9VsGGCKK#JLxc7QgDWBneDqERMkDHADQlCE6GS0GlJ974w8ouAA4

 Problem: 

I failed to write Audi J518 ELV emulator 2010 ol01y with xhorse vvdi prog. It says chip not connected. Any idea?

Solution:

You did wrong wiring connection.

Follow correct wiring diagram here and make good connection again.

Here is the detailed instruction on how to write Audi J518 emulator with vvdi prog

http://blog.vvdishop.com/write-audi-j518-elv-emulator-256-128-with-vvdi-prog/

Information: what programmers to use and from which to stay away when doing Porsche front and rear BCM modules on Cayenne, Macan, Panamera and others.

How to back up MCU memories – D-Flash and P-Flash, read IMMO/Key/CS related information and how to adapt used BCM and ECU modules to the car.

When you are trying to read/unlock/write BCM is dead after.
MCU’s used in these BCM’s is very sensitive (Motorola MC9S12 – 1L15Y, 1N35H, 2M25J, 5M48H)
and some programmers when trying to ID/Read/Unlock/Write these MCU’s tend to corrupt or erase the memories in these MCU’s.
From what we have experienced it is the D-flash and Partition configuration that tends crash.

Here’s the user working experience:

“I have from scrap Cayenne 2014 4.2 diesel – front and rear BCM modules and both ECU’s EDC17CP44
and I also bought used BCM from Macan 2017 to play with.

BCM reading/unlocking:
Cayenne Front BCM with 5M48H MCU, rear BCM with 2N25J MCU and Macan front BCM with 1N35H MCU.
All 3 BCM modules i successfully read with Xhorse VVDI Prog. I removed the diode, 0 ohm resistor,
made the cut to crystal connection and i prefer to desolder the crystal too and 12V power supply to programmer connected.
It had no problem reading the backup of Dflash and Pflash. It did the UNLOCK function without problem.
From there is started to experiment what could be the reason for corrupting these memories.
Using VVDI Prog i used LOCK function to lock back these MCU’s where locked byte is 7D (FE for unlocked).
I have Autel IM608 with XP400Pro programmer and I tried to use that for reading these BCM’s. 2M25J was OK. 5M48H was OK. 1N35H – DEAD.
Autel could not do the backup of the 1N35H, it was unsuccessful unlocking the MCU. After that VVDI Prog could not unlock it too because something in that MCU was already corrupted by Autel programmer.
Had to use “Force Unlock” with VVDI Prog and it worked but Dflash was already wiped, partition config was wiped and Pflash was seriously corrupted.
So i revived that 1N35H memories with what i had backed up before, did the LOCK again and tried again with Autel.
Autel killed it again. I don’t know about other people experience but mine Autel XP400Pro is a “No GO” fot 1N35H MCU.
I am not saying VVDI Prog is the golden tool because some people using VVDI Prog have killed the BCM’s.
For example i tried to read the 1M35H and 5M48H mcu with VVDI Prog but 12V power supply disconnected – it did not read anything. But it also killed these memories like Autel.
Maybe Autel has bad power delivery to MCU where 5M48H tends to survive but 1N35H is way too sensitive and dies.

Immo/ECU/BCM CS:
Since i have both BCM’s and ECU from the same car i did some research on IMMO CS information.
These are only my findings and I have no idea but maybe it can help to adapt used module to the car for someone using this info.

ECU is EDC17CP44 like VAG cars i tried to use VVDI2 to calculate CS from eeprom and flash and it worked.

 VVDISHOP.com provides latest Xhorse VVDI BIMTool Pro software 1.8.5 download free.

===== BMW V1.8.5 (2022-05-23) =====
-Require firmware V1.8.4

This version does not require firmware upgrade.

1. Support mileage calibration for ISTAP CAS3+ via OBDII
2. Support read part eeprom for ISTAP (9389115/9389116/9395656/9395657) via OBDII
3. Support change CAS ISN for ISTAP (9389115/9389116/9395656/9395657) via OBDII
4. Support write customize VO code

Free download vvdi bim tool software 1.8.5

Mega link

Xhorse cloud link

 Problem:

I got a problem with xhorse dolphin xp005 key cutting machine, axis motor is not working and app says error code 56. Any clue?

Solution:

Solution 1:

Clean everything with solvent and don’t update it put an older version so the error is erased and don’t put the last update

Solution 2:

vacuum, clean from shavings. lift it air flip. shake. restart BRUSH. Done. Again, if happened?! Repeat, Do step one.

Feedback:

solution 2 works no problem. xhorse dolphin now is working properly.

 How-to: program a spare key on Audi A8 year 2012 with xhorse vvdi2 vag and keydiy remote.

Procedure:

• Read EEPROM Data
• Read Immo data
• Make dealer key
• Add key
• Learn key

Let’s move to the details.

Turn on the ignition switch with original key
Auto connect type A3/TT/R8
Select type A3/TT/R8

Read EEPROM and Save

Read Immo data and save

Select Make dealer key
Select Audi brands, press Next

Select Add key
Add key succeed

Turn ignition on with the new key
immo indicator doesn’t go off, remote not working

Go to Xhorse vvdi2 Learn key function
Go to Key Learn-> Remote Key Adaptation-> BCM key remote adaptation
Start learning remote control

Turn off key, press UNLOCK in 15 seconds for each key
Learn remote control completed

http://blog.vvdishop.com/add-audi-r8-2012-spare-key-with-xhorse-vvdi2/

 Many people say they cannot find a remote option to generate xhorse xm38 remote key.

This is just an example:

I have a xhorse vvdi key tool max. I bought XM38 smart remote. I want to generate remote for 2017 Prius alpha (Japanese market) but there’s no option here. Making a spare remote. Not sure of the frequency and chip type yet. Just curious if there is just one model vvdi key tool max as global version or are there different for American and Asian market?

Here’s the clue.

Check OEM remote from supplier, chip type (and frequency will usually do).

Generate according to the same type of transponder first, then program the car. If a car can start, then you can adjust the button location and remote freq through toyota vvdi smart key setting on the key tool.

1. First of all, Check customer key transponder type 4D? 8A? A8 A8 or A9 A9.
2. Just generate xm38 with the same type of transponder first then program it to the vehicle. (Better 2 times generated). No need to generate the same frequency and button.
3. If the remote can be programmed to the vehicle and start, later you can change the xm38 remote freq and button function under the toyota smart function key tool.

Tip:
1. Generate xm38 smart with the correct id chip, forget the frequency.
2. Program new key xm38.
3. Adjust xm38 freq and button using key tool later.
4. Test remote function to car.

Here is the useful tips to make a new spare key on late Audi MK1 A1 2018 ID48 key with xhorse vvdi2 key programmer.

Audi a1 2018 id48
Add key
Successfully
Use method 3
Read eeprom save
Read immo data save
Make dealer key
Add key
Aftermarket keys
Just so you no it’s works