Using Tesla nav button/ limitations?

[Darhall993]

When using the Tesla nav button the nav system doesn’t recognize the supercharger as such it sees it as an address, is this by design? I’ve attached two pics to help 

[Jason-ABRP]

Unfortunately yes, we tried many different tricks to get the Tesla Nav to recognize that we were sending it a supercharger.  That way it would pre-condition your battery for supercharging.  What may work (I haven't tried it) is sending the destination to the nav, then selecting the supercharger from the map once it auto-pans, and picking that as your destination.

[Jojo]

Hello Jason

I do it exactly as you said (picking Supercharger after auto-Pan). It's not nice, but the Tesla Nav Interface is obviously not capable enough to do it better. It also fails to find destinations send from the sharing button in Android. It's the best you can do.

I also often use the "Tesla Nav" button in ABRP, due to the lag of "intermediate destinations" within the Tesla navigation system, to send the next destination to my Tesla.

Often, when I'm charging at the supercharger it doesn't work because ABRP does not recognize, that I've reached the supercharger already. So it doesn't send the next destination but always the Supercharger I'm already sitting at. Maybe it is due to the unprecise information between GPS position of the charger in the map and the real position or the difference between "ABRP position" and the supercharger selected after auto-pan. See procedure above.

Could we have a bigger radius around a destination, where ABRP recognizes the "reaching" of a destination, so ABRP sends the next destination when hitting "Tesla Nav"?

Or could we have a button behind each individual destination in a plan to send this specific destination to the  nav? Something like that.

Thanks

 

 

Edited August 12, 2019 by Jojo