Let' s take a look at the recent feedback from BMW users on VVDI2:
1. I made a CAS1 BMW yesterday and read the eeprom through the obd to get the key info and cutting code.
2. VVDI2 BMW can directly make keys in BMW ews through obd, or programmers need to read ews dump and make keys.
3. I have a VVDI2 with VAG and BMW authorization.
New key must be programmed in BMW (BMW e90 2008 usa year) without keyless entry.
In original key internal transponder pcf7953 315mhz.
My tip for you: Chinese key only works transponder but remote needs to remove cas and do it on bench in tango or xhorse VVDI but obd method needs to be always original to have a better chance chip is 7945 or 7953 this is 46 Family luck.
4. Xhorse VVDI2 v1.2.1 adds support for MED17 / EDC17 dump tool, supports cloning ECU (menu-> special function-> MED17 / EDC17 dump tool).
But unfortunately only for Condor key cutter users.
5. My VVDI 2 is the full version, not the basic version.
But the function of edc17 is only available for condor cutter user.no for all VVDI2 full version users.
VVDI mb bga has token system, if you have condor cutter 1 day free 1 token, if you don' t have you need to pay.
they are different.
6. I tried mini 2012 lost key CAS3+ on VVDI2.
all the best.
Get ISN from DME, EEPROM from CAS.
And remote programming is successful.
But the car didn' t start I made a mistake, when the VVDI tool asked me if the car was started, I said yes, but the car didn' t start, I thought it might be because the battery was low, but I powered the battery but didn' t try the joy remote Functional, but yellow keys appear on the cluster.
I was then advised to try the blank key position with the 7953 transponder to make the key by the ISN method.
I literally reprogrammed the key and the car started.