ABRP distance estimates off by 100 miles, is it me?

[Timeless Epoch]

Just got my Lightning about 10 days ago. Loving it so far.

Per many recommendations here and other places, I tried to use ABRP with a BTLE dongle. It’s been a complete scheiße show.

1) On the way to my destination about 320 miles away, after a second charge, the route turned to dashed lines and was not routing. When I restarted the route, it wanted me to go back to the very beginning and did not pick up where it left off. So I abandoned it and finished with Apple. I didn’t have any further charging to do anyway.

2) On planning my route back, it’s off by exactly 100 miles from both Apple Maps and Waze. How does THAT happen? It is affecting my battery estimates as well. Screenshots below.

Am I missing something? I don’t see anyone else on any forum complaining about this exact issue.

 

[TaxmanHog]

I noticed your starting point was 100% SOC, assuming that was actually the case and the ABRP default profile for a Ford Lightning extended range Platinum is factored for temperatures & terrain of the route, then refined by the live data based on your actual driving habits, leading to a 100 mile shortage.

Also note, the 300 mile potential range of a Platinum under 100% (if was actually showing that) is a massive falsehood, join any of our many threads where that is proven to be the case.

 

[PJnc284]

I noticed your starting point was 100% SOC, assuming that was actually the case and the ABRP default profile for a Ford Lightning extended range Platinum is factored for temperatures & terrain of the route, then refined by the live data based on your actual driving habits, leading to a 100 mile shortage

Think what he's saying is that abrp shows the total distance being about the same as apple maps/waze are showing just to the charger.

 

[Timeless Epoch]

Thank you and my apologies, this is not a range question. Just the distance to where I am now to “Mark Porter Ford”.

Apple: 207 miles
Waze: 207 miles
ABRP: 107 miles

Just in case it is important in a way I don’t understand, I will be starting off with a full charge from the hotel. That is why I overrode the starting SOC so I could plan this evening.

 

[TaxmanHog]

The ABRP projection shows:

Leg 1 107 miles using 54% of your battery ~71 kWh, averaging 1.51 miles per kWh [MPK]
Leg 2 107 miles using 47% of your battery ~ 62 kWh, averaging 1.73 MPK

What did you actually average over these legs or the entire trip?

 

[TaxmanHog]

ABRP: 107 miles

Might you be misunderstanding the ABRP screen?

It's showing the entire journey as 214 miles with the legs evenly spaced from the charger at 107 miles

 

[Timeless Epoch]

Lets forget the EV part of the planning for a second and drop back to basic A to B routing. ABRP is wildly off on just the basic routing. Apple and Waze are correct that this charger is 207 miles away.

The total trip is about 320 miles.

 

[TaxmanHog]

Lets forget the EV part of the planning for a second and drop back to basic A to B routing. ABRP is wildly off on just the basic routing. Apple and Waze are correct that this charger is 207 miles away.

The total trip is about 320 miles.

You waypoints in ABRP are indicating 214 miles total not 320 miles, is there another waypoint needed? I'm confused!

 

[TaxmanHog]

Try resetting the trip and pick the starting location at your actual location now

 

[Timeless Epoch]

You waypoints in ABRP are indicating 214 miles total not 320 miles, is there another waypoint needed? I'm confused!

My apologies and I really appreciate your taking so much time to assist.

The Waze and Apple estimates are for the first leg only. They are spot on. ABRP is way off. This first leg really is 207 miles. The whole trip is 320 miles, not 214, and that charger is not dead in the middle of the route. It appears that ABRP has calculated the first leg incorrectly and then just reused that number for the second leg. It is so weird. I’ve never had a route planner behave this way.

If anyone wants to try it, route from “GreenBrier Resort, White Sulphur Springs, WV“ to “Mark Porter Ford in Jackson, OH”. Toll roads ON.

 

[TaxmanHog]

My apologies and I really appreciate your taking so much time to assist.

The Waze and Apple estimates are for the first leg only. They are spot on. ABRP is way off. This first leg really is 207 miles. The whole trip is 320 miles, not 214, and that charger is not dead in the middle of the route. It appears that ABRP has calculated the first leg incorrectly and then just reused that number for the second leg. It is so weird. I’ve never had a route planner behave this way.

If anyone wants to try it, route from “GreenBrier Resort, White Sulphur Springs, WV“ to “Mark Porter Ford in Jackson, OH”. Toll roads ON.

EDIT 100% start and programmed 1.6 MPK what I average this time of year on a road trip

 

[Timeless Epoch]

Yes sir, THAT looks correct. if you pull out the stop at the Tesla charger (for comparison‘s sake), then you are right at 207 miles to Mark Porter.

I don’t know why mine found a 100 mile shortcut.

 

[PJnc284]

Got the same route as above. I just have my dest and charger percentage at 10%

 

[TaxmanHog]

Clear out the trip details and start from scratch, possibly the GPS "My Location" is not tracking accurately

 

[potato]

I wonder if your "Home" location is what you think it is. ABRP is probably planning an out-and-back hence the identical distances

Sponsored