Hey @SamyAbi have you solved the problem?
I experienced something similar and I think fix from github fixed it:
#if ENABLE_OBD
if (sys.devType > 12) {
batteryVoltage = (float)(analogRead(A0) * 12 * 370) / 4095;
} else if (state.check(STATE_OBD_READY)) {
batteryVoltage = obd.getVoltage() * 100 ...
Search found 2 matches
- Wed Dec 08, 2021 4:48 am
- Forum: Freematics Products
- Topic: Possible reason for ONE+ (H) to stop sending data
- Replies: 11
- Views: 99167
- Mon Nov 29, 2021 9:21 pm
- Forum: Freematics Products
- Topic: OBD II "Distance traveled since codes cleared"
- Replies: 0
- Views: 8424
OBD II "Distance traveled since codes cleared"
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 ...
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 ...