kw1281test: A Free VDS-Pro / VagTacho Alternative

[gmenounos]

If VCDS-Lite can't connect to the CCM then kw1281test won't be able to either. Maybe your CCM has a broken K-Line.

 

[stallion_007]

Is there a way to check the CCM for power and broken K-Line? Also, my daughter had taken this car to a locksmith recently, and they were able to program a new key so I am assuming the CCM was working a few months ago?

 

[P2B]

Is there a way to check the CCM for power and broken K-Line? Also, my daughter had taken this car to a locksmith recently, and they were able to program a new key so I am assuming the CCM was working a few months ago?

Key programming does not require CCM access.

 

[berre]

This is probably going to be a long post, because some context is necessary, but I'll try to keep it concise.

I own a 1998 Passat Variant, 3B5, with the 1.9 turbo diesel AHU engine, 66 kw. I've been addressing all kinds of issues, got it through technical inspection (here in Belgium), etc. I have recently lost engine performance, but a new turbo and vacuum lines have been ordered and I'm gonna install it soon. Might have to buy some new sensors too.

The instrument cluster has 'misbehaved' since the moment I got it, which is 2 years ago now; except for the speedometer, the values were wrong. The needles for rpm and fuel tank volume move, but their 'zero' is competely wrong (e.g. 0rpm = 1900rpm on the dial). Also, the red display doesn't work.

Earlier tonight I checked again if I could get the shareware version of vcds-lite working, this time with a cable with a ch340 chip, after my earlier attempt with an ftdi chip based cable was unsuccesfull.
This time it worked, and I decided to try an 'auto-scan'. During the scanning, which took quite a while, the needles moved 'around the place', and after finishing the needles for speed, engine temp and fuel tank volume stayed in the 'maxed out' position. I disconnected the car battery for a while, but when I turn the ignition on that's still exactly what I get: +1900 for the rpm value, and the needles for speed, tank volume and engine temp in their highest position (further than what's on the dial).
The needles move if I start the car, or in any case the one for fuel tank volume - had to stop testing though as I don't have a battery charger at the moment.

I can monitor vehicle speed with gps on my phone, for now. Fuel tank volume is more inconvenient; before it indicated (a lot) less than was in the tank, giving me some indication at least, while now it indicates way more than what's actually there.

I like kw1281test, have been reading the documentation. Using the command line is no issue, but as I'm a (car) noob there's still a lot I don't understand. Is there a way to reset the needles? Should I maybe take out the cluster and move the needles physically? Or would it be best to replace the cluster? In case the last option is the best, I guess I should have the skc/pin of the replacement cluster?

Thx in advance for any replies.

 

[Nuje]

So, when the engine is turned off (key out of ignition), are the needles sitting at "zero"? Or are they all in the wrong place - like the RPM needle is at 1900 even with the engine turned off?

If so, it's easy to pop out the needles and rotate them backwards (counter-clockwise) so that the needle now sits at zero. Probably some videos on youtube, but the hardest part is be unplugging the blue and green connectors from the back of the cluster. After you have it out, you simply undo two T10 (maybe T15?) screws, pull the cluster apart, then you can rotate the needles to wherever you want them to have as their "zero" position.

 

[gmenounos]

You can use the kw1281test "ActuatorTest" command (or I think called "Output Test" in VCDS) to test the needle alignment. The needles will each sweep from min to max and then stop at a specific midpoint (50% for fuel gauge and coolant temp, 100km/h for speedo, 3000rpm for tach). Plus it will test all the lights and the alert sounds.

 

[berre]

Thx for the feedback!

Yes with the key out of the ignition, rpm is at 1900, and the needles for engine temp and speed are beyond the scale, maxed out so to speak. I'm gonna look into moving the needles. Probably best to do that first and then do the kw1281test 'ActuatorTest' command, I guess?

 

[berre]

I got the cluster out, put the needles in the right place, and did the ActuatorTest command.... Had to use a baud rate of 9600 in stead of 10400 (I tried that first, but after that failed the software suggested trying another rate, which is convenient ).

All gauges work now as they should, I wasn't able to make a bluetooth connection between my phone and my OBD dongle so couldn't get live data, but rpm values seem normal. Indicated speed is a bit higher than what it actually is, 3km/h or so, might have bumped the needle when putting things back together but it's not a serious issue. Tank volume is correct (filled it up), engine temp seems to be correct too (have to verify more accurately).

Thx a LOT for this software (I love open source stuff!), as well as the advice given.

 

[ecala001]

For skc would it be 1451?

Received "Read EEPROM Response" block: AB 05 AB 05 AB 05

This is on a 05 bew

Sending Custom "Unlock Additional Commands" block

00: VWK503LL $00 $09

01: $58 $20

02: $13 $0B $02 $0D $35 $04

03: VW/Sk LL ROM-Maske

Sending Custom "Unlock partial EEPROM read" block

Unlock code for software version 'VWK503LL 09.00 is 3E 35 3D 3A

Sending Custom "Get Access Level" block

Access level is 4.

Sending Custom "Seed request" block

Block: C4 C3 E4 5B E4 07 DO 35 01 00

Access level 7 secret: $55 $16 $A8 $94

Sending Custom "Key response" block

Sending Custom "Get Access Level" block

Access level is 7.

Cluster is unlocked for ROM/EEPROM access.

Saving EEPROM dump to 3VWSR69M15M024560_____VWZ7Z0D0137567_$010A_eeprom.bin

Sending ReadEeprom block (Address: $010A, Count: $06)

Received "Read EEPROM Response" block: AB 05 AB 05 AB 05

Saved EEPROM dump to 3VWSR69M15M024560_____VWZ7Z0D0137567_$010A_eeprom.bin

Sending EndCommunication block

 

[gmenounos]

For skc would it be 1451?

Received "Read EEPROM Response" block: AB 05 AB 05 AB 05

This is on a 05 bew

Yes, SKC should be 01451.

Also, in case you didn't know, kw1281test has a GetSKC command that will usually be able to calculate the SKC for you.

 

[ecala001]

Yes, SKC should be 01451.

Also, in case you didn't know, kw1281test has a GetSKC command that will usually be able to calculate the SKC for you.

Got it to successfully pair the new (used) cluster and key matching. However, I noticed there are two vins now on the extra field. Did I mess something up?

Also how can fix the milage on the cluster for a bew? I have 297k on original cluster and new one shows 230k. I need it to match for upcoming smog

Edit:::
Was able to edit it using vag eeprom programmer to match my original cluster. The weird thing is that vcds ECU mileage shows 296215 miles and my cluster reads 297106. Not sure if this will get flagged when I get smog. 297107 was the number prior to replacement as the used cluster was at 230k.
***Note not trying to do anything malicious, just trying to match what I initially had.

 

[gmenounos]

Got it to successfully pair the new (used) cluster and key matching. However, I noticed there are two vins now on the extra field. Did I mess something up?

Are both "VINs" 17 characters long? Or is one 17 characters long (which would indicate a VIN) and the other 14 characters long (which would indicate an immobilizer ID)?

The weird thing is that vcds ECU mileage shows 296215 miles and my cluster reads 297106.

VCDS ECU mileage is not exact like the cluster mileage: https://www.ross-tech.com/vcds/tour/EDC-15-Mileage.php

 

[ecala001]

Are both "VINs" 17 characters long? Or is one 17 characters long (which would indicate a VIN) and the other 14 characters long (which would indicate an immobilizer ID)?



VCDS ECU mileage is not exact like the cluster mileage: https://www.ross-tech.com/vcds/tour/EDC-15-Mileage.php

Yeah both are 17 characters long