topblog Ivoire blogs


How to build a Power Supply for BMW ICOM

Best way “I” would build a power supply for icom bmw, buy OBDII Extention, Go to your local salvage place and buy BMW OBDII+20 Pin plug+wires(cut)
Then buy power plugs (male and female) from your local electric store and DIY your final product to this forum how much it cost you at the end


This is BMW ICOM A2 OBD+20pin cable


Icom 20pin to 16pin cable




16pin J1962 obd2 car proprietary connector at bmw


used in all BMW models produced after 2000’s


PIN Signal Description
pin 1 +12v ignition (in run or start)
pin 4 CGND chassis ground
pin 5 SGND signal ground
pin 7 ISO 9141-2 K-line engine (iso-914 ans iso-14230), automatic transmission diagnostic (in some models)
pin 8 ISO 9141-2 K-line ike/kombi, abs, abs/asr, abs/abd, esp, dsc, airbag and other diagnostic equipment
pin 9 TD/RPM engine rotation speed
pin 15 ISO 9141-2 K-line k-line of iso 9141-2 and iso 14230-4
pin 16 +12v battery power


Pinout status: +0 / -0


20pin car proprietary connector at the car side


used in all BMW models in 1988-2000’s

PIN Signal Description
pin 1 engine rotation speed TD
pin 2 OBDII diagnostic  
pin 7 oil service and inspection reset  
pin 11 external starter turn on  
pin 14 battery power  
pin 15 ISO 9141-2 L line RXD- Diagnostic data link
pin 16 ignition +12v  
pin 17 USI 8141-2 k line n/c?
pin 18 PGSP Programming line  
pin 19 GND  
pin 20 ISO 9141-2 K line TXD- Diagnostic data link


Pinout status: +6 / -1


VVDI2 VAG prepare new dealer key for 5th immo vag

It’s vvdi2 manual of how to use VVDI2 VAG to make a dealer key for vag vehicles with the 5th immobilizer system.


Type: VAG 5th immo transponder or OEM key


Cars: A4 (2009-), A5, Q5, A6 (2012-), A7, A8(2011-), Touareg (2011-)



If you want prepare a new dealer key, you must know the total 16 bytes CS. So we need read BCM2 data from BCM2 module (J393)


Step 1: Choose a method to read BCM2 data

so far, most cars support read BCM2 data via OBDII (Add key and lost all key all support). (No. 1), read BCM2 need enter service mode, the cluster may become dark under reading.


Useful tips:

– Error “read data length error” in OBD read method:

you need read BCM2 data with 5th BDM Programmer (No. 2)


– OBD Read BCM2 for lost all key:

It need disconnect BCM2 power (2 interfaces) for a few seconds. Just follow program message


– Fail to read BCM2 data:

Under OBD Read BCM2 for lost all key process, if cannot read BCM2 data after disconnect power or you get disconnect power for next time read, this type may not support OBD read without working key, you need read BCM2 data with 5th BDM Programmer


– switch OFF or ON:

Before you read BCM2 via OBDII, you’d better switch OFF/ON ignition again, Keyless cars press START/STOP button again to switch ON. Else may enter lost all key mode, of course, if reading success, it is also right BCM2 data


– How many times to read BCM2 data:

BCM2 data is always for the same car. So you only need read one time. As long as you have the BCM2 data, you don’t need to read again, no matter key learn, no matter when



BCM2 (J393) module position



BCM2 (J393) module remove plug



introduction for 5th BDM Programmer



BCM2 (J393) front connect line



BCM2 (J393) back connect line




Step 2 – Verify key lock status with the “Check Key Status” button (No. 3)

Check key is locked or not, is keyless key or not. For there are many OEM keys on the market, keyless key result may not accurate


Step 3 – Make Dealer Key (No. 4):

Click on “Prepare dealer key”

Request load BCM2 data (step 1)

Put the programmable key into VVDI2 key programmer

Prepare the dealer key and wait complete


Useful tips:

– key is locked:

After making key successfully. The key is not locked before you learn it. So you can make key for other cars before key learning. Once learn the key, it locked


– need a working key or not:

Make key for A4/Q5/A5 don’t need a working key

Make key for A6/A7/A8/Touareg need a working key

(if you don’t have working key, the keyless function will not work )


– make OEM keys:

You can unlock the locked OEM key in “Transponder Programmer->Other Key Tool”. (Most OEM keys is not support unlock, it can be prepared again with lock status, then learn it as normal). If the OEM keys support change ID, you can make an OEM key, the method is same as 4th immobilizer cluster OEM key, select one original key position and continue


Step 4 – key learning through VVDI2 VAG (No. 5)

Connect the VVDI2 VAG commander to the car,

Prepare all the key for this car

Insert one key to the switch ignition

Input the key number you want to learn

Click on “key learning”

Request load BCM2 data (step 1)

Complete the key learning


At the last, you will get a message insert every key to learn, don’t press “OK” until you get message “Learn key success” at the bottom. If you press “OK” before that message will cause key learn failure. When you get that message, the cluster will show “x-y”, “x” is the learned key number and “y” is the total learning number. If you learn 2 keys, first will show 0-2, after learn 1 key, it show 1-2, after learn 2 keys, it show 2-2. After success learn key, it will show KM


Step 5 – Alarm ON:

Open the immobilizer alarm, you are advised to open it after key learn


Step 6 – Alarm OFF:

Close the immobilizer alarm




Flyobd2 FVDI2 VAG Commander reviews

I bought Flyobd FVDI generation 2 for VAG group vehicles. The only improvement they did was on vag group and that improvement did affect other software.  The rest = 0 or bad.

Hmm… Maybe i can also say nothing new on on VAG. it’s v24 also. Only this time it can process info over the Internet and it function same as avdi v24 but does not support JC cluster and cannot read immo data for Audi from 2009 up , and also when trying to get cs for key coding after processing data over internet it shows 00 00 00 00 00 00 00
What i did on VAG vehicles with this Fvdi2 vag commander:


– Brand/Model of car : VW Caravelle
– Year of car : 2001
– Feature in relation : transponder programming from dump
– Version of FVDI : Tagkey Tool 6.2
– Result : Error (4pcs. PCF7935 damaged)
Dump recognized good, pin readed correctly. Problem solved programming prepared PCF7935 to VW id44 via OBD.


– Brand/Model of car : Skoda Roomster
– Year of car : 2006
– Feature in relation : pin read and key programming
– Version of FVDI : VAG 24.0
– Result : OK


– Brand/Model of car : golf 6 TDI 2012
– Feature in relation : with CS (component protection ) , pin read and key programming
– Result : ok
– Brand/Model of car : VW Passat 3C 2.0tdi
– Year of car : 2007
– Feature in relation : learning key
– Version of FVDI : OLD 18
– Result :ok


– Brand/Model of car : VAG
– Year of car : 1998-2002
– Feature in relation : pin read from EDC15
– Version of FVDI : VAG 24.0
– Result : Error (can’t connected)


– Brand/Model of car : Audi A4
– Year of car : 2003
– Feature in relation : pin read and key programming cluster RB4 crypto
– Version of FVDI : VAG 24.0
– Result : Error
After read pin, eeprom content in RB4 faulty. Car don’t recognized original key. Solved by write content saved after first read.


– Brand/Model of car :Seat Leon 1PA

– Year of car : 2011
– Version of FVDI : fvdi 21
– Feature in relation :add new key
– Result : successfully
I would only suggest fly company to focus more on individual software like vag group and deliver like Xhorse VVDI2 than try to do many and only anger and frustrate customers