I have covered it
here.
Direct link can be found
here.
I'd say that's flatlander stuff, but it's not even that: it doesn't take into account their wicked weather (wind and various diverse precipitation styles). 3rd party resources on this have been far superior and mostly sufficient for years, almost ever since Model S came out. I've bought and donated to many of those; I suggest others seek them out. The first and best one is still the best one (EVTripPlanner.Com). The current in car Model S and Model X nav is second best, plus it's in the car, so you can skip evtripplanner.com planning mostly.
Up until 7 months ago when I sold my Model S, I had attempted to use ABetterRoutePlanner and EVTO, and both seemed like they were a mixed bag on good days, but were both buggier than the stalwarts (evtripplanner and Tesla's own current in-car nav systems for S & X), but since I gave up on them fairly quickly, they could have debugged them fairly well by now (if they do work well now, just keep backup options for those remaining or future quirks (i.e., learn evtripplanner)). EVTO seemed to try to do the most, and a few times, it was actually really a treat to use, figuring out some things that none of the others could (unfortunately, it often was so buggy that I could reach the next SuperCharger before EVTO worked). ABetterRoutePlanner
always crashed my browser and didn't work. EVTO would make a whole colony of spiders fat. I want to try them again and report back.
Abetterrouteplanner still has a very difficult to use web-based scripting user interface that I find quite awful: unobvious translucent windows with their controls default off of the page cover other windows. It's really beautiful and tries to do a lot of really neat UI things, but as is usual with beautiful neat web UI's, it just doesn't work (failure of the web browsers delivering an easy to make work correctly working scripting language, I suppose). The batch-form oriented evtripplanner, despite being very old IBM-mainframe style (form and batch), still seems to be superior than this. However, once I have fought the abetterrouteplanner web script style of windows (figuring out what is a window, finding its controls, etc.), it relents to sufficient options, and I can get it running. I am excited to put in one of my usual trips with all sorts of options, and hit the go button ("Plan route"), but then it just hangs, with a little bouncy indicator. I really wish it wouldn't hang. If it is an issue of processing power, I wouldn't mind paying through a Lightning Network Bitcoin channel or VISA card for my share of use of cloud GPU farms (such as AWS's NVIDIA GPU farms) to actually make it work. It looks promising as ever, but still never works. I'm sorry.
A quick search for EVTO on my iPhone found it with 3 out of 5 stars. I hit download, and tried it again. Because I was a development tester, I deleted it and reinstalled it, to try to get the latest release version. I have to say, it is more intuitive than before, a lot less buggy, and quite a bit faster. (The less buggy helps with all of that.) It still has some knowledge problems: users don't know how to "add segment" in the first window they see that they learn "segments" exist, and are left to wonder if "add waypoint" is related, until one realizes "add segment" is grayed out and requires $10/year. I almost gave up when it dumped me into Apple's store interface for that purchase, requiring me to use my laptop in conjunction with my iPhone to make the purchase and type a horrendously long password using Apple's awful security system. I was rewarded for my torture by an iTunes store error ("can't connect", an error that is
literally impossible in this day of age, and yet, programmers seem to think it's not totally insane to spit it out at users), and had to use waypoints as a workaround. Its suggested addresses aren't ordered in most likely format, but pull in places from Texas before California (which is odd since I've never been to Texas and live in California). I got the waypoint in as the destination, hit refresh, and then it comes up with a reasonable route. Pressing the "Consumption" tab shows that it did pretty well at the calculation. Looking for options such as weather, traffic and speed aren't as easy and explicit as evtripplanner (which explicitly gives you options for which you have to guess and lacks traffic), but EVTO does attempt to take into consideration predicted weather along the route. I believe but forget whether or not it also takes into consideration elevation, which we know evtripplanner does. I recommend those who drive Teslas far to a new destination on at least a weekly basis check it out. It has a big learning curve.