pcmhacking.net

No kidding, just went through the so called "instrument" settings for vx.. wow... what a poor excuse for editing parameters. Yeah, I did notice that there wasnt any "reset" settings in there for them. Although I do believe you can do it over comms line. Havent actually tried this yet but Im assuming if one was to send F2,57,0A,01,chksum they would reset table from to default settings ect. Each table resets a different parameter eg fuel, speedo cal ect. This is what goes on for vy/vz clusters. Could be a quick fix if something goes wrong assuming they had this implemented (Id say they did) since the F2,56,0A,chksum still resets cluster (to clear any faults).

just got a 3 window VT cluster and it is nothing like the VX, 1 of the windows is completely different.( the VX cluster is already CANBUS cluster )
the software loaded is very different and the calibrations are different for the stepper motors and warning lights, and the hex values are transposed from the VX
it has a engineering mode but it does not display the warning lights or the dial needle placements

if you want to program these early eeprom stick to serial basic programmers

Bit of a late reply,
The info stored may be different but should be stored in the same locations? . Its responses over comms are the same in regards to what each byte means, although the actual figures may be slightly different due to different calibrations eg speedo/tacho compression values.

Hi guys,

I'm new to the forum and have found this topic to be very interesting. I've been playing around with a VZ HSV level 3 cluster. Here are 2 dumps taken at 137,090 and 137,101kms. Can anyone help me in calculating new values to alter the odo reading? Changed a few values and didn't have much luck - put the odometer to 999,999kms Any help would be much appreciated.

Looks like a series 2 VZ file OBD2, they changed mid series and probably like the VE

if you search this forum you'll find the VE calculations which will be the same

damo wrote:Hi guys,

I'm new to the forum and have found this topic to be very interesting. I've been playing around with a VZ HSV level 3 cluster. Here are 2 dumps taken at 137,090 and 137,101kms. Can anyone help me in calculating new values to alter the odo reading? Changed a few values and didn't have much luck - put the odometer to 999,999kms Any help would be much appreciated.

By the looks of it, you got these dumps using ponyprog? Most likly using a serial programmer?

VX/VT calcs are nothing like the VY/VZ calcs. And the VE calcs are even more messed up! (least for the e3 clusters which is a whole new league!).

Try the attached vz file out

Thanks guys. Yes was using Ponyprog2000 and serial port. Tried the file but no luck - odo still reading 999,999kms

Ahh, haha I read your comment wrong. I thought you said set it to 999,999. I was wondering why you were asking that? haha. Use the original files got since they will have the original configurations

If the original files that you read dont write back properly, then they not be valid.. and must have only got part read or just a bad read in general.

That, or your not writing to the device properly.

Have you tried reading and then verifying the read? Make sure its the same?

Same with the writing, should also take a few reads, verify the reads then make changes and write. Then make sure to verify the write to ensure it worked.

Haha yeah I've been able to restore the original files okay. Ideally I'd like to be able to calculate the values to be able to set the odo to around 100,000 or any other value. Doing a compare between the two dumps shows the location that has been changed but no idea how the values are calculated

I dont like the sounds of this. Its probably time for a quick reminder: The only reason you should be adjusting a dash odo is if you are replacing a broken dash or upgrading a dash to a higher spec cluster from another car and you are setting it to the exact and correct reading for the car it is going in to.