kw1281test: A Free VDS-Pro / VagTacho Alternative

[gmenounos]

Seems like RB8 isn't quite the same as RB4

Is there anything else you want me to try?

When you have a chance, could you try a few more times and verify that this command always returns "Controller did not wake up"
.\kw1281test COM6 10400 17 DumpRBxMem 66560 1024

and this one wakes up the controller and says "Protocol is KW 2027 (8N1)"?
.\kw1281test COM6 10400 17 ReadIdent

Thanks.

 

[tr7]

When you have a chance, could you try a few more times and verify that this command always returns "Controller did not wake up"
.\kw1281test COM6 10400 17 DumpRBxMem 66560 1024

and this one wakes up the controller and says "Protocol is KW 2027 (8N1)"?
.\kw1281test COM6 10400 17 ReadIdent

Thanks.

Nps,

I've tried it now a number of times and in a number of different cars. TDI and TFSI it doesn't matter the same responses

I tried it with ignition on, ignition off, tried it immediately after clocked light up and also giving it a minute to have fully 'woken up'.

The same responses each time below.

Does it waking up at all with ReadIdent give you any indication of what to try next?

Regards,
Tim

Version 0.81-beta (https://github.com/gmenounos/kw1281test/releases)
Args: COM6 10400 17 DumpRBxMem 66560 1024
OSVersion: Microsoft Windows NT 10.0.19044.0
.NET Version: 7.0.4
Culture: en-GB
Opening serial port COM6
Sending wakeup message
Wakeup duration: 2 seconds
Reading sync byte
Retrying wakeup message...
Wakeup duration: 2 seconds
Reading sync byte
Retrying wakeup message...
Wakeup duration: 2 seconds
Reading sync byte
Caught: System.InvalidOperationException Controller did not wake up.
Unhandled exception: System.InvalidOperationException: Controller did not wake up.
   at BitFab.KW1281Test.KwpCommon.WakeUp(Byte, Boolean) in C:\Users\gmeno\src\kw1281test\KwpCommon.cs:line 63
   at BitFab.KW1281Test.Tester.Kwp2000Wakeup(Boolean ) in C:\Users\gmeno\src\kw1281test\Tester.cs:line 48
   at BitFab.KW1281Test.Tester.DumpRBxMem(UInt32, UInt32, String) in C:\Users\gmeno\src\kw1281test\Tester.cs:line 426
   at BitFab.KW1281Test.Program.Run(String[]) in C:\Users\gmeno\src\kw1281test\Program.cs:line 238
   at BitFab.KW1281Test.Program.Main(String[]) in C:\Users\gmeno\src\kw1281test\Program.cs:line 26

Version 0.81-beta (https://github.com/gmenounos/kw1281test/releases)
Args: COM6 10400 17 ReadIdent
OSVersion: Microsoft Windows NT 10.0.19044.0
.NET Version: 7.0.4
Culture: en-GB
Opening serial port COM6
Sending wakeup message
Wakeup duration: 2 seconds
Reading sync byte
Keyword Lsb $6B
Keyword Msb $8F
Protocol is KW 2027 (8N1)
Caught: System.InvalidOperationException Received complement $68 but expected $E8
Unhandled exception: System.InvalidOperationException: Received complement $68 but expected $E8
   at BitFab.KW1281Test.KwpCommon.ReadComplement(Byte) in C:\Users\gmeno\src\kw1281test\KwpCommon.cs:line 117
   at BitFab.KW1281Test.KwpCommon.WakeUp(Byte, Boolean) in C:\Users\gmeno\src\kw1281test\KwpCommon.cs:line 95
   at BitFab.KW1281Test.Tester.Kwp1281Wakeup(Boolean ) in C:\Users\gmeno\src\kw1281test\Tester.cs:line 32
   at BitFab.KW1281Test.Program.Run(String[]) in C:\Users\gmeno\src\kw1281test\Program.cs:line 256
   at BitFab.KW1281Test.Program.Main(String[]) in C:\Users\gmeno\src\kw1281test\Program.cs:line 26

 

[dpspc]

Hey guys I own a Golf MK4 3-door from '01 with the CCM '1J0 959 799 AH'. I'm trying to get the windows to open/close with the fob and I've been having some trouble working with the kw1281test. I've managed to find which adresses and values I need to change and when I try to read the eeprom in those values most of the times it doesn't work. First time it worked like it was suppose to:

Version 0.80-beta (https://github.com/gmenounos/kw1281test/releases)
Args: COM3 9600 46 ReadEeprom 04295
OSVersion: Microsoft Windows NT 10.0.19045.0
.NET Version: 7.0.0
Culture: pt-PT
Opening serial port COM3
Sending wakeup message
Wakeup duration: 2 seconds
Reading sync byte
Keyword Lsb $01
Keyword Msb $8A
Protocol is KW 1281 (8N1)
ECU: 1J0959799AH 2K Zentral-SG Komf. 0001
Software Coding 00256, Workshop Code: 01317
Sending Login block
Sending ReadEeprom block (Address: $10C7, Count: $01)
Received "Read EEPROM Response" block: 48
Address 4295 ($10C7): Value 72 ($48)
Sending EndCommunication block

Right after, I try the same command and it doesn't work anymore, just returns this instead:

Version 0.80-beta (https://github.com/gmenounos/kw1281test/releases)
Args: COM3 9600 46 ReadEeprom 04295
OSVersion: Microsoft Windows NT 10.0.19045.0
.NET Version: 7.0.0
Culture: pt-PT
Opening serial port COM3
Sending wakeup message
Wakeup duration: 2 seconds
Reading sync byte
Keyword Lsb $01
Keyword Msb $8A
Protocol is KW 1281 (8N1)
Caught: System.InvalidOperationException Received block end $0F but expected $03
Unhandled exception: System.InvalidOperationException: Received block end $0F but expected $03
at BitFab.KW1281Test.KW1281Dialog.ReceiveBlock() in C:\Users\gmeno\src\kw1281test\KW1281Dialog.cs:line 392
at BitFab.KW1281Test.KW1281Dialog.ReceiveBlocks() in C:\Users\gmeno\src\kw1281test\KW1281Dialog.cs:line 351
at BitFab.KW1281Test.KW1281Dialog.Connect() in C:\Users\gmeno\src\kw1281test\KW1281Dialog.cs:line 91
at BitFab.KW1281Test.Tester.Kwp1281Wakeup(Boolean ) in C:\Users\gmeno\src\kw1281test\Tester.cs:line 39
at BitFab.KW1281Test.Program.Run(String[]) in C:\Users\gmeno\src\kw1281test\Program.cs:line 256
at BitFab.KW1281Test.Program.Main(String[]) in C:\Users\gmeno\src\kw1281test\Program.cs:line 26

EDIT: I've found out that unplugging the usb cable and plugging it back in between commands would make it work.
I've already changed all of the values for :

1J0 959 799 AH 046 Sedan
Address Old New Remark
04295 138 64 This memory address added to keep the rear trunk handle from locking the car
04283 138 64
04289 138 2
08628 242 246 driver side front window
12724 250 254 passenger side front window

and the windows still don't open/close with a long press

 

[gmenounos]

Nps,
I've tried it now a number of times and in a number of different cars. TDI and TFSI it doesn't matter the same responses

I tried it with ignition on, ignition off, tried it immediately after clocked light up and also giving it a minute to have fully 'woken up'.

The same responses each time below.

Thanks for doing all that testing. I've published a new release: https://github.com/gmenounos/kw1281test/releases/tag/v0.82-beta

Can you download it and try this new command:

.\kw1281test COM6 10400 17 DumpRBxMemOdd 66560 1024

 

[tr7]

Thanks for doing all that testing. I've published a new release: https://github.com/gmenounos/kw1281test/releases/tag/v0.82-beta

Can you download it and try this new command:

.\kw1281test COM6 10400 17 DumpRBxMemOdd 66560 1024

Version 0.82-beta (https://github.com/gmenounos/kw1281test/releases)
Args: COM6 10400 17 DumpRBxMemOdd 66560 1024
OSVersion: Microsoft Windows NT 10.0.19044.0
.NET Version: 7.0.5
Culture: en-GB
Opening serial port COM6
Sending wakeup message
Wakeup duration: 2 seconds
Reading sync byte
Keyword Lsb $6B
Keyword Msb $8F
Protocol is KW 2027 (8N1)
Sent: 82 17 F1 1A 94 38 (readEcuIdentification)
Caught: System.TimeoutException The operation has timed out.
Unhandled exception: System.TimeoutException: The operation has timed out.
   at System.IO.Ports.SerialStream.ReadByte(Int32)
   at System.IO.Ports.SerialStream.ReadByte()
   at System.IO.Ports.SerialPort.ReadByte()
   at BitFab.KW1281Test.Interface.GenericInterface.ReadByte() in C:\Users\gmeno\src\kw1281test\Interface\GenericInterface.cs:line 36
   at BitFab.KW1281Test.KwpCommon.ReadByte() in C:\Users\gmeno\src\kw1281test\KwpCommon.cs:line 104
   at BitFab.KW1281Test.KW2000Dialog.ReceiveMessage() in C:\Users\gmeno\src\kw1281test\Kwp2000\KW2000Dialog.cs:line 199
   at BitFab.KW1281Test.KW2000Dialog.SendReceive(DiagnosticService, Byte[], Boolean ) in C:\Users\gmeno\src\kw1281test\Kwp2000\KW2000Dialog.cs:line 122
   at BitFab.KW1281Test.Cluster.BoschRBxCluster.SecurityAccess(Byte) in C:\Users\gmeno\src\kw1281test\Cluster\BoschRBxCluster.cs:line 32
   at BitFab.KW1281Test.Cluster.BoschRBxCluster.UnlockForEepromReadWrite() in C:\Users\gmeno\src\kw1281test\Cluster\BoschRBxCluster.cs:line 14
   at BitFab.KW1281Test.Tester.DumpRBxMem(UInt32, UInt32, String, Boolean ) in C:\Users\gmeno\src\kw1281test\Tester.cs:line 433
   at BitFab.KW1281Test.Program.Run(String[]) in C:\Users\gmeno\src\kw1281test\Program.cs:line 244
   at BitFab.KW1281Test.Program.Main(String[]) in C:\Users\gmeno\src\kw1281test\Program.cs:line 26

This is what I got. It definitely took the longest out of anything so far so it seems to be doing something

 

[dhangejr]

First THANKS! This is GREAT! No more Russian software and no more vag taco ! You sir are genius!

I have one question regarding the RF ID programing into the immobilizer: do you have to reprogram old RFID chips when programming a new one ?

I thought IMMO3 chips could only be programmed once , I know whenever you program a new remote all the remotes must be present.

I’m just trying to decide how many RFID chips I need

 

[caffeine]

First THANKS! This is GREAT! No more Russian software and no more vag taco ! You sir are genius!

I have one question regarding the RF ID programing into the immobilizer: do you have to reprogram old RFID chips when programming a new one ?

I thought IMMO3 chips could only be programmed once , I know whenever you program a new remote all the remotes must be present.

I’m just trying to decide how many RFID chips I need

My understanding is that any key that has been previously programmed to either the ECU or cluster can be re-used when programming a new key. However, when programming keys to the immobilizer system, all have to be programmed (or reprogrammed) at once.

Also, most IMMO2 keys I've come across can be reused with IMMO3. Being previously used with an IMMO2 system will not count towards the initial IMMO3 programming.

 

[Nuje]

The above from @caffeine has been my experience as well.

The "write once" pairing of the RFID, though, relates to being good on just that one car to which the key was initially paired/programmed.

So, if you find a key sitting in a wreck at the scrapyard and think you're going to just replace the key blade and then pair the key to IMMO - won't work.
You can still re-use that key body, but it would require removing and replacing the little grain-of-rice-sized RFID glass vial that's embedded in the key body.

You can get a 5-pack of those RFID things at Aliexpress for like $10, and it's not brain surgery to replace one (I've done a couple), but you'll probably want to check out a couple YT videos so you know exactly where you're going to get at it.

 

[dhangejr]

The above from @caffeine has been my experience as well.

The "write once" pairing of the RFID, though, relates to being good on just that one car to which the key was initially paired/programmed.

So, if you find a key sitting in a wreck at the scrapyard and think you're going to just replace the key blade and then pair the key to IMMO - won't work.
You can still re-use that key body, but it would require removing and replacing the little grain-of-rice-sized RFID glass vial that's embedded in the key body.

You can get a 5-pack of those RFID things at Aliexpress for like $10, and it's not brain surgery to replace one (I've done a couple), but you'll probably want to check out a couple YT videos so you know exactly where you're going to get at it.

My question is simpler said : “if I make a new rfid chip will my old one still work?

 

[gmenounos]

My question is simpler said : “if I make a new rfid chip will my old one still work?

Your old ones will still work but you have to match all of them to the car as explained here: http://wiki.ross-tech.com/wiki/index.php/Immobilizer_III_Key_Matching_(Cluster)

 

[dhangejr]

Ok so I is just like matching the remote. This is great news !

 

[Nuje]

Yes - current key + add new (new) key(s) = no problem. Just need to do all at the same time. Follow Ross-Tech instructions.

Current key + new (to you; previously matched to different car) key with new blade = no go (until you replace the IMMO chip with one of these).