-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reading Odometer values #272
Comments
hello! i'm a complete novice at this and new to coding. however it seems most ecus do support being able to pull mileage off the ecu. reading the documentation https://python-obd.readthedocs.io/en/latest/Custom%20Commands/ it seems you can make a custom command perhaps to pull mileage from the ecu! i'm not sure how to go about it but hopefully it's somewhat helpful :) |
i stand mistaken. i asked chatgpt for the hex code for mileage info however it seems that doesnt exist. "Mileage data is often stored in the vehicle's EEPROM chip, not directly accessible via the diagnostic bus for security reasons. Some OBD readers might provide mileage information indirectly by calculating distance traveled since certain events, but this varies by reader and vehicle " ^ from chat gpt. |
I am concerned how much you trust a chat bot. 2019+ vehicles were mandated in California to provide odometer the codes are: A6 166 - expect 4 bytes Before 2019 its not so easy - relying on either avg speed * engine hours, or distance traveled before + after a CEL Took me 4 minutes to google it: https://en.wikipedia.org/wiki/OBD-II_PIDs |
thank you for the knowledge :) still learning as i go! |
the commands you have listed are car-dependent. |
Hello
is it possible to read the odometer value ?
i have checked all the commande listed on the wiki but it does not contain it.
maybe the odometer is part of the Non-sensor data ?
The text was updated successfully, but these errors were encountered: