pcmhacking.net

just use this line all the time 01 01 D9 26 FF 00 DF 20 worked for me so far

The1 wrote:just use this line all the time 01 01 D9 26 FF 00 DF 20 worked for me so far

I've just got the reader/writer working after changing PCB boards. I tried the working set of digits (from 148856.bin) and it worked. I have several working sets of numbers so will try a mix of them over several ranges of KMS - then run it in the car for a while.

The good news is so far all 4 I've done today (with the same 8 digits) on the bench tests pass the diag mode.

So looks like things are back on track. Now to find out what makes the set of digits work - how to calc that!.

Do you need to know why they work? If the original 8 bytes do the job, why not just use those each time?

festy wrote:Do you need to know why they work? If the original 8 bytes do the job, why not just use those each time?

Hmmm - would I like to know - you bet - Will I ever know - maybe not.

And Yep - using the original 8 bytes and working fine now

I've looked at all the readings I've taken from ODO chips removed from the PCB and all have a differnt 8 bits of data.

So far the test I've done the 8 bits from 1 ODO reading will not work in another. It will pass the ODO reading test but not the "in cluster Diag test"

I'll run a chip in a socket for a few months - taking readings every other week to see if and when the first 8 bits of data change.

88GreenVN wrote:I've looked at all the readings I've taken from ODO chips removed from the PCB and all have a differnt 8 bits of data.

Can you post the first 8 bytes of each (or the whole bins), along with the cluster model it came from?
After you get the 'FAIL', is the bin modified at all by the cluster?
From memory there's a couple more checksums in that section of the bin, would be interesting to see what yours look like after a 'FAIL'...

So far the test I've done the 8 bits from 1 ODO reading will not work in another. It will pass the ODO reading test but not the "in cluster Diag test"

Are you trying them in the same model cluster that the data came from, or swapping them around?

Some back ground on the trip computers.

There are only 2 types of trip computer in the VN to VS to work with. The VP has modified instructions for the fuel flow calcs but still has the same configeration for low feul and cruise as the VN. The VR VS has them swaped over so if you fit a VS trip to a VN cluster - it may look and appear to work correctly but it will show low fuel warning for over speed and over speed for low fuel and cruse contro; will not engage. But they will count kms in any car from VN to VS.

Now to my testing. I'm using the same VP cluster case and trip PCB with a socket in it for swapping out ODO chips for testing.

I get the failed in the middle screen if I use any other 8 bits of data - other than the "master key set of 8 bits"

I'll post up the .bin files as I take reading.

OK here is some 250,000 kms .bin files.

4 files within 5,000kms all have different first 8 bits of data

The odo chip I'm currently testing has only added 40kms so far and still has the same master first 8 bits.

I can try it in a different trip computer to see if that changes the the first 8 bits.... yes i shall try that tonight.

What model is each of these bins out of?
What model cluster and trip computer are you testing them with?

festy wrote:What model is each of these bins out of?
What model cluster and trip computer are you testing them with?

All 4 odo readings are from the VR/VS trip computers and being tested in a VP S2 cluster.

Adding a few hundred kms to the test unit has not changed the first 8 bits.