Sorry to necro an old thread, but it's one of the top results when searchig for the fuel level PID for our cars, and now that I found more data I realized the thread is misleading.
Quote:
Originally Posted by CSG Mike
The only problem with FLI is that it's a raw reading, so it'll read *all over the place* when you're moving/driving. What you see on your dash is an interpolated average.
FLI is available on the AIM via generic canbus, but it's a relatively useless reading...
|
Quote:
Originally Posted by philooo
Seems like someone else is looking for fuel level for the RACEPAK system here
@ Poodles mentioned " in Torque, the fuel sensor is PID 2129"...if Torque app can get fuel level, I assume the $$$ Aim should be able to do it :S |
Quote:
Originally Posted by CSG Mike
It can. It's a raw reading, and is useless in the real world, without interpolation.
|
I logged the standard OBD PID for the fuel level and the
custom OBD PID 0x2129 during the recent track day at Buttonwillow.
It very much looks like 0x2129
is interpolated.
In fact, having looked at my data over a few track sessions, I haven't found
any issues with that data. Basically the fuel level is just constant when I'm parked, drops fairly linearly over time when I'm on the track, and stays constant after as I come back to the paddock and do my cool down.
Having that evidence, I feel like the 0x2129 can be very much trusted at the track.
I wouldn't rely on it being precise up to +-1 liter, so don't try using it to estimate how many miles you have till the next gas station... but it looks more than good enough to estimate the average fuel burndown rate.
Here's how the data looks like.
Yellow — standard PID, green — 0x2129, cyan line — lat G's.
