We’e got a new VVDI 2 VVDI II user that give us positive feedback from obdii365.com customer.
Full review as following:
I successfully use VVDI2 to add a key bcm2 on a 2013 audi a5.
2007 Audi A4 B7 RB8 crypto – mileage correction ok
Audi BCM2 add spare key by obd worked fine, and I did one on a 2013 A5 and it worked flawlessly.
A6/Q7 EZS Kessy: Added a dealer key (remote sourced from the dealer) without issues. Seemed to read everything properly but I had a working key to begin with.
2007 Audi A4 B7 RB8 crypto – mileage correction ok
Audi BCM2 add spare key by obd worked fine, and I did one on a 2013 A5 and it worked flawlessly.
A6/Q7 EZS Kessy: Added a dealer key (remote sourced from the dealer) without issues. Seemed to read everything properly but I had a working key to begin with.
Audi A6: Testet with A6 read kessy working, learned new key
Skoda Octavia 2006: got CS & PIN , programmed key fine, but not remote programming.
VW passat. B5: Pulled PIN, programmed key, corrected miles.
VW Passat B6 2009: Pulled PIN but couldn’t get 6 bytes CS, needed comfort dump.
VW Transporter T5 2006 : Pulled PIN Programmed key, no remote programming.
Audi A4 2006 : mileage correction success .
Audi A6 2003: Mileage correction fail. car not start. remove battery terminal. car start.
Skoda Octavia 2006: got CS & PIN , programmed key fine, but not remote programming.
VW passat. B5: Pulled PIN, programmed key, corrected miles.
VW Passat B6 2009: Pulled PIN but couldn’t get 6 bytes CS, needed comfort dump.
VW Transporter T5 2006 : Pulled PIN Programmed key, no remote programming.
Audi A4 2006 : mileage correction success .
Audi A6 2003: Mileage correction fail. car not start. remove battery terminal. car start.
http://www.key-programmer.org/2016/01/18/xhorse-vvdi-2-vvdi2-commander-review-2016-01-18/
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.