ABRP currently offers two ‘views’ of a trip once on the road: 1) the overall trip and 2) the next waypoint. I’m suggesting changes to enhance the usefulness of both.
I’ll address the big picture first - the overall trip.
If the ‘round trip’ option is selected, I’d argue the Big Picture becomes too big to be useful when on the road, even if in the planning phase the total picture is valuable.
A round trip is made up of ‘out’ and ‘return’ legs, each leg of which is an important sub-element of the journey. They may even be separated by an overnight stop. They may involve very different energy economies, such as a dive uphill to the turnaround waypoint, then a more economical downhill return.
Of course one might just create a separate trip, but that has some downsides. One solution would be to have different ‘levels’ of waypoints, say ordinary and major, with data on each leg between major waypoints being able to be scrutinised separately.
Which brings me to the ‘view’ of metrics on legs between minor waypoints.
At present limited data is displayed on the main driving screen, just current SoC and Arrival SoC. Missing are the important, IMO, Duration to Arrival and Time of Arrival.
The addition of these data fields would not be space hungry, but add significantly to screen usefulness.
A right button of this cluster field could switch between data on the current leg between minor waypoints and the current progress point and the next major waypoint.
Please authenticate to join the conversation.
Open
💡 Feature Requests
4 months ago

Daryl Sturgess
Get notified by email when there are changes.
Open
💡 Feature Requests
4 months ago

Daryl Sturgess
Get notified by email when there are changes.