Dude, what took you so long? Even though it's all command prompt, SO much more intuitive than VDS Pro. I feel you though - my old laptop is about 6 pounds with rebuilt battery, and old laptops aren't really very visible in sunlight when trying to program the CCM.
Wouldn't it be in hex? So whatever the odometer mileage reports back via VCDS (which is probably kilometers), convert to hex and then search for that string in a hex editor? Or not that simple?
If you dump the eeprom before and after a drive, then wherever some bytes have changed, that's where your odo will be.
Not usually that simple: http://nefariousmotorsports.com/forum/index.php?topic=3504.0
Totally didn't think about that, so good point!
Even though that thread is for mk3 clusters, I presume mk4 clusters would follow the same algorithm?
Awesome, appreciate all the work you put in for the community. Worked like a charm as usual when none of the other programs like vag k+can 1.4 or vageeprom would work. Thanks again!Thanks for the report. kw1281test wasn't recognizing "1JE920827" as a cluster part number because it was expecting the 3rd character to be a digit. Should be fixed in version 0.85:
Release v0.85-beta · gmenounos/kw1281test
Fixed an issue where it was failing to identify "1JE920827" as a cluster part number because it was expecting the 3rd character to be a digit. Added a unit test project.github.com
At least some do. Some of the later clusters (VWK503 I think) have a checksum that needs to match the odometer block. Others (Bosch RB8) store the odometer using a different format.
I totally get it. For moral and ethical reasons, I'd be in the same boat as you.
Odo fraud is only prosecutable during the car's first 10 years, federally. If you're worried about potential mischief by crooks, the loss of an entire car to quick immo delete would be much worse than someone rolling the miles back 200k on an unsuspecting buyer. Other signs of wear and tear will be present.
You don't need to hack the cluster for that. Just turn the key on, and have your Arduino cycle the VSS input a million times.
I'm by no means an expert on the subject but i dont think a "quick" immo delete is even possible. For their age, these cars have some great theft protection and im glad to see that it has stood the test of time.
There's easier ways than that lol.
Setting the odometer to match the ECU when replacing a cluster is completely legitimate.
On an ALH? immobilizer delete takes me about 5 minutes or less. Super easy. PD and CR require bench flashing, which would be easier if I had an Alienware K-Tag device.
True. Coincidentally, the last, or only Arduino I've bought was for a project here on TDIclub another member did for showing EGTs.
I don't know about intuitive. You have to literally know com port, baud rate and the specific addresses for each individual hack you're doing.
It takes some practice, but you get the hang of it after a while. For the most part, the COM port my keyspan gets assigned doesn't change. I think all modules are 9600 baud except the instrument cluster, which is 10400. I guess I'm biased, because I've used it a few times, so I remember some, though I don't use it daily. In Windows, it also helped to enable quickedit, so you can double click on options or highlight to copy to the clipboard, to avoid misspelling flags (like ReadEeprom, which I've done by typing manually and forgetting an E).
I've used it before on a 486-based ThinkPad I have, which I've rebuilt the battery on. It works, but I still find kw1281test more intuitive, especially when I'm going to open a file in a hex editor or clone the EEPROM to another cluster (in case of an upgrade).
That it is. @gmenounos did a fine job on this program. And I was being sarcastic giving you crap in not having used this earlier, btw.
Version 0.85-beta (https://github.com/gmenounos/kw1281test/releases)
Args: COM1 10400 17 getskc
OSVersion: Microsoft Windows NT 10.0.19045.0
.NET Version: 7.0.11
Culture: en-US
Opening serial port COM1
Sending wakeup message
Wakeup duration: 2 seconds
Reading sync byte
Keyword Lsb $01
Keyword Msb $8A
Protocol is KW 1281 (8N1)
ECU: 1J0920925D A4-KOMBIINSTR. VDO V09
Software Coding 07232, Workshop Code: 00001
Sending ReadIdent block
Sending Custom "Read Software Version" blocks
Sending Custom "Unlock Additional Commands" block
00: VAT500MH $01
01: $91 $17
02: $11 $04 $00 $0C $12 $03
03: VW A4/T4 5/01 Maske
Sending Custom "Unlock partial EEPROM read" block
Unlock code for software version 'VAT500MH 01.20' is 01 04 3D 35
Sending Custom "Need Seed/Key?" block
Sending Custom "Seed request" block
Sending Custom "Need Seed/Key?" block
Failed to unlock cluster.
Saving EEPROM dump to IMMO-IDENTNR_VWZ7Z0Y2988264________$0090_eeprom.bin
Sending ReadEeprom block (Address: $0090, Count: $10)
Received "Read ROM/EEPROM Response" block: 56 57 5A 37 5A 30 59 32 39 38 38 32 36 34 56 57
Sending ReadEeprom block (Address: $00A0, Count: $10)
Received "Read ROM/EEPROM Response" block: 5A 37 5A 30 59 32 39 38 38 32 36 34 56 57 5A 37
Sending ReadEeprom block (Address: $00B0, Count: $10)
Received "Read ROM/EEPROM Response" block: 5A 30 59 32 39 38 38 32 36 34 04 60 04 60 04 60
Sending ReadEeprom block (Address: $00C0, Count: $10)
Received "Read ROM/EEPROM Response" block: 58 58 58 58 58 58 58 58 58 58 58 58 58 58 58 58
Sending ReadEeprom block (Address: $00D0, Count: $10)
Received "Read ROM/EEPROM Response" block: 58 FF 58 58 58 58 58 58 58 58 58 58 58 58 58 58
Sending ReadEeprom block (Address: $00E0, Count: $10)
Received "Read ROM/EEPROM Response" block: 58 58 58 FF FF FF FF FF FF FF 3F E3 3F E3 3F E3
Sending ReadEeprom block (Address: $00F0, Count: $10)
Received "Read ROM/EEPROM Response" block: 3F E3 3F E3 40 E3 40 E3 40 E3 00 00 00 00 08 00
Sending ReadEeprom block (Address: $0100, Count: $0C)
Received "Read ROM/EEPROM Response" block: 00 00 00 00 00 00 00 00 00 00 FF FF
Saved EEPROM dump to IMMO-IDENTNR_VWZ7Z0Y2988264________$0090_eeprom.bin
SKC: 06004
Sending EndCommunication block
Yeah, the newer VDO clusters have this seed/key thing where, in order to unlock it fully so that the EEPROM can be dumped, you have to ask the cluster to send you a 4 byte random value (the seed), then you take that seed and do a calculation with it using a secret algorithm to compute a 4 byte value (the key) that you send back to the cluster. The cluster then verifies that you sent back the right result and lets you access the EEPROM.
Unfortunately not.
Read the first post of this thread: "Q: Will it work with my car?"
I can't speak for your ECU, but I know Bosch ECUs can be read/written to with an MPPS cable. EEPROM usually requires another cable and software (EEPROM modification is used when you want to delete the immobilizer, for instance). But it still also depends on the generation of car, too. Some ECUs need to be opened up and flashed on the bench.
Can you send us a screenshot, or copy/paste the error you get on your command prompt? You should be able to highlight everything with your left mouse button, then right click to save to the clipboard. Then, you could paste it on your next reply.
Your 2008 is most likely CAN Bus, and not compatible with this program.
There was a post with information about which vehicles are compatible and at the bottom there a note * about 2008 Beetles, can't find it now.
Found it, don't completely understand it.
Microsoft Windows [Version 10.0.19045.3448]