I usually do the Golf 7 Gti MQB with my VVDi 2.
Last week had one which was around 2014 model or 2015.
VVDI identified cluster but failed to do SECURITY login to read immo data. This was spare key only so usually we don't have a problem. But this time it failed. I tried Login 1 and Login 2. ALso tried the COntinental and other option and all failed.
I then reluctantly took my X300 DP Plus which usually I don't use on MQB because it never worked on any thus far and Amazingly it did this cluster. So is it a bug in the VVDI2 or is it just some software version that was overlooked by Xhorse or what?
The week before I used my VVDI2 and VAG helper to do a spare key on Golf 7 GTI with Virtual cockpit and worked 100%. But this week it dissappointed me especially since it wasn't a very late model. Generally my VVDI2 did all the older models and it's the first MQB like that it failed. This wasn't even virtual cockpit but standard DASH.
Not sure if it's a bug in this latest Software version which came recently......
rob h (14th October, 2019)
Good afternoon, I want to add a second key to VW Jetta 2017, VVDI2 defined the system as NEC + 24С64 with an MQB key, native key 5K0837202BP, bought a new one with the same number. VVDI2 defined the native key as MQB 48, the new key as ID 48. When I try to make a dealer key, VVDI2 writes that the transponder was not found, can someone tell me how to program the system NEC + 24C64 with an MQB key correctly, maybe to me need to prepare a new key somehow?
Last edited by zimir; 15th October, 2019 at 11:45 AM.
There is different option in vvdi. Instead of choosing 24c64 select nec24c64MQB
I chose this option
Maybe you have the wrong transponder key??
Sent from my MI MAX 3 using Tapatalk
Native key:
0-02-0a-6b887cbada73a32336bac279a36ff7c15a8f44b73a772072978c5eabc6031f6c_d3d48484.jpg
New key:
0-02-05-1f57c50ec5de09bb9a69704c4214cb3b5ddb5d0f8c5fba11d707fa2439e23ea1_2964810b.jpg
they are identical
---------------------------------------------
this is how VVDI2 defines them;
Native key:
0-02-05-dfac91b1dd2722595a533a97f8ea18d917823dfbdec99a0fdaec3ed294e0d9b9_beca14.jpg
New Key:
0-02-05-04daad4ef9c124a0d709e3cd839b51e7005bc73f693ed68710a7fb89960cfb99_c2d28208.jpg
maybe VVDI2 does not correctly determine the transponder or to me need to somehow right prepare a new key before programming
So finaly got around to test the Kline gallardo 2006 with adapter cable and VVDI2 got some promissing result could read DTC's from almost all modules except Airbag module.
Cluster is RB8 which i expected CCM is 8H0959433K, wanted to see if i could learn a new remote but it didn't let me erase or learn new remote's maybe pin needed? it did see channel 21 but not channel 00 but when testing empty remote spot it said ok but remote did not learn and said save failed. remote is good and new original lambo part. i'll have a go next time my friend comes around again.
gallardo instr.jpggallardo CCM.jpgChannel 0.jpgTest 3.jpgSave 3.jpg
he was also excited that it worked to see DTC's
Last edited by Staafonline; 15th October, 2019 at 01:24 PM.
Maartinj (15th October, 2019)
Any way to program this Passat Smart MQB key yet? (2014 onwards model)
https://3dgroupuk.com/product/view/VGR86ac
Thanks!
Tools owned -
AD100 PRO, Lonsdor, FVDI 18, FVDI 20, VVDI PROG, VVDI2, VVDI MB
CGDI BMW, SuperVag, Renault ECU tool, OBDstar X300 DP Plus, AUTEL im508
VVDI Mini Keytool, KeyDIY KDX2, SBB, ACDP CAS/KVM
Opcom, VCDS pro, Diagbox, Multiecuscan, Forscan, JLR SDD
Hello,
Is there some hero that try to make BMW CAS4 key by OBD with VVDI...Is there that option active on VVDI like they say.
Also how good its working vvdi prog for cas4, is it safe like 100%
Last edited by Alekso; 17th October, 2019 at 11:34 AM.
Yes. If you read few posts up you will see few people done that.
I did few with obd.
Alekso (17th October, 2019)
Bookmarks