How to Unlock Audi 7945 Key SUCCESSFULLY using FVDI 2 fly obd terminator

Updated news ,FVDI 2 FLY OBD Terminator is update and add  new functions follow these：

1 Unlock Audi 7945 key;

2 Put key into the coil to read and write data (No need to disassemble the key cover);

3 Unlock keys for heaps of times;

How to unlock Audi 7945 key:

Read BCM 2 data by OBD mode

( using with FLY OBD Terminator or with other programmers e.g. Orange 5)

Load data

Put the key in the coil,

Click on the Unlock button;

What else can Fvdi2 do for AUDI cars:

 A4/A5/Q5 2007+ Generation 5 Immobilizer;

1.Read BCM2 Immobilizer Data By OBDII;

2.Generate dealers keys and key learning;

3.Open/close Immobilizer Horn;

4.Recover Emergency data(Data recovery and wake up in the process of reading immobilizer data failure cases);

5.Check the new PCF7945AC (HitagExt VAG);

6.Load decode file (Can generate dealer key and learning key);

7.Load PFLASH and DFLASH file (Can generate dealer key and learning key);

A6/A7/A8/VW Touareg Generation 5 Immobilizer;

1.Read BCM2 Immobilizer Data By OBDII;

2.Generate dealers keys and key learning;

3.Open/close Immobilizer Horn;

4.Recover Emergency data(Data recovery and wake up in the process of reading immobilizer data failure cases);

5.Check the new PCF7945AC (HitagExt VAG);

6.Load decode file (Can generate dealer key and learning key);

Add keymaker for Audi A4/A5/Q5 Generation 5 Immobilizer

can do all key lost, IC is NEC D70F3634;

Add keymaker for Audi A6/A7/A8 and VW Touareg Generation 5 Immobilizer

can do all key lost, IC is NEC D70F3634;

Edit ID of PCF7945AC (Hitag VAG)/ Edit Audi Generation 5 Immobilize deputy factory Key ID;

http://blog.obdexpress.co.uk/2016/12/29/unlock-audi-7945-key-using-fvdi-2-fly-obd-terminator/

Ktag and Kess v2 ecu programming review

Bought a bundle of Ktag and kess v2 last week.

And the kit arrived today. Shipped from China.
Attempting to use the ecu programmers this weekend.
Installed all appropriate software.

I run it on Windows xp

Edit: i successfully tested on some ECUs using the ktag and kess. Used without network connection.

Chinese pcb but high quality, i have this kess and ktag pcb in my old clones ( kess v2 fw: v4.036 and ktag fw: v6.070 and work well without any fault, also work with 24v)

 

kess and ktag tested in old ecus, works perfect (Sim 32, edc15p+, me7.5, me7.5.10, me7.5.30, Edc17c54, etc)

New Protocols Ecu Tested:

Ktag, Ford fiesta 1.6Ecu Siemens EMS2211 Tricore
Reading OK (very fast)
Writing OK
Cheksum correction OK

  
Kess, Toyota Hilux 2.5 D4D Engine, DENSO 175822-887ID OK
WRITING OK
CHEKSUM CORRECTION OK

  Kess write in 2 minutes.

Ktag, Toyota Hilux 2.5 D4D DENSO 175822-887 (needs luck)Reading ok
Wrinting ok
Backup ok
Cheksum Correction ok

    

Kess, Vw Amarok 2.0 163cv OBDII WritingID Ok
Cheksum OK
Writing ok

In short, KESS V2 is perfect for OBD use, while KTag is perfect for Jtag, BDM and all the Boot application (tricore and ST10).

With KESS V2 you programming directly through the OBD port of the vehicle, while with Ktag you need to take apart the ECU and  open it, after you can make the read/write operation.

Many ECU has the advantage that can be read and write from OBD port (so KESS V2 is perfect), but there are lot ECU that need to disassemble from the car and open and this is the case for all the ECU that need to be programmed with Jtag, BDM and Boot protocols, so KTAG is needed. And that is why i bought Ktag and kess v2 together.

(big thanks to masciaro share info to us)

http://blog.obdexpress.co.uk/2016/12/10/kess-v2-for-obd-and-ktag-for-jtag-bdm-boot/