Search results

OK, today I re-enabled supercharge.info as main information source for superchargers. Let us see if that information is more correct than Tesla's (obviously not so correct information).

A month or two back, we switched from supercharge.info to tesla.com for supercharger info since supercharge.info was missing a few new pieces of information (probably due to the Google maps pricing issues). However, it has always been the case that supercharge.info contains community-corrected...

ABRP Forums! We realize that reading a 39 page thread here at TMC or other forums about ABRP is a daunting and not very rewarding task, so we have finally set up forums of our own to discuss ABRP specifics. Feel free to join us at A Better Route Planner ! Also the blogs have moved there meaning...

The difference between arriving at 10% and 15% at a charger with a modern Tesla battery is pretty small in terms of charging time (in an early S85, for example, it was always clearly better to arrive at as low SoC as possible). For some routes, ABRP may propose to arrive 15% instead of 10% even...

Thanks, that was a bug - now fixed!

Try a hard reload of the page, we have moved some files around. Shift+reload button.

ABRP 3.3 has been released. Highlights: Driving mode, with or without telemetry. As soon as you move fast enough, ABRP will switch to driving mode and display a graph of the next route leg including elevation and expected battery State-of-Charge % (SoC) together with estimated arrival time...

I have no first hand experience with the Tesla Model 3 browser, but I am hoping it shares all the bugs^H^H^H^H features with the Model S/X browser. When you go to ABRP in the browser, does it display the EULA/GDPR dialog at the bottom? Did you accept it? I really appreciate your will to...

Yup, I emailed him with my experience the same day he closed. Guess the poor guy is not too happy with the unwanted extra work.

I hear you! The tech is now in place for it, I just need to add a little enabling. Coming soon.

I run the A Better Routeplanner service where we let users login via MyTesla and optionally share data with us. For fun and statistics, I just checked the option codes for all 258 Model 3s in our database. They are all the same. Seems like Tesla took some shortcuts on this one in production...

Nice car! Does not really matter what you select for logging purposes - we read out your option codes so we should be able read it out from there. And yes, we would be very happy to get more data from the P3! Edit: Just added the M3 Performance as an alpha model in ABRP too.

Nah, navigation in ABRP is mostly an attempt to do something about the hopelessly outdated maps in the previous Tesla nav. The ABRP maps are updated from OpenStreetMaps about weekly. However, the Tesla browser is too slow to make realtime nav possible.

Nope, not yet. But ABRP supports also non-Teslas and non-Superchargers nowadays and some other charger databases support realtime reporting.

We could easily update supercharger status much more often than today, but question is if the Tesla charger API really reports realtime status. Anyhow, I think we will add a way to check realtime status of chargers (when info is available) shortly.

No general outage anyway, our hourly site checking has not reported any issues and it works for me (now). Do you still have problems loading the page properly?

Yes! I just found it here on TMC too: "User-Agent" had to be set in the headers. Now ABRP with MyTesla is up and working again!

Nope, I am not sure, but I get a "503 Service Temporarily down" from the Tesla servers. Do you have any further pointers to information?

Not much we can do at the moment, the inofficial Tesla API we use has been down for 36 hours now. Hope they solve it soon.

We realize this is a problem, especially for Model 3 owners who cannot enjoy ABRP on their fast MCU. So, we just released a feature called "24h background sharing" which (optionally) lets ABRP servers poll your vehicle for up to 24 hours after you use ABRP. This makes data sharing from Model 3...

You can just go back to the ABRP "tab". It will sync up with the car again, and you can check the status of the plan and replan if needed. However, if you want to help out and provide driving/consumption data to ABRP, you have to keep the ABRP page on top and have the screen active. We only...

And now; more of the same! "CCS", "Chademo", "Destination" and "Charger" are now also magic search terms for getting charger proposals.

OK! "SC" added to the list of words which searches for Tesla Superchargers.

Ok, first stab at adding superchargers to autocomplete results. Try out by typing any address/name containing "suc", "super" or "tesla". For example, "suc kettle".

That is a good point. We know very well the name of every charger and should be able to extend the autocomplete search data with specific charger matches. Will look into it!

Another piece written on data from ABRP, this first time on Model 3: Model 3 Consumption and Charging – About A Better Routeplanner

Good luck on the trip! Unfortunately there is no way to rotate the map; Google does not support it and the Tesla browser is not fast enough for any tricks. That said, it is likely that we have to switch out Google maps for something else altogether in the near future, so perhaps the next maps...

Try reselecting your car model, this should reset both problems!

Good to hear that you find it useful! I have noticed the Tesla browser MCU crashing issues on my own car too - it seems like if you make the browser work too hard for too long, the MCU crashes (may be a watchdog or a memory issue, of course). ABRP is trying to give the browser some room to...

ABRP 3.1 released - a lot better adapted for the mobile browser ABRP on a mobile phone browser has been a so-so experience. From today, we have made the UI a lot better suited for small screens (as well as big including the Tesla browser) so you should find it more useful in your phone. Let us...

Just reselect the car model in the drop-down menu. This will reset the reference consumption.

As Google announced their hefty price changes, we previously moved to an OpenStreetMap-based solution for address autocomplete (you type a few letters for a destination and get a list of proposals). However, as many of you have noticed, the address database was not nearly as complete as Google's...

A Better Routeplanner 3.0 So, after ironing out a couple of release bugs, we are proud to present ABRP 3.0. Full release notes are on the ABRP blog. Main new features is support for multiple EV brands, starting of with the first serious Tesla contender: Chevy Bolt/Ampera-e. We expect to add...

Right, see it is a sneak preview! We discovered some performance issues after releasing it last night, and we are still working on those. Will announce it more in a day or two.

The new address autocomplete - non-Google due to new pricing - is not as complete as Google's. However, if you type in an adress which is not autocompleted, it will still translated correctly to a position using Google once you press Plan.

There are new versions, and a lot more info over at the ABRP Blog: About A Better Routeplanner – Updates, news and statistics from ABRP

Nope, this is only based on the measurements made by some institute claiming that the 19" wheels consume 15% more - but I have no data yet. If anyone has more measurements I'd be happy to know. I think that the 19" wheels would mostly consume more at higher speeds where the worse aerodynamics...

ABRP route planning is based on speed limits and your input - not traffic. So basically you get a "best case" estimate when it comes to driving times. However, this also means that for battery, it is usually conservative - more traffic means lower consumption.

Gee, thanks for the report! For some reason, this Supercharger and three others were marked as not being a charger in the database. I took some measures to try to ensure it does not happen again, but let me know if you find something strange.

I am trying to keep the number of options somewhat limited (both to reduce risk of bugs and to make UI understandable), so probably not. In practice, you'll have to tune the number based on your car and driving anyway and the default values are pretty OK.

Thanks, good input, will fix.

Yes, I worked around the car marker issue to a good enough level. When the new Tesla browser came in 2018.12(?) one of the bugs I reported to Tesla was that it crashed the MCU if the web page scripts were too heavy. ABRP would then crash the MCU all the time. As a workaround, I now have a limit...

The estimated reference consumption is done by observing how fast your SoC% decreases compared to the plan, so it is a pretty blunt tool. Basically, you'll have to wait until you have consumed 20-30% of the battery before the numbers stabilize.

Yes, I will consider that. Another way is to calculate it automatically for users who are logged in with MyTesla.

The reason why I have not implemented this is that different Teslas use different conversion figures between remaining kWh and miles. It varies betwen P and non-P models, different (offical) wheel sizes, and even North American and European versions. I even think it varies between different...

Don't worry, ABRP will remain. The most costly API calls were moved to OpenStreetMap-based services a year ago. Now I may have to move some more.

This is an issue introduced by the latest Tesla browser; the good thing is that the position is updated every second, but the bad consequence is that the map re-center updates takes so much time that the car icon is sometimes not visible. I am trying to work around the issue.

The guys behind NowYouKnow, Zac and Jessie did a nice interview with me about ABRP a couple of weeks back when they visited Scandinavia. Check it out you want!

Partially. ABRP has used OpenStreetMap and OSRM since 2.0 for routing since Google was way too expensive. Now more APIs will likely be too expensive, and I will have to switch. Likely that the visual maps stay Google, though, the traffic layer is quite important. (Autocomplete in the address...

I tried to fix this at some point but I think longpress is not well supported by browsers. I'll have a look again.