Waypoint charging options

[REckard]

I am trying to add a waypoint with an L2 charger but I am forced to include a time or "charge to" value.  I'm hoping to have the ability to just add the kW for the waypoint and let the servers determine how long I need to be there to continue the trip.  When I only put in the kW for the waypoint and nothing else, the mapped route doesn't set up any charge times at the w/p even when the car needs juice to complete the journey.  This would come in handy when adding personal L2 connectors from a home owner's w/p (as listed in PlugShare and when given permission from the respective homeowner).  I don't know how long I need to be at this stranger's house, but I know I need to charge up to something to make it home. TIA

[Jason-ABRP]

6 hours ago, REckard said:

I am trying to add a waypoint with an L2 charger but I am forced to include a time or "charge to" value.  I'm hoping to have the ability to just add the kW for the waypoint and let the servers determine how long I need to be there to continue the trip.  When I only put in the kW for the waypoint and nothing else, the mapped route doesn't set up any charge times at the w/p even when the car needs juice to complete the journey.  This would come in handy when adding personal L2 connectors from a home owner's w/p (as listed in PlugShare and when given permission from the respective homeowner).  I don't know how long I need to be at this stranger's house, but I know I need to charge up to something to make it home. TIA

Hmm, this is a feature we don't really support just yet, the way I currently do this when presented with this option is to set the charge-to% to 100, then run the plan.  Then subtract whatever I don't need off of the 100%.  So if it gets me to the next charger at 35%, then I reduce the charge-to % by 25 to 75%, so I arrive at 10%

[REckard]

Agreed, it can be done manually. But when using the in-car browser, we have to wait for the plan to populate (painfully slow) then do the math and run the plan again. If the plan knows the waypoint kW, then it could calculate the time automatically saving the user a step. Again, this is mostly painful when using Tesla's MCU1 in-car browser.  I love using the mapping program, this was merely a feature request, nothing wrong with the existing behavior.