pcmhacking.net

festy wrote:

The1 wrote:
doesn't work
CA35 FF00 15EA 20DF

00+15+20=35^FF=CA

You need to convert to LSB so your programmer can read the bin correctly - the line above is still MSB.

20df 15ea 00ff ca35

So that should be Least SB?

The1 wrote:

festy wrote:

The1 wrote:
doesn't work
CA35 FF00 15EA 20DF

00+15+20=35^FF=CA

You need to convert to LSB so your programmer can read the bin correctly - the line above is still MSB.

20df 15ea 00ff ca35

So that should be Least SB?

So 001520 is the target.
First the digit-pair nibbles -
00 15 20
Next, add the complimentary checksums, 00^FF, 15^FF, 20^FF
00FF 15EA 20DF
So now to get the checksum word for the group, add the digit pairs together - but remember these are hexadecimal ((00+15+20)^FF) = CA, and has cmp of 35
CA35 00FF 15EA 20DF
So that's the 4 word block, but in MSB (the 8051 MCU is big endian).

For LSB (purely so your x86 pc can interpret the bin to program the '244 with),
0=0,1=8,2=4,3=c,4=2,5=a,6=6,7=e,8=1,9=9,a=5,b=d,c=3,d=b,e=7,f=f
so
CA35 = 35CA
00FF = 00FF
15EA = 8A75
20DF = 40BF
but LSB being the reverse of MSB, 1234 would be 4321...
35CA = AC53
00FF = FF00
8A75 = 57A8
40BF = FB04
So there you have the words in LSB format, AC53 FF00 57A8 FB04.

Does that make sense?

Thanks HEAPS!! , i know where i was going wrong now, didn't use the nibble table and convert before MSB to LSB.

So when you releasing a test version of your program?

also by accident i put the chip in backwards once and it turns on like normal!! lolz woops. So you must be able to trigger modes via there somewhere

The1 wrote:

I was going to post the same pic, but wasn't sure anyone else would get it
Congrats on nailing it - i imagine it's been driving you nuts being so close!

My program isn't much use without my hardware, and I don't have any plans to release either of them.

So I'll just share another screenshot for now

fair enough, there's plenty of info in this thread anyway, not that legally this thread should exist prob.

Yeah the thread was discussed by the mods But we let it run as getting stuck in to the inner workings is really what this site is about. If everyone did the right thing it could be a very handy tool for those replacing clusters but wanting to keep the kms of the vehicle accurate.

Yeh that's it thanks vl, without this thread i wouldnt have learnt some more, now to crack a vt cluster open

This thread is a bit grey area. I think that information should be free, as it can be used for good, but if somebody misuses it then it is them who should get in to trouble. Anybody can swap a dash without this thread.

But i agree, there is enough info here for the geeks now.

Fantastic work there guys. Looks like this was far more difficult than the troubles I had working with VE Clusters.

I am in the same situation as the moderators of this site at the moment.
I originally started working with VE clusters to try and get them so as you could swap them around for different models.
(I.E. fit a HSV cluster to an Omega, fit a triple LCD cluster to a car with a single LCD cluster).

Whilst working on this, I also found how to change the Odo readings to whatever value I wanted.
I have enough information on my website for geeks like ourselves to do this themselves, however I want to make things easy for people to program their clusters themselves.
I have written some php code that will generate a VE EEPROM .bin for uploading to a cluster.
This code will set the Odo reading, the Cars VIN number, as well as other settings and options to get the cluster to work.

However, its the setting of the Odo reading that has got me worried.
The code works 100%, but I obviously do not want this feature to be abused.

I feel the information should be free and available for anyone to use. (I would like to think that most people will use it for good, not evil), however I know this will not be the case.

Does anyone have any suggestions.

(P.S. The VE Cluster EEPROM locations are freely available on the web, if you do a google search for VE Cluster EEPROM).
Also moderators, please feel free to copy the EEPROM information up on delcohacking if you feel it may be of interest to your forum members.

Cheers, and looking forward to posting much more
Matti