Here you go. Keep in mind, this was compiled from research I did 17 years ago, from many disparate wiring diagrams provided by strangers on the internet, and I was not entirely paying attention to differences between model years and cluster part numbers. The photo I posted above is the only indication I ever got that I didn't F it all up royally. Hopefully someday soon I'll be able to reinstall, match the immo, and double-check my work.
I can say for certain that, on my 1J0 CCM, the bit for “rear hatch unlock type” works perfectly. You can remove the asterisk. I just rewired my hatch from Jetta style to Golf, and the two-way solenoid didn’t work properly until I flipped that bit.
Well I tried it, and this was the result:
Version 0.62-beta (https://github.com/gmenounos/kw1281test/releases)
Args: com2 10400 17 dumpeeprom 0 2048 bins\AllroadCluster\Stock03-297831k.bin
OSVersion: Microsoft Windows NT 6.3.9600.0
.NET Version: 5.0.8
Culture: en-CA
Opening serial port com2
Sending wakeup message
Reading sync byte
Keyword Lsb $01
Keyword Msb $8A
Protocol is KW 1281 (8N1)
ECU: 4B0920933S KOMBI+WEGFAHRS. VDO D12
Software Coding 06364, Workshop Code: 19411
Sending ReadIdent block
Sending ReadIdent block
Sending Custom "Read Software Version" blocks
Sending Custom "Unlock Additional Commands" block
Received NAK block
Received NAK block
Received NAK block
Received NAK block
Received NAK block
Sending Custom "Unlock partial EEPROM read" block
Caught: System.Collections.Generic.KeyNotFoundException The given key '0' was not present in the dictionary.
Unhandled exception: System.Collections.Generic.KeyNotFoundException: The given key '0' was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey )
at BitFab.KW1281Test.Cluster.VdoCluster.UnlockCluster(IKW1281Dialog kwp1281) in C:\Users\gmeno\src\kw1281test\Cluster\VdoCluster.cs:line 17
at BitFab.KW1281Test.Program.UnlockControllerForEepromReadWrite(IKW1281Dialog kwp1281) in C:\Users\gmeno\src\kw1281test\Program.cs:line 863
at BitFab.KW1281Test.Program.DumpClusterEeprom(IKW1281Dialog kwp1281, UInt16 startAddress, UInt16 length) in C:\Users\gmeno\src\kw1281test\Program.cs:line 979
at BitFab.KW1281Test.Program.DumpEeprom(IKW1281Dialog kwp1281, UInt32 address, UInt32 length) in C:\Users\gmeno\src\kw1281test\Program.cs:line 572
at BitFab.KW1281Test.Program.Run(String[] args) in C:\Users\gmeno\src\kw1281test\Program.cs:line 205
at BitFab.KW1281Test.Program.Main(String[] args) in C:\Users\gmeno\src\kw1281test\Program.cs:line 26Thanks mate! I will compare it with what I had so far.
Awesome!! Should be updated now.
1C0920803T M73 V01 (2008 NB) - This one seems to make it using 14336 2048 before hitting the (expected?) NotImplementedException1C0920801L (2009 NB) - Next up to test
Now if only we could pull and rewrite EDC16 EEPROMS (or even rewrite EDC15 EEPROMS, where the immo has been deleted). I've been using another program to delete the immo off EDC15 ECUs, but it'd be nice to do it on the EDC16 as well!
Ah, we call that 'interior monitoring'
For Magneti Marelli clusters (Beetle and TT), you'll need to temporarily use version 0.71. The newer versions contain the bug that you ran into. Hopefully I'll have some time to fix that soon.
try to edit it with a binary editor, such as HxD on windows
I'm not sure. I don't think I have any 919 clusters to test it on so you may have to try it yourself. I think in the US, the 919 clusters don't have an immobilizer, so kw1281test isn't very useful on those.
I will test and report back then. I have germany market car and I'm pretty sure it has the immobilizer in the cluster itself.
I can probably dig up that info but some of the scales are checksum protected so if you try to modify them and don't include the checksum, the cluster will complain in some way. The safest way would be to use DashDumpEdit. There's a download link here:
