This would be the case with 2017 cars
Hi guys,
In very new VAG PQ cluster firmwares (for example 920 870 SW11xx) it is possible that the first byte of config in immo area is 65 (which is normally 21).
When bit 2 (value 4) in this byte is set the cluster cannot detect a normal ID48 transponder, so it seems to check for some other type of transponder.
Does anyone know if latest PQ VAG clusters use a different type of transponder?
Rgs H2Deetoo
This would be the case with 2017 cars
I tried to program a key to a 2017 VW Caddy and I can not program a transponder, doesn't read the key.
I tried 4 X ID48 and nothing, and this transponder are perfect because I used with others cars... So maybe you are right
The config of this caddy was:
2D0106220100
Last edited by H.Wessel; 20th March, 2018 at 11:29 PM.
We're you able to read it like a 2016? I have been asked to do a 2017 jetta (north American so not mqb) with key from dealer but it reads like an id88 mqb key.... I haven't done it yet because I don't want to damage anything.
If it has the same 24c64 cluster as a 2016 I can give it a try to see if it adds the dealer key but want some reassurance before risking anything
Sent from my SM-G930W8 using Tapatalk
dmp (20th March, 2018), milehighlockdoc (18th July, 2019)
2D = 0010 1101 which means bit 2 (value 4) is set (same as 65).
So indeed this is exactly what I'm facing as well
I can confirm these new transponders are ID88, the same as used by MQB clusters !
When bit 2 is set, then the cluster only detects ID88 transponders.
When bit 2 is cleared, then the cluster detects ID48 transponders.
This is from SW11xx for both black/white and color.
amigokola (25th November, 2018), dijo (12th November, 2019), DreamDancer (12th November, 2019), Faraday (3rd January, 2022), H.Wessel (21st March, 2018), HeXeN (21st March, 2018), jonny r (21st March, 2018), just4upal (12th December, 2021), milehighlockdoc (18th July, 2019), nazz2 (2nd December, 2022), p1et (3rd June, 2019), u.s (6th April, 2018)
If you clear bit 2 then ONLY ID48 is detected, ID88 will NOT be detected.
I only found ID88 in complete key with remote.
the wallet key for MQB Polo has glass transponder. so guess they will be available
I did a 2017 Jetta kessy AKL (with dealer key since I couldn't even find a source for a blank). Dash prepared like a 2016 with 24c64 eeprom. I added key on the bench (knowing I will likely have to re-add it in the car for kessy to work) in order to verify.
Key was programmed as tested on the bench.
Notably, when I tried to 'add key' (knowing kessy wouldn't work until I learned it), it added a chip id FFFFFFFC (not the proper ID). I had to add it with immo data to have it program to the dash properly.
To confirm, the dash acts just like a 2016 Jetta, just requires the new chip to function.
id FFFFFFFC is normal when you try to read an ID88 transponder as ID48.
So make sure you use a high enough firmware version (SW11xx) and enable ID88 transponders (set bit 2 (value 4) as explained).
Last edited by H2Deetoo; 4th June, 2019 at 11:37 AM.
Hi all,
I have the same problem as H. Wessel. I tried to add a Megamos ID 48 Can transponder to a 2017 NEC24C64 dashboard without success. Dashboard do not recognize transponder.
Please could someone explain how to change the bit on the config example below ? I would like to clear bit 2, so that the cluster detects ID48 transponder as H2Deetoo wrote.
Config: 2D0106220100
Sorry for my question, I am an bloody beginner...
Thanks in advance.
re, Andi
2D hexadecimal = 00101101
So clear bit 2 results in 00101001 which is 29 hexadecimal.
amigokola (25th November, 2018), Andi 85 (25th November, 2018), autoTkey (16th February, 2021), milehighlockdoc (18th July, 2019), paulsta (18th July, 2019)
Thanks for your answer and explanation H2Deetoo.
Bookmarks