Skip to main content

Departure SoC is not restored when loading a saved plan (v7)

Since the update to v7, saving a plan does not persist the manually set Departure State of Charge. When reloading the plan using the "Destinations Only" option, the app reverts to the current live SoC or the default value instead of the saved one.

Steps to Reproduce

  1. Create a route with at least one destination.

  2. Manually edit the Departure Stop and set a specific Departure SoC (e.g., 90%).

  3. Plan the route and Save the plan.

  4. Clear the current map/route to return to the start screen.

  5. Go to "Saved Plans", select the plan, and choose "Destinations Only".

Actual Result: The route loads with the correct stops, but the Departure SoC is ignored and replaced by the current live vehicle SoC or a pre-selected default value.

Expected Result: The Departure SoC saved within the plan should be applied, even when loading as "Destinations Only" (as is already the case for Arrival SoCs at subsequent waypoints). This was also the behavior in previous versions.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Status: Completed2 comments

Log in to comment and vote

Comments2

  • Linda ABRP

    Team•

    May 8

    This is fixed and will be out in the next release 7.1.0.

  • Linda ABRP

    Team•

    Feb 18

    Hi

    Thanks for reporting this. I have sent it to a colleague so it can be fixed.