Flyobd2 FVDI2 VAG Commander success and fail

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 : ErrorAfter 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

http://blog.obdexpress.co.uk/2016/11/28/flyobd2-fvdi2-vag-commander-success-and-fail/

How to use FVDI Read write MED17 EDC17

FVDI abrites commander for vag can read out the data of MED17, EDC17 engine control unit,can get 6-digit Security Byte and 5-digit login password by reading the data from MEDC17, and get 7-digit Security Byte by reading data from comfort modules.

What need to prepare for FVDI reading/writing MED17 EDC17?
PC, FVDI, USB cable, MEDC17 adapter, dongle, welding iron, solders, several 1K ohm resisters and 12V DC power supply.
(Note: refer to “medc17-pinout.pdf” that shows connections between MEDC17 adapter and MEDC17 ECU.)

Picture 1 shows connections between FVDI, PC, dongle, MEDC17 adapter. Your PC must be online.

How to read write MED17 EDC17 by FVDI?
Step 1: Disassemble MEDC17 ECU, uncover it.
Step 3: Connect FVDI with PC, open VAG 18.0, and enter special functions, and select “EDC17/MED17 Engine Control Unit”. It’s shown as picture 2.

Step 4: Select correct MCU type, and click “CONNECT” as Picture 3.

Step 5: Read what you want to read.
Step 6: Assemble MEDC17 ECU and install it to vehicle.