GM Technical Document Discussion
Holden VT and VX Instrument Cluster EEPROM Programming
Forum rules
To gain access to the Invite Only forum you must be invited by a member of that forum. That member will PM the mods or admins (NOT you) saying that they nominate you for access. THEY will be responsible for your actions. If you don't post and just leech info, you will BOTH be removed. Dont send a PM to the moderators or admins asking for access, you really dont want to see the result. If you submit information, you may simply be invited
To gain access to the Invite Only forum you must be invited by a member of that forum. That member will PM the mods or admins (NOT you) saying that they nominate you for access. THEY will be responsible for your actions. If you don't post and just leech info, you will BOTH be removed. Dont send a PM to the moderators or admins asking for access, you really dont want to see the result. If you submit information, you may simply be invited
by jezzab » Tue Apr 03, 2012 7:49 pm
Try writing to it with the 9v battery connected. Ive had to write PIMs this way. the board sucks too much power from them to write.
Daily Ute - 2009 Holden VE SSV Ute Single Turbo (IQ, E3 Cluster, EDI) - 586rwhp
Drag Ute - 2002 Holden VU SS Twin Turbo - 1010rwhp [SOLD]
All VE/VF Module reprogramming. Remote programming with flash box
http://www.facebook.com/jsbperformance
Drag Ute - 2002 Holden VU SS Twin Turbo - 1010rwhp [SOLD]
All VE/VF Module reprogramming. Remote programming with flash box
http://www.facebook.com/jsbperformance
by gruntly69 » Tue Apr 03, 2012 8:44 pm
Where/what pins do I apply the the 9v to?
Thanks for the advice
Thanks for the advice
by gruntly69 » Wed Apr 04, 2012 10:00 am
Got to work & saw the gq# programmer has a power supply connector, cool never had to use it!
anyway I tried a 9v & tried it on all speeds -2, -1, 0, +1 & +2 & now good, so then I thought I'd try 12v power & on all speeds again but the same result no luck!
Still waiting to hear from MCUmall, i'm hoping maybe a firmware update or something?
anyway I tried a 9v & tried it on all speeds -2, -1, 0, +1 & +2 & now good, so then I thought I'd try 12v power & on all speeds again but the same result no luck!
Still waiting to hear from MCUmall, i'm hoping maybe a firmware update or something?
by jezzab » Wed Apr 04, 2012 4:51 pm
gruntly69 wrote:Got to work & saw the gq# programmer has a power supply connector, cool never had to use it!
anyway I tried a 9v & tried it on all speeds -2, -1, 0, +1 & +2 & now good, so then I thought I'd try 12v power & on all speeds again but the same result no luck!
Still waiting to hear from MCUmall, i'm hoping maybe a firmware update or something?
Be very careful you dont keep the connector on the chip too long with the board powered up with 12v or the programmer could get very hot and error (and possibly fail). I used to do a quick flash and then unclip (on unplug from the ZIP socket)
Daily Ute - 2009 Holden VE SSV Ute Single Turbo (IQ, E3 Cluster, EDI) - 586rwhp
Drag Ute - 2002 Holden VU SS Twin Turbo - 1010rwhp [SOLD]
All VE/VF Module reprogramming. Remote programming with flash box
http://www.facebook.com/jsbperformance
Drag Ute - 2002 Holden VU SS Twin Turbo - 1010rwhp [SOLD]
All VE/VF Module reprogramming. Remote programming with flash box
http://www.facebook.com/jsbperformance
by gruntly69 » Thu Apr 05, 2012 7:28 am
Yeah thats o.k. I don't think I'll use the extra power for programmer as i didn't help anyway!
I'm thinking the power must be going to some other part of cluster circuitry & causing the issue?
I did manage to get 1 flash yesterday without having the fail, on the cluster that already had bad data written on chip so thought I'll grab the other cluster & test that & failed so now I have 2 dead clusters!
the only way I could get it close to flash properly was select M93S66WP & use 9v extra power & it flashed & changed the 3 bytes I wanted from AFA3 to AFA2, but it sent the very 2 first bytes as 00 00 but didn't offset after that so it actually successfully changed odo reading from 355,373 to 355,372Kms!
So A little bit of progress, but thinking for it to work properly it may need chip un-soldered?
EDIT: why does this forum always redirect to first page of thread after posting????
I'm thinking the power must be going to some other part of cluster circuitry & causing the issue?
I did manage to get 1 flash yesterday without having the fail, on the cluster that already had bad data written on chip so thought I'll grab the other cluster & test that & failed so now I have 2 dead clusters!
the only way I could get it close to flash properly was select M93S66WP & use 9v extra power & it flashed & changed the 3 bytes I wanted from AFA3 to AFA2, but it sent the very 2 first bytes as 00 00 but didn't offset after that so it actually successfully changed odo reading from 355,373 to 355,372Kms!
So A little bit of progress, but thinking for it to work properly it may need chip un-soldered?
EDIT: why does this forum always redirect to first page of thread after posting????
by TazzI » Thu Apr 05, 2012 9:41 am
Desoldering it will definitely eliminate the possibility of it being the board sucking up too much power. looks like your going to have to grab some solder wick and get those buggers off.
Yeah I know what you mean about being shot to the first page.
Yeah I know what you mean about being shot to the first page.
by gruntly69 » Thu Apr 19, 2012 12:32 pm
Well I unsoldered & wrote to the eeprom fine & soldered back on but it's a pain staking process & because I don't know what the calculation is for odo I won't do it all the time if anyone has more info it would help!
I changed all 16 double bytes to 2B67 which equates to 11111 & the odometre reading came out as 869,344Kms
Then we know the AFA2 which equates to 44962 in the 16 double bytes reads odo as 656,912
also have a couple of the early one's to work off too...
any ideas anyone???
I changed all 16 double bytes to 2B67 which equates to 11111 & the odometre reading came out as 869,344Kms
Then we know the AFA2 which equates to 44962 in the 16 double bytes reads odo as 656,912
also have a couple of the early one's to work off too...
any ideas anyone???
by TazzI » Thu Apr 19, 2012 2:58 pm
could solder on an eeprom socket onto the board?
That way you could simply pull the eeprom out each time?
As for the calcs... may take some guess and checks to get some different numbers going.
That way you could simply pull the eeprom out each time?
As for the calcs... may take some guess and checks to get some different numbers going.
by gruntly69 » Sat Apr 21, 2012 1:54 pm
BIG UPDATE....
Unsoldered wrote the same bin with all 2B67 for first 15 double bytes & just added 1 hex to the very last digit so changed 16th double byte to 2B68 & the odo reading came DOWN 1km!
Hoping someone can figure maths theory to know how it calculates???
So 16 double bytes of 2B67 = 869,344Kms
& 15 double of 2B67 & 1 double of 2B68 = 869,343Kms
Hopefully someone can figure it out as it's painful soldering on & off, well actually soldering on is easy its more unsoldering does anyone have anytips for this I've tried solder wick but it doesn't remove all of it, so with what's left I heat up solder & gently pry EEPROM up, but legs aren't going to last long doing it that way!
Unsoldered wrote the same bin with all 2B67 for first 15 double bytes & just added 1 hex to the very last digit so changed 16th double byte to 2B68 & the odo reading came DOWN 1km!
Hoping someone can figure maths theory to know how it calculates???
So 16 double bytes of 2B67 = 869,344Kms
& 15 double of 2B67 & 1 double of 2B68 = 869,343Kms
Hopefully someone can figure it out as it's painful soldering on & off, well actually soldering on is easy its more unsoldering does anyone have anytips for this I've tried solder wick but it doesn't remove all of it, so with what's left I heat up solder & gently pry EEPROM up, but legs aren't going to last long doing it that way!
by TazzI » Sun Apr 22, 2012 11:24 am
Seems I may have figured it out.. in a crude way.. but works!
2B67 * 16= 177776 = 869 344 KMS.
2B67 * 15 + 2B68 * 1 = 177777 = 869 343
(hex number increases, kms decreases)
therefore by that logic, 100 000 would be:
869 343 - 769 343 = 100 000 (therefore add 769343)
177777 + 769343 = 947120 (new total decimal value)
947120/16 = 59195 (decimal value you each location)
then to hex: E73B (new hex value)
Alright, now have a theory of how it works, lets try one of your previous readings:
To get 377296:
869 343 - 492047 = 377 296 (the difference)
177777 + 492047 = 669824 (new total decimal value)
669824/16 = 41864 (each location)
then therefore to hex: A388 (hex value)
WOOP! A388, same as your example on delco
Just to confirm it works, could you give it a go with the 100 000 reading Grunt?
2B67 * 16= 177776 = 869 344 KMS.
2B67 * 15 + 2B68 * 1 = 177777 = 869 343
(hex number increases, kms decreases)
therefore by that logic, 100 000 would be:
869 343 - 769 343 = 100 000 (therefore add 769343)
177777 + 769343 = 947120 (new total decimal value)
947120/16 = 59195 (decimal value you each location)
then to hex: E73B (new hex value)
Alright, now have a theory of how it works, lets try one of your previous readings:
To get 377296:
869 343 - 492047 = 377 296 (the difference)
177777 + 492047 = 669824 (new total decimal value)
669824/16 = 41864 (each location)
then therefore to hex: A388 (hex value)
WOOP! A388, same as your example on delco
Just to confirm it works, could you give it a go with the 100 000 reading Grunt?