Arrival SoC Way Off On Some Routes
ABRP is pretty much dead on when calculating the arrival SoC traveling southbound between Tacoma, WA and Portland, OR in the US. On the reverse, northbound, trip it is off by a significant amount (say 10% SoC at the destination, even when “overcharging” at the charging stop) – enough to require second charging stop or a “white knuckle” arrival at the destination.
I’ve noticed this on a couple of recent trips (but don’t recall it from earlier trips, so it may be a change). I don’t think it is related to significant weather differences, except perhaps the wind.
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments3
ABRP User #811399
Jul 8
For whatever it might be worth. I did a similar drive (Gig Harbor, WA to Beaverton, OR) a couple of days ago using 7.1.3 and the arrival SoC was as expected (the value of the predicted SoC at arrival slowly climbed as the return trip progressed). Maybe 7.1.3 or one of the intervening versions fixed something or ???.
Nikola
Jun 17
Hello Doug,
I planned a route from Tacoma to Portland and reversed, i didn’t get a noticeable difference.
Can i ask what car you were driving and if you have the route saved?
ABRP User #811399
Jun 17
The problem isn’t with the planned route, it’s with the plan vs. the actual drive. The plan requires much less energy than is consumed in the actual drive. I usually drive the speed limit with cruise control engaged, so I don’t think the cause is different driving behavior on the outbound trip vs. the return trip.
In my experience with ABRP, it is rarely off by more than a few % of the arrival SoC and aside from these trips I can’t think of a time when the arrival SoC estimate has been dropping as the trip progresses – usually it is either holding firm, or on longer trips the estimate of the SoC at the destination is going up.
The car was an EV6, I don’t have the route saved, but it would be easy enough to recreate the route.