Skip to main content

ABRP doesn’t honor destination SoC when planning

Bug Reports

Hi there. Can you please explain why the app doesn’t honor my preferred destination SoC? As an example, I let the app plan a trip from Panama City Beach, FL to Brookhaven, GA and it’s showing 14% SoC at destination while I clearly have 18% set.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by ABRP User #1567406 ·
Status: In Progress5 comments

Log in to comment and vote

Comments5

  • Mahde - ABRP changed status to Completed
    Team•

    Jul 6

    Pinned

    Hello @ABRP User #1567406,

    This is due to your max charge limit being at a percentage that would result in the plan prioritizing arrival at a lower percentage instead of having to charge your car for the last percentages (since your max charge limit is at 82% for charging). If you want to arrive with higher percentage, please adjust the max charge limit so you arrive with 18%.

    • ABRP User #1567406

      •

      Jul 6

      Is there a way I can prioritize SoC on arrival? These are Tesla superchargers so if you set the target SoC much above 82% then you’ll get charged congestion fees if the station is busy.

      • Mahde - ABRP

        Team•

        Jul 7

        Unfortunately, the 82% max charge limit makes it so that the last 3% needed to charge is not necessary for the plan so you will have to increase this number.

    • ABRP User #811399

      •

      Jul 7

      I’m not following this… Arrival SoC (either at the destination or at a charger) seems like something that should be inviolate. For one thing you don’t know why the user set that number: for example do they want to be sure to arrive at a destination with no charging available with enough charge to get to a charger the next day? If so, you’ve just put them in a very difficult place.

      At an absolute minimum ABRP should very clearly warn that it did not produce a plan that meets the user’s parameters and suggest what to do to fix the problem. Users should not need to be versed in ABRP lore and workarounds to get it to create plans that meet the input criteria.