kw1281test: A Free VDS-Pro / VagTacho Alternative

[sixspeedbmw]

Any tips on getting past this error:

Version 0.71-beta (https://github.com/gmenounos/kw1281test/releases)
Args: com2 10400 17 DumpEeprom 0 2048
OSVersion: Microsoft Windows NT 10.0.19042.0
.NET Version: 6.0.0
Culture: en-US
Opening serial port com2
Sending wakeup message
Reading sync byte
Keyword Lsb $01
Keyword Msb $8A
Protocol is KW 1281 (8N1)
ECU: 4B0920981Q KOMBI+WEGFAHRS. VDO D07
Software Coding 03283, Workshop Code: 09109
Sending ReadIdent block
Sending Custom "Read Software Version" blocks
Sending Custom "Unlock Additional Commands" 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.Unlock() in C:\Users\gmeno\src\kw1281test\Cluster\VdoCluster.cs:line 170
at BitFab.KW1281Test.Program.UnlockControllerForEepromReadWrite(IKW1281Dialog kwp1281) in C:\Users\gmeno\src\kw1281test\Program.cs:line 1016
at BitFab.KW1281Test.Program.DumpClusterEeprom(IKW1281Dialog kwp1281, UInt16 startAddress, UInt16 length) in C:\Users\gmeno\src\kw1281test\Program.cs:line 1100
at BitFab.KW1281Test.Program.DumpEeprom(IKW1281Dialog kwp1281, UInt32 address, UInt32 length) in C:\Users\gmeno\src\kw1281test\Program.cs:line 688
at BitFab.KW1281Test.Program.Run(String[] args) in C:\Users\gmeno\src\kw1281test\Program.cs:line 278
at BitFab.KW1281Test.Program.Main(String[] args) in C:\Users\gmeno\src\kw1281test\Program.cs:line 30

 

[gmenounos]

ECU: 4B0920981Q KOMBI+WEGFAHRS. VDO D07

That's an Audi cluster, and since I don't own any Audi clusters, it's pretty much impossible for me to support them. You might try VAG EEPROM Programmer. There's a link to it here: https://forums.tdiclub.com/index.ph...tacho-alternative.509151/page-28#post-5694070

 

[Mozambiquer]

I just used this to program the mileage for my new red dot cluster I am installing in my mk4 golf. I am once again, very satisfied!

 

[caffeine]

Just used this on a 1C0920801A Beetle cluster and successfully got a memory dump. The software spat out a warning about it being an untested cluster version. It's from a Canadian '00 ALH 5-speed Beetle.

I see that VAGTacho can change the mileage on these clusters but that can't be done with kw1281test as of now, right?

 

[Mozambiquer]

Just used this on a 1C0920801A Beetle cluster and successfully got a memory dump. The software spat out a warning about it being an untested cluster version. It's from a Canadian '00 ALH 5-speed Beetle.

I see that VAGTacho can change the mileage on these clusters but that can't be done with kw1281test as of now, right?

It at least can be done on the Jetta/golf/Passat clusters... I just did it on one.

 

[Nuje]

Those are 1Jx or 3Bx clusters; @caffeine is using a 1C0 cluster - I don't know the answer to their question, but whether or not kw1281test works on a Golf/Jetta/Passat cluster is irrelevant to its capabilities on a relatively early NB cluster.

 

[caffeine]

It at least can be done on the Jetta/golf/Passat clusters... I just did it on one.

Yes I know haha, I've used this to adjust mileage lots of times on 1J0 xxx xxx clusters.

 

[Mozambiquer]

Yes I know haha, I've used this to adjust mileage lots of times on 1J0 xxx xxx clusters.

I would say that if you know where the mileage is stored, you should be able to do it on the beetle ones as well. I have to rely on someone telling me where it is, so I'm not much help on that part.

 

[VW_Factor]

This stuff might be relevant to my interests.

The last 4 VWs I've had, I was able to use VCDS to enable the keyfob window function. On my 2020, I checked the codings for the function, and they were already checked as enabled??. I left it alone and asked the dealer. They were clueless, but interested. Through some reading I found that on the cars that had Carnet, the window function was through that module (which my car didn't have yet due to chip shortages). Last month, finally got the Carnet module installed (yay, car is finally done being built).

Carnet is supposed to be able to report windows up/down, car locked/unlocked, etc, and supposed to be able to use the application to operate these things. Carnet application reports "windows unavailable".

But, the keyfob will open and close the sunroof, windows don't respond.

Given that the dealer didn't even know the cars would or could do this, I'm in sort of a weird spot. Would be nice if Carnet worked like it was supposed too for my 2020.

This is more a complaint post of the weirdness. At this point, would be nice to just have the car operate like its supposed too. When I get some time this weekend, I really really need to pull an autoscan of the car, and post it over at Ross-Tech, see if they have any insight. Other than asking the dealer to just completely re-flash the modules in the car, I'm not really sure where to go at this point.

Having other potential options to look at it for digging into the modules a bit sounds like it could be helpful.

 

[gmenounos]

Just used this on a 1C0920801A Beetle cluster and successfully got a memory dump. The software spat out a warning about it being an untested cluster version. It's from a Canadian '00 ALH 5-speed Beetle.

I see that VAGTacho can change the mileage on these clusters but that can't be done with kw1281test as of now, right?

It's on my To-Do list.

Now that your cluster is no longer "untested", could you please post the software version (probably contains the word "M73") and the size of the dump file (should be either 1024 or 2048) so that I can add support for it to kw1281test? Thanks!

 

[gmenounos]

Having other potential options to look at it for digging into the modules a bit sounds like it could be helpful.

Unfortunately, kw1281test only works with older cars that use the K-Line for diagnostics. Anything made in the past 10+ years uses the CAN bus, and since I currently only own MKIV cars, I can't add support for anything newer.

 

[VW_Factor]

Dang, that's a bummer. Keep up the good work though, we need more people digging into these things like you are

 

[caffeine]

It's on my To-Do list.

Now that your cluster is no longer "untested", could you please post the software version (probably contains the word "M73") and the size of the dump file (should be either 1024 or 2048) so that I can add support for it to kw1281test? Thanks!

Software version was "M73 V02" and size of the dump file was 1024

 

[gmenounos]

Software version was "M73 V02" and size of the dump file was 1024

Are you sure it was M73 V02? That should have got identified as a 2048-byte EEPROM instead of "Untested".

 

[caffeine]

Are you sure it was M73 V02? That should have got identified as a 2048-byte EEPROM instead of "Untested".

This is a snippet of the log:
"Protocol is KW 1281 (8N1)
ECU: 1C0920801A KOMBI+WEGFAHRS. M73 V02
Software Coding 01302, Workshop Code: 00050"

I also just discovered it also spat out the "Untested cluster version" message on an 01 Gas NB cluster I had:

"ECU: 1C0920801 KOMBI+WEGFAHRS. M73 V02"

Both of the clusters I get the message on are IMMO2 clusters. 1C0920801A from an 00 TDI and 1C0920801 from an 01 2.0L.

 

[caffeine]

And I know that the 1024 byte cluster dumps are accurate because the SKC code is contained at 0x313/0x314.

 

[Nuje]

I'm surprised that these are 1024-byte EEPROMs; all of the IMMO2 dumps I've picked up (admittedly from 1Jx clusters) have been only 512bytes.
e.g.

 

[caffeine]

I'm surprised that these are 1024-byte EEPROMs; all of the IMMO2 dumps I've picked up (admittedly from 1Jx clusters) have been only 512bytes.
e.g.

Beetle clusters are a totally different animal

 

[gmenounos]

This is a snippet of the log:
"Protocol is KW 1281 (8N1)
ECU: 1C0920801A KOMBI+WEGFAHRS. M73 V02
Software Coding 01302, Workshop Code: 00050"

I also just discovered it also spat out the "Untested cluster version" message on an 01 Gas NB cluster I had:

"ECU: 1C0920801 KOMBI+WEGFAHRS. M73 V02"

Both of the clusters I get the message on are IMMO2 clusters. 1C0920801A from an 00 TDI and 1C0920801 from an 01 2.0L.

Darn, I was assuming that the software version could be used to determine if the cluster is Immo2 or Immo3 (which I think also determines the EEPROM size). However, here's an example of a 2005 Beetle cluster (presumably Immo3 because of the year and because the VIN shows up in the VCDS scan). It's also running M73 V02 software:

Address 17: Instruments Labels: 1C0-920-x4x.lbl
Part No: 1C0 920 951 F
Component: KOMBI+WEGFAHRS. M73 V02
Coding: 11232
Shop #: WSC 00000
VCID: 2411EBBD07CAC0878DF-4B1E
3VWCD31Y55M350443 VWZ5Z0D9188110

And here's a 2008 Beetle cluster, part number 1C0920801J, which other than the J is the same part number as your 00/01 clusters:

Address 17: Instruments Labels: None
Part No: 1C0 920 801 J
Component: KOMBI+WEGFAHRS. M73 V04
Coding: 11234
Shop #: WSC 00066
VCID: 2241F895AE5D279BF5-4AB4

It sounds like it's going to be pretty difficult to auto-identify the Beetle clusters based on software version or part number, so I'll probably remove that logic from kw1281test.

 

[70chips]

Hi gmenounos , I'm having a clear out of the stores and have found a few TT clusters I'm not going to use. I was wondering if they were of any use to you now?

Alan

 

[gmenounos]

Hi gmenounos , I'm having a clear out of the stores and have found a few TT clusters I'm not going to use. I was wondering if they were of any use to you now?

Thanks for the offer! Do you happen to have the part numbers? Do you know if any do not currently work with kw1281test? Since you're in the UK and I'm in the US, it might only be worth shipping one if it's not currently supported by kw1281test, since I may be able to add support if I have one in hand to test with.

 

[Melkel_21]

Thanks for the offer! Do you happen to have the part numbers? Do you know if any do not currently work with kw1281test? Since you're in the UK and I'm in the US, it might only be worth shipping one if it's not currently supported by kw1281test, since I may be able to add support if I have one in hand to test with.

Greetings could you put this audi tt cluster version?
Protocol is KW 1281 (8N1)
ECU: 8N1920980E KOMBI+WEGFAHRS. M73 D07
Software Coding 23244, Workshop Code: 00000
It said that is untested software version. Thanks

 

[pkhoury]

I don't suppose anyone knows if I could set the rear hatch to always stay unlocked on a 2000 NB, along with a possible needle sweep on the cluster, and what bits I'd change for windows up/down with the remote? I acquired a non-running 2000 NB TDI on Thursday, and got it running so far (previous owner or his mechanic had the IP timed 180 degrees off, and said it was a blown head gasket).

 

[gmenounos]

Greetings could you put this audi tt cluster version?
Protocol is KW 1281 (8N1)
ECU: 8N1920980E KOMBI+WEGFAHRS. M73 D07
Software Coding 23244, Workshop Code: 00000
It said that is untested software version. Thanks

For Magneti Marelli clusters (e.g., New Beetle and Audi TT), you can try 2 different ways to dump the EEPROM. (replace "COM1" with the port that your cable is using)

For your Audi, I would try this one first:
.\kw1281Test.exe COM1 9600 17 DumpMarelliMem 14336 2048

Only if it doesn't work, you can also try this one:
.\kw1281Test.exe COM1 9600 17 DumpMarelliMem 3072 1024

If either one works, let me know and I'll add it to kw1281test. If neither one works, there's not much I can - unless some generous person wants to donate one in the name of science

 

[gmenounos]

I don't suppose anyone knows if I could set the rear hatch to always stay unlocked on a 2000 NB, along with a possible needle sweep on the cluster, and what bits I'd change for windows up/down with the remote? I acquired a non-running 2000 NB TDI on Thursday, and got it running so far (previous owner or his mechanic had the IP timed 180 degrees off, and said it was a blown head gasket).

I've never heard of a needle sweep patch for NB clusters, only MKIV MFA/FIS VDO clusters.

 

[pkhoury]

For Magneti Marelli clusters (e.g., New Beetle and Audi TT), you can try 2 different ways to dump the EEPROM. (replace "COM1" with the port that your cable is using)

For your Audi, I would try this one first:
.\kw1281Test.exe COM1 9600 17 DumpMarelliMem 14336 2048

Only if it doesn't work, you can also try this one:
.\kw1281Test.exe COM1 9600 17 DumpMarelliMem 3072 1024

If either one works, let me know and I'll add it to kw1281test. If neither one works, there's not much I can - unless some generous person wants to donate one in the name of science

I'm pretty sure I sent you a cluster from a 2003 NB before, but mine is a 2000. There *might* be one in the junkyard from a 2001, if that would help you, assuming it follows the whole Immo2 to 3 switch from 2001 to 2002 like with the Jetta and Golf. I need to raid that one (also a TDI) for various parts for my beetle).

As for the comfort control module in the Beetle - what could I do there? Any way to allow the rear hatch to always be unlocked, where I only have to pull the handle to unlock, as with the Golf, and mom's Jetta Wagon?

 

[pkhoury]

I've never heard of a needle sweep patch for NB clusters, only MKIV MFA/FIS VDO clusters.

I didn't think so, but thought I'd check. Never done anything with the Magnetti Marelli clusters, though I'd like to change some of the lighting options on it.

 

[Nuje]

As for the comfort control module in the Beetle - what could I do there? Any way to allow the rear hatch to always be unlocked, where I only have to pull the handle to unlock, as with the Golf, and mom's Jetta Wagon?

Take a look at what the part number is for the CCM. Given that most of the hacks are on 1C0959799* CCMs, and 1C0 means the part first appeared on a NB (1C0 = NB), there's a half-decent chance it has that capability. I'd be curious to see as well.

 

[caffeine]

Take a look at what the part number is for the CCM. Given that most of the hacks are on 1C0959799* CCMs, and 1C0 means the part first appeared on a NB (1C0 = NB), there's a half-decent chance it has that capability. I'd be curious to see as well.

An 00 Beetle will have a 1J0 CCM, but it's still supported, just different bits to change. 01.5 was the changeover to 1C0 CCMs

 

[Nuje]

2001 Golf I looked at recently had a 1C0962258P - any idea which bits to flip on what bytes there?