piev said:How should this be read?

OBDZero stores two files PID_..txt and PIDint_..txt. In PID_..txt all of the number are in hex apart from the time and date. In PIDint..txt the bytes are converted to integers while the PID is still hex. This save a step when working with the data.

In the data piev posted above the PID 346 byte 3 has at different times the integer values 0, 2, 32, 48, and 95 where 32 is by far the most common.

When I convert 2 to binary using Excel I get 00000010. 32 gives 00100000, 48 gives 00110000 and 95 gives 01011111. I couldn't find a standard for numbering bits in a byte but it appears that most agree with Excel that the 1st bit from left to right is the msb = 127 and so on. As 32 is the value of byte 3 almost all the time then the third bit is probably the ready light. Byte3 was 48 at times 16:37:11, 16:39:34, 16:39:36, 16:46:37, 17:31:55, 17:31:57, 17:32:00 and 17:33:16. At these times the 4th bit was 1 and this was probably the turtle light. Byte3 was 95 at times 16:39:40, 16:39:48 and 16:46:59. At these times the ready light was off and the turtle was on and probably the other lights on the dash as well. Here is one series:

16:39:28 | 32 |

16:39:31 | 32 |

16:39:34 | 48 |

16:39:36 | 48 |

16:39:38 | 0 |

16:39:40 | 95 |

16:39:42 | 0 |

16:39:45 | 0 |

16:39:48 | 95 |

16:39:50 | 32 |

16:39:52 | 32 |

16:39:54 | 32 |

The ready light was on (byte3 =32). The turtle light came on (byte3 = 48). piev turned the car off (byte3 = 0) then turned the car on (byte3 = 95). (maybe twice?) Then the ready light was on (byte3=32) and all was in order. Now comes the hard part figuring out why the turtle came on.

Cheers

David