Couldnt really find a section for this..

[Holden202T]

this is what I got from it, haven't had any time to do much more with it though.

and from memory the odometer was 24xxxx but I am not sure other than I was sure it was up there.

read1.bin

[Holden202T]

this looks good matches what im seeing in the hex editor!

dash reading.jpg

[VX L67 Getrag]

Nice Work Holden202T, it's been a while since I played with this stuff & looks like you've got t sorted!

[Holden202T]

was pulling my hair out for a while trying to get it all working! should have checked the solder joints first hehe!

[j_ds_au]

was pulling my hair out for a while trying to get it all working! should have checked the solder joints first hehe!

You'd have made life easier for yourself if you'd have offset the SIP socket by 0.1" to line up with the ZIF socket pins.

Joe.

[Holden202T]

yeah my first design was like that, then I thought nah i'll offset them and make it more compact lol!

the other half of the issue is I made the pads too small and when I was drilling the holes its ripped off some of the pads, so less area to solder to.

[Holden202T]

so would just like to see what peoples thoughts are on this:

normal read

read1.jpg

then every one in 10 or so one of the three in the red box is different usually by one character

read2.jpg

is this something do with with settings on the com port or PC ?

im more just worried that if it does it the one time I try to write to the chip it might screw it up ?

[antus]

B5 = 1011 0101
35 = 0011 0101

So one bit is not reading correctly sometimes.

I wouldnt worry about it. It sounds like you have enough consistent reads that you can be sure that one or the other is correct (actually it would be the B5 thats correct because the data is there three times and the other copies are consistantly B5), and you wont damage the chip even if it writes incorrectly. You can read it back a couple of times to be mostly sure the data has written correctly and if it hasnt the dash will detect the checksum failure and give you some kind of error (or decide 2 out of 3 must be correct and fix the odd one out itself), but if you need you can repeat the process and try again.

[Holden202T]

yeah cool thanks

[j_ds_au]

so would just like to see what peoples thoughts are on this:

normal read

read1.jpg

then every one in 10 or so one of the three in the red box is different usually by one character

read2.jpg

is this something do with with settings on the com port or PC ?

im more just worried that if it does it the one time I try to write to the chip it might screw it up ?

Hmmm ... might be a timing issue? There was some mention about timing back on page 18.

You might also try adding a small decoupling capacitor 10-100nF between the supply pins on your PCB.

Joe.