Skip to content

transponder chip

Featured Replies

Hi all

 

i've got some new keyfobs adapted to a 2006 mk1 Fabia but the immobiliser will not accept the transponder chips.  they are supposedly ID48 which I thought covered all Fabia mk1s.    Did the chips change?  or have I happened to buy two duff ID48 chips in a row?

 

thanks

justin

You need to get them programmed, RFID chips aren't going to program themselves...

  • Author
Just now, sepulchrave said:

You need to get them programmed, RFID chips aren't going to program themselves...

 

yes.  that's why I mentioned that the immobiliser was not accepting them.  the adaptation was not sticking.

 

however I have now found this was to do with too high a latency on my serial lines and rewritten some open source code to force the adaptation.  this worked and the chips are now programmed.  

It would be good/informative to know how you finally managed to resolve this issue, including the hardware used as keys can be bought - cut to a photo - which I had done to allow access should the keys either get locked in the car but to take them from basically a dumb key to fully functioning would be great.

  • Author

sure Keith

 

to get an eeprom dump I used vag k+can 1.4.  it refused to work reliably for a long time, giving only snippets of the rom.  but just once it connected, maintained the connection and was able to get a full enough dump to decode the SKC. 

 

the issue i think is that the ftdi cable running through a usb c converter into a mac running parallels added too much software latency and the app was disconnecting.  i suspect that if you were using an older windows PC there would not be the same issues.

i then recompiled kw1281test with long timeouts of 10 seconds and issued this command with a key in the lock and the ignition on.

 

dotnet run com4 10400 17 adaptationsave 21 3 01777 

 

this tells the application to open com4 at a baud rate of 10.4k and talk to module 17 to adapt channel 21 to a new value of 3 (3 keys), logging in with the code 01777.

 

this was the output

 

Version 0.80-beta (https://github.com/gmenounos/kw1281test/releases)
Args: com4 10400 17 adaptationsave 21 3 01777
OSVersion: Microsoft Windows NT 10.0.22621.0
.NET Version: 7.0.3
Culture: en-US
Opening serial port com4
Sending wakeup message
Wakeup duration: 2 seconds
Reading sync byte
Keyword Lsb $01
Keyword Msb $8A
Protocol is KW 1281 (8N1)
ECU: 6Y0920981M KOMBI+WEGFAHRSP VDO V02
Software Coding 00401, Workshop Code: 13765
Sending Login block
Sending AdaptationRead block
Received "Adaptation Response" block: 15 00 02 E7 25 00 6C 25 00 6D 1C 00 02 25 00 6B
Adaptation value: 2
Sending AdaptationTest block
Received "Adaptation Response" block: 15 00 03 E7 25 00 6E 25 00 6D 1C 00 03 25 00 6B
Adaptation value: 3
Sending AdaptationSave block
Received "Adaptation Response" block: 15 00 03
Adaptation value: 3
Sending EndCommunication block

 

which shows that the code read channel21, tested writing 3 to it successfully and then committed that write permanently.

 

changing channel21 allows 60 seconds for new transponder IDs to be mated to the immobiliser.  put each key in to the ignition in sequence and turn ignition (not engine) on.  wait a couple of seconds until the immo light stops flashing.  

 

 

the remote open for each fob was done in the normal way (window down, ignition on, put new key in to drivers door, lock the door, remove key, press lock once, press and hold unlock for a couple of seconds. turn ignition off.  

the keyblades I got from keys in the post.  the blank fobs I got off amazon.  I used a hammer and panel nail to drive out the cotter(ish) pin, hammer to bash the new key blade in and to drive the pin back into the blade.  oddly this took a long time (I didn't have my magnifying glass and my eyes don't work that well any more).  

 

hope that helps.

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.