Alright.. Im assuming what I had before then was probably correct.VL400 wrote:No, there are A/D values and converted values.
A/D are the raw counts, or filtered counts (to reduce noise on the sample). Coolant voltage from the A/D is X / 51.2
Then you may also get the converted value from the ECU - ie linearised coolant that you use the (X * 0.75) - 40 with.
Another example is throttle position, you get a 0-5V value of the voltage read by the ECU (maybe is 0.6V for closed throttle to 4V for 100%) that you use X / 51.2 to get a voltage from the A/D counts, this is the TPS A/D or TPS voltage item. The ECU then scales this so that the learnt range (say 0.6V to 4V for closed to WOT) to cover 0-100%, being an 8bit item so you can use X / 2.56 to get a 0-100% reading when converting the TPS % item. Two differernt items for different tasks in the ECU.
There are multiple RAM locations for sensor reading. Take coolant as an example, there will be a raw reading of the A/D, a filtered A/D, a linearised value, a filtered linearised value, a non-defaulted value, a defaulted value (what gets substituted/used when a fault occurs). There are then others for special parts of the code, like the last reading, the startup coolant reading .... and so on
Yeah that does make sense then. Since different bytes in the ALDL stream correspond to the raw/filtered counts value and linearised value. Two completely different bytes.
That should be it I think for the initial build.
