|
I am thinking of adding a trip data recall function which will allow the user to save trip data for later recall. This could be useful for comparing two or more runs. Say you have an idea for a new route to work. Is it faster, shorter, uses less fuel?
I was thinking this would likely be restricted to Outings (generally a one way trip) but would TRIP or TANK data be useful as well?
The data set (fuel used, time, distance...) could be named for easier recall about what the trip was about. An automatic name could be like "Outing A", "Outing B"... or you could over ride that with a new name like a driver name or street name. Once named, we could easily sort them by shortest or longest distance, fastest or slowest time...
Would distance, fuel, and time be enough or should other data (maybe wasted) be included too. (If we include just three PID's the name would take the other PID. Additional PIDs could be utilized with two screens per trip, or a title screen, or selectable PIDs...)
Saving the data could occur automatically prior to a data reset, or perhaps via a button selection (like all three buttons at once.)
Anyway. What are your thoughts. Would you like to see this feature?
|