Trip time is roughly twice what it should be

[Buck]

I hesitate to report this as a bug since I'm probably doing something stupid.  I created a route I've used before in a Tesla using a Chevy Bolt.  It's in the midwest of USA on interstate highways with two charging stops. A trip that should take 8 or 9 hours is reported as 17 hours.  And it's the drive that's elongated, not the charging stops. I've tried switching the vehicle back to Tesla and it still shows an excessively long trip.  Oddly, the iPhone app reports a different time, but is also much too long. 

What settings should I be checking?

[Trisc64]

I'm getting the same problem. Google Maps gives an ETA of 3 hrs 40,  but ABRP estimates is a crazy 8hr 55 mins!

 1 x charging stop of 15 mins. Charging overhead time set to 5 mins

[Katya-ABRP]

Hi @Buck, @Trisc64,

Check what's set for reference speed and max speed in your settings. Should you not find the error write us an email or report a bug via the support & feedback section at the bottom of the settings menu and make sure to include a link to the plan.

/Katya

[Buck]

Both the web app and the iPhone app have these settings:

Reference Speed  100%

Maximum Speed  65 mph

 

Note:  I deleted a manually added waypoint in the web app and let ABRP recalculate the route with just the two endpoints and it shows a reasonable time, even though the waypoint matched one of the recommended charging locations.  The phone does not show any manual waypoints but still shows an elongated trip time. 

Edit:  I saved the plan from the webapp and loaded it on the phone.  The phone now shows a normal trip time. My biggest concern was that I couldn't trust the app.  I guess I've found a workaround. 

Edited August 4, 2022 by Buck

[Buck]

I have two saved plans (for the adminstrator only) in my profile.  They look the same and are from and to the same locations.  One 8 hours and 39 minutes (407 miles) and one is 17 hours and 51 minutes (407 miles).