Page 15 of 23

Re: VT-VX Clusters

Posted: Thu Jan 31, 2013 7:46 pm
by VX L67 Getrag
If you can unlock eeprom & get bytes from the device both VT-VX are the same & that was all the info I could find & it all lines up with direct dump off actual VT cluster eeprom & VX clusters respond with same/similar data to all byte locations!

Re: VT-VX Clusters

Posted: Sun Feb 03, 2013 2:43 pm
by madmn
ok i've been looking for that info and didn't find anything, some locations might be the same but the clusters are different in many ways, the stepper motors are and some vt clusters don't have TC or ABS etc,etc...

anyway i've made a test VX cluster that i can write to and then reconnect the MCU without soldering the pins, it now works perfectly so i'll be able test some of those locations you've posted
testcluster.JPG
testcluster.JPG (109.95 KiB) Viewed 4406 times
000000.JPG
000000.JPG (98.57 KiB) Viewed 4406 times

Re: VT-VX Clusters

Posted: Fri Feb 08, 2013 9:34 am
by VX L67 Getrag
Yeah ALL the locations are the same, where you see gmh options, enables & same for vdo there actually bitmasks so each byte has 8 options including ALL you've mentioned!

But looks good on the vx cluster!

Re: VT-VX Clusters

Posted: Mon Feb 25, 2013 2:31 pm
by kody
You guys never seem to be able to come across something that when you put your minds to it that can changed.

I got hold of a clip and thought I would have a play around with this myself.
I have a cluster here that I did a read with using a gq4x programer, the cluster had 399615 kms on it. Attached is the bin file and after having a look it all seems to have read ok.
vt mick.bin
(256 Bytes) Downloaded 271 times
The thing I can not work out is when I go to write back to the chip I seem to end up with a write error,
c:\documents and settings\clint\desktop\vt mick.bin.
Speed = 2
ID check skipped
Writing... Code
Elapsed time: 3.32 seconds.
Device write completed OK
ID check skipped
Verifying... Code
Verify Failed, Address=0x000000, Device=0x00, Buffer=0x9E
Verify Failed
Elapsed time: 1.91 seconds.

I have added a 9v power pack to the gq4x as I thought this might have been the problem, but it has not seemed to help.
Any suggestions or ideas on what I am doing wrong would be great

Thanks

Re: VT-VX Clusters

Posted: Mon Feb 25, 2013 4:31 pm
by VX L67 Getrag
Not sure how you did it as I tried with a GQ3x & could never get the dump on board, but once I took chip off & then read & wrote it was fine!

Maybe there is extra power needed to write to it while IC, or a security measure while IC?

It does look like you have selected correct chip & settings so not too sure as it's uncharted waters for me!

Re: VT-VX Clusters

Posted: Mon Feb 25, 2013 4:55 pm
by kody
Does the chip read seem correct to you?

I am wondering if the cluster needs to be powered up to write to the chip while it is on the board

Re: VT-VX Clusters

Posted: Mon Feb 25, 2013 5:01 pm
by VX L67 Getrag
Yeah Chip read looks o.k. to me without looking SUPER close!

I tried all ways of even reading IC with powered up or not & didn't seem to help me, hence why I had no experience with IC as I desoldered & resoldered & worked fine!

Re: VT-VX Clusters

Posted: Mon Feb 25, 2013 7:03 pm
by Tazzi
I always thought powering the board up would give the required juice to read. Last option would be to also use that additional power supply on the gq4 with the cluster powered up although not sure if thatll fry something :?

Or bite the bullet and lift the eeprom off.

Re: VT-VX Clusters

Posted: Mon Feb 25, 2013 7:47 pm
by kody
Yeah soldering skills are not very good, might have to have a look around for a 12 v power pack to run the cluster and might use the 9v pack to give the gq4x some more juice.
If it all goes bad :s I will just get another cluster to have a play with (y)

Re: VT-VX Clusters

Posted: Mon Feb 25, 2013 7:50 pm
by kody
I think I can get it to read as I got my last spare dash here and it seemed to read ok. Just when it comes time to send the bin file back it does not want to play the game.
vtsc.bin
(256 Bytes) Downloaded 299 times
194,463 kms

lol now have 2 clusters here with odoerror