Quote:
Originally Posted by euromodder
An extensive hypermiling feature set will sell better to the ecodriver's niche-market - but we're below the 1%-ers  |
This is true, but I want to see what can be done if we really focus on ourselves. Part of it is scratching my own itch, certainly.
Quote:
Originally Posted by euromodder
The internet connection isn't always on or working though.
Don't fall into the developer's trap that the 'net always needs to be working for the app to function properly
|
Sure. There needs to be fall-backs, if not because 3G is unreliable, then at least because I want it to work reasonably on an iPod Touch.
Quote:
Originally Posted by euromodder
Must haves :
- logging
- high frequency OBD polling, i.e. realistic measurements updates.
- % time and distance idling
- % time and distance in which gear
|
Of those, the only thing that presents a real challenge would be high-frequency OBD polling. How high is sufficient? I would guess something like 1/5th of a second would be reasonable. Would you agree?
Quote:
Originally Posted by euromodder
CdA is relatively easy to find, but Crr ?
|
My understanding is that a coast-down test will give you both -- CdA as the "m" component and Crr as the "b" component in y=mx+b.
Quote:
Originally Posted by euromodder
You could maybe built a feature that grabs the required time/speed data and calculates the drag ?
|
You're reading my mind, euromodder.
Quote:
Originally Posted by euromodder
You'd need to have the topography of the road ahead, actual vehicle weight, RR, ... this would get complicated very quickly.
|
I was just imagining the *vertical* rise.
Of course, there's another (possibly better) way to do this -- exploit the "critical points" that we make during our routes. You know: "Passing this sign I need to go 22 mph to juuust reach the stop on the hill." Put those in somehow, and then give feedback on the best time to EOC, for instance.
Love all these great ideas! Thanks, eurorider.