SF to LA trip: "No route found to this location" when trip planner turned on

[xanatos]

Wondering if anyone has seen this before. I am located in SF area. If I try to navigate to a location in LA with the trip planner turned on, it churns for a while ("finding superchargers for your trip") then says "no route found to this location".
Yet if I turn off the trip planner, it will churn for a while ("calculating route") and properly route my trip. I tried a couple of different addresses in LA and all have the same issue.

Is the trip planner function somehow broken and not not able to route properly? Can someone in SF area try the same destination on their nav with trip planner enabled and see what happens?

Pics below:

 

[Big Dog]

to paraphrase Erma Bomeck (LA): 'there is no there, there'.

 

[Need]

Are you doing this when your car has a low SoC? Maybe it thinks that you can't even make it to the first Supercharger with your current SoC so it just gave up on the planning.

 

[xanatos]

Are you doing this when your car has a low SoC? Maybe it thinks that you can't even make it to the first Supercharger with your current SoC so it just gave up on the planning.

thats a good theory, but no, the screenshots are from this morning when I had 220+ miles range left...

 

[bmah]

TL;DR: It worked for me.

Personally, the early experience that a number of people reported with the trip planner around multi-charging-stop trips led me to turn off the trip planner and only rely on the navigation system to get to the next Supercharger. I do the higher-level planning using something like EV Trip Optimizer or A Better Route Planner, and then just navigate to the "next" charging stop, so I can put up the energy graph to see my project energy usage. Actually between SF and LA, you almost don't need to do any planning at all, with two independent routes (I-5 and US-101), and enough density that you can skip chargers on either route if you want.

Anyway to directly answer your question, I just tried it now with your destination in Arcadia, and it routed me to Harris Ranch (6% reserve) and then Bakersfield. S85D with 2018.21.9, new nav, non-vector CID maps, 89% charge (probably equivalent to 235-240 RM). Personally, I like shorter driving legs, so I'd probably override that and do Santa Nella ("Gustine" in Tesla's naming), Kettleman City, then one of (Bakersfield, Buttonwillow, Tejon Ranch).

Bruce.

EDIT: My car and I were in my garage in Lafayette.

 

[Ampster]

I have been getting that message lately as well. Haven't put much effort into figuring out why. It does seem to be a long distance issue. I just set a destination near where I want to go then later enter the correct one and it goes through.

 

[xanatos]

I have been getting that message lately as well. Haven't put much effort into figuring out why. It does seem to be a long distance issue. I just set a destination near where I want to go then later enter the correct one and it goes through.

good to know I'm not the only one having this issue!

 

[xanatos]

TL;DR: It worked for me.

Personally, the early experience that a number of people reported with the trip planner around multi-charging-stop trips led me to turn off the trip planner and only rely on the navigation system to get to the next Supercharger. I do the higher-level planning using something like EV Trip Optimizer or A Better Route Planner, and then just navigate to the "next" charging stop, so I can put up the energy graph to see my project energy usage. Actually between SF and LA, you almost don't need to do any planning at all, with two independent routes (I-5 and US-101), and enough density that you can skip chargers on either route if you want.

Anyway to directly answer your question, I just tried it now with your destination in Arcadia, and it routed me to Harris Ranch (6% reserve) and then Bakersfield. S85D with 2018.21.9, new nav, non-vector CID maps, 89% charge (probably equivalent to 235-240 RM). Personally, I like shorter driving legs, so I'd probably override that and do Santa Nella ("Gustine" in Tesla's naming), Kettleman City, then one of (Bakersfield, Buttonwillow, Tejon Ranch).

Bruce.

EDIT: My car and I were in my garage in Lafayette.

thanks, that was very helpful, at least now I know what the nav suggests!

 

[Lmredcar]

I never had a problem until this year same thing sf area to so cal
Very annoying I am baffled fortunately I know all the super chargers along the way but I really liked knowing how long to be at one to optimize my trip
It also seems to have gotten worse from the. Last time I went in Jan

 

[sakimano]

Necro bump

Same problem here

Tesla couldn't fix it this week. They'll send a mobile specialist Will update

 

[jkdman123]

Had this same issue trying to navigate to a restaurant by name search less than 3 miles away with 80% charge. ‘No route to this location’.

However, if I typed in the address it could show the route. Maps glitch I think.

 

[smartypnz]

I think the car is intervening.... it just doesn't want to go to certain places.