OBD II "Distance traveled since codes cleared"
Posted: Mon Nov 29, 2021 9:21 pm
This might not be a Freematics related Question.
I adapted the firmware_v5 telelogger firmware to send Distance since code cleared (PID_DISTANCE) by adding "{PID_DISTANCE, 2}," to "PID_POLLING_INFO"
I do get some Distance values but they change... in a weird way.
at 15:20:00 the result of 0x131 was 4286
at 15:20:09 the result of 0x131 was 4358
at 15:20:18 the result of 0x131 was 4286
at 15:20:27 the result of 0x131 was 4286
at 15:20:36 the result of 0x131 was 4358
at 15:20:45 the result of 0x131 was 4358
at 15:20:54 the result of 0x131 was 4358
it basically switches back and forth until they decide to jump to 4359 or 4288 (left out 4287 for some reason) and later to 4360 (haven't driven since then)
Is this normal or a car related Issue? I drive a Volvo XC60 2015. I use a Freematics One+
I adapted the firmware_v5 telelogger firmware to send Distance since code cleared (PID_DISTANCE) by adding "{PID_DISTANCE, 2}," to "PID_POLLING_INFO"
I do get some Distance values but they change... in a weird way.
at 15:20:00 the result of 0x131 was 4286
at 15:20:09 the result of 0x131 was 4358
at 15:20:18 the result of 0x131 was 4286
at 15:20:27 the result of 0x131 was 4286
at 15:20:36 the result of 0x131 was 4358
at 15:20:45 the result of 0x131 was 4358
at 15:20:54 the result of 0x131 was 4358
it basically switches back and forth until they decide to jump to 4359 or 4288 (left out 4287 for some reason) and later to 4360 (haven't driven since then)
Is this normal or a car related Issue? I drive a Volvo XC60 2015. I use a Freematics One+