pcmhacking.net

Would a few VT VX clusters with VIN's and model be helpful in working out where info is stored? I have 19 "spare" VT VX clusters to play with.

after cleaning up my bin file with a text editor so that it now corresponds to the VT bin files
although i have all the security codes for my VX there is not a single code that i could match, i'm beginning to think that with the VT-VX , the only info in the clusters are the ODO and only data related to the cluster trip,distance to go etc.

i also think that all other info is stored in the BCM's EEprom, so i now have 1 on the way

Just a thought.......

88GreenVN wrote:Would a few VT VX clusters with VIN's and model be helpful in working out where info is stored? I have 19 "spare" VT VX clusters to play with.

Sounds like that would be useful, knowledge of their VIN, airbag config, v8/v6 and any other settings would be great, they must be saved in there somewhere in the NEC chip. Changes can be made with the cluster outside of the car so its not saved in the bcm, bcm is a whole new game!
My nec programmer never rolled up, got refunded luckily. I decided to try another way round and attack the cluster through its serial communication line. There is PLENTY of info in there, just need to figure out what is what! Should be able to do most changes through aldl. Nec prog would be needed for the odo through.

madmn wrote:
i also think that all other info is stored in the BCM's EEprom, so i now have 1 on the way

Just a thought.......

There is a lot on the BCM, keep in mind that if you are going to post your dumpd from the BCM it has all the info to make a key to your car, immobiliser and the mechanical key.

BPJ wrote:

madmn wrote:
i also think that all other info is stored in the BCM's EEprom, so i now have 1 on the way

Just a thought.......

There is a lot on the BCM, keep in mind that if you are going to post your dumpd from the BCM it has all the info to make a key to your car, immobiliser and the mechanical key.

I thought so when i tried to clone my single to the triple it stuffed all calibrations including the readout , as with any other cluster that has a separate EEprom it's doable

all the info is in the BCM and transferred via serial

i still want to see the inside of a S2 VX cluster

But them how is S1 instrument cluster then re-calibrated for a S2 instrument cluster and vise versa? Cant all be stored in the BCM, I though BCM was for security related information such as key code ect.

I have replaced BCM's with there being no affect on the cluster so I think it is safe to say that the Km's are not in the BCM, only stuff related to the cars security and things related to the body of the car, electric windows, central locking... stuff like that.

all VX clusters are S2 wether single or triple window and that's a pic from my single window

holden stuffed again with the VE' s between 2007 and 2008 cluster weren't interchangeable

I thought most VE clusters were not interchangable without the correct programming.

Is that a picture of a VX cluster? I thought there was S1 and S2 VX clusters?

The series 2 clusters have a large P in the bar code lable - Level 3oP

The supercharged series 2 clusters have Level 3siP (si being a new found code for me)