This is how to renew 315 868 433 remotes to BMW E & F series, using Xhorse VVDI Prog and PCF79XX adapter version 2.
What do you need prepare for BMW remotes renew:
BMW remote (315MHz/433MHz/868MHz)
What kind of BMW remote VVDI-PROG supports:
BMW E SERIES
ORIGINAL 315 Need PCF79XX adapter
ORIGINAL 868 Need PCF79XX adapter
THIRD PARTY Need PCF79XX adapter
BMW F SERIES
315 REMOTE Need PCF79XX adapter
433 REMOTE Need PCF79XX adapter
868 REMOTE Need PCF79XX adapter
How to connect the BMW remote chipuse to PCF79XX adapter:
Put the chip in the IC socket
Desolder the original battery before writing the file
BMW-E-SEIRES-THIRD-PARTY-REMOTE-RENEW-CHIP: PCF7953/PCF7945
BMW-E-SEIRES-THIRD-PARTY-REMOTE-RENEW-IN-CIRCUIT
BMW-E-SEIRES-ORIGINAL-REMOTE-RENEW-CHIP: PCF7953/PCF7945
BMW-E-SEIRES-ORIGINAL-REMOTE-RENEW-IN-CIRCUIT
BMW-F-SEIRES-REMOTE-RENEW-CHIP: PCF7953
BMW-F-SEIRES-REMOTE-RENEW-IN-CIRCUIT
PCF7953/PCF7945 adapter version 2 required!!!!!!!!!!!!!
How to renew BMW remotes with VVDI Prog:
This is a BMW remote review from a customer who has good success.
I did renew 2 keys! Renew BMW series E 868 key – 100% OK using vvdi prog v4.6.0. Both worked and now are programmed to cars!
Only thing you need to disconnect from PCB is battery while writing the renew file.
I think that is only for those who have older version of that adapter. Older version came with 33 ohm resistor and later they decided that it is not needed and newer adapters like mine came with 0 ohm resistor that is just connecting both sides together without resistance.
If you have that 33 ohm resistor then remove it and short-connect it.
If you have 0 ohm resistor, then don’t mind that first box in connection diagram. It’s not for you.
I did it in circuit.
http://blog.vvdishop.com/vvdi-prog-v4-6-0-renew-pcf79xx-remotes/
If you have Xhorse VVDI2 VAG key programmer to add dealer key on VW Transporter/Caravelle T5 2011, but not work, you must read this post, the problem is finally solved.
Problem description:
VW Transporter/Caravelle T5 2011. Had an existing working key and used Xhorse VVDI2 to make a dealer key on a UDS cluster but something went wrong or more likely I did something wrong. It says 2-2 on the cluster and lights go off as if programmed but once cranked it starts and dies and the glow plug indicator light flashes. I stripped the cluster and tried with putting the cluster in to service mode but still much the same. With AD100 it says 2 keys coded and cluster in Mode 7. A friend came with his Zedfull and recoded in both keys and it said precoding ok but still the same issue. The dump of the original 24c64 and the backup I first made are attached and I’d appreciate any advice or help on this. Thanks everyone
folder: Transporter T5 24c64 Original Read
Folder: Transporter T5
Advice:
Config: This value contain car manufacture, key number, immobilizer status (new, learned, closed), keyless or not etc.
Your immo status is likely changed, did you press the reset immo button.
When did you made the 24c64 backups.
After entering service mode true obd, or after your keylearning procedure?
Question:
The initial backup (small file)was made before I made the key but I read the 24c64 only after it wouldn’t start. Any idea how to change the config from o7 to 06 again?
Instruction guide by senior:
go in to service mode by obd.
read immo data.
change the conf 7 in to 6.
press, write immo data.
press, reset instrument.
that should do it.
Finally! Solved
Thanks everyone. Yes it was me being stupid, I think I actually wrote the 24c64 complete file back instead of the smaller immo file. Did as advised and problem solved.
http://blog.vvdishop.com/solved-vvdi2-make-a-dealer-key-on-vw-transporter/
Xhorse VVDI2 BMW is BMW professional key programmer tool that covers full functions of BMW Multi Tool,and which is better than Multi Tool. Software and firmware both online upgrade-able.
VVDI2 BMW includes BMW OBD and CAS4 authorization, and VVDI2 BMW software language: English, Italian, Spanish, Dutch, Hungarian.
VVDI2 BMW can support not only key programming,but also km,some can do via OBD,some need CAS Plus,some need by eeprom way,like CAS4,needs to use VVDI Prog to read eeprom data,then use with VVDI2 BMW.
Xhorse VVDI2 BMW Key Programmer Feedback:
1) Cars that I have successfully done with VVDI2
2005 BMW E87 CAS3
2006 BMW E90 CAS3
2003 BMW E60 CAS2
2010 Audi A5 with Keyless Entry
2011 Audi A3
2009 VW Golf mk6
2) I tested my vvdi2 on 2008 bmw m6 today. It worked flawlessly and was a bit quicker than multi-tool.
3) I did a perfect job on 2010 bmw X5 with ISTAP today. I downgraded CAS ( I backed up eeprom with xprog first) and then retrieved key info OK. Adding key was a brieze after that. Cleared all errors, synchronized ELV. DONE
4) Hi i yesterday have bmw f10 2012 year ,read cas4+, change, write back all ok work .happy 100%
5) BMW cars I have completed with VVDI 2.
– EWS 2
– EWS 3
– EWS 3+
– EWS 4
– CAS 2
– CAS 3
– CAS 3++ (ISTAP)
I think some people need to do more research before blaming tools.
Credit to VVDI2 BMW users from DK forum.
http://blog.vvdishop.com/xhorse-vvdi2-bmw-key-programmer-feedback/