ABRP doesn't work at all in Model 3 browser

[Jojo]

Hello ABRP

I tested ABRP in the vehicle browser yesterday for the first time on a 200km trip.

First calculation at the beginning worked well. Tesla account access is green, live data showed up, ABRP login is also green.

At all following looks into the browser (it is minimized in between to see the car navigation), ABRP is not working well. If it "wakes" up after opening the browser again, it does not have the current SoC. It's sometimes 5-10% behind. Sometimes it changes SoC after opening but still to an older SoC. GPS position is also not updated after opening. At the end the page does not even react to input, which is maybe more a problem of the tesla browser. 

Also a reload of the complete page doesn't help.

So making long story short. Unusable.

Do I have to use my smartphone instead?

Thanks

 

PS.: Did you get data from me yesterday?

Edited April 2, 2019 by Jojo

[Lady Sprite Blue]

Bummer. 

[Jason-ABRP]

If you saw live data in the car on ABRP (or on your phone, or computer), then we got data from you!

At the moment, ABRP doesn't work very well when put into the background.  Something we'll have to work on, certainly! Especially with new features like Navigate on Autopilot where you definitely want to have ABRP working well with the Tesla Nav.

[BRuhling]

I cannot get the new chromium browser to respond to ABRP at all in my Model 3.

 

Also, for some reason when I enter my Tesla account info into ABRP on my computer or phone, it says I have a LR RWD car as opposed to the LR AWD car I actually own...

[smurs]

I'm trying to find a way to send the full route to my Tesla's navigation (model 3 long range all wheel drive), but it doesn't seem to support "waypoints".  When I generate the route on my iPhone (e.g., enter destination and a waypoint) then I click "Share" and "open in apple maps", it will send just the first segment of my trip to my apple maps (which then successfully sends to my Tesla Nav), but I lose connecting info.  When I click "open in google maps", it does open the entire route in google maps on my iPhone, but when I then try to share that to my Tesla Nav, it errors out.  

Edited April 20, 2019 by smurs

[smurs]

Also, when I calculate a route to avoid tolls, it honors that setting when planning the route, but when I send that route to google maps, it forgets that preference and re-routes.

[Jojo]

New Status with Model 3 Software 2019.12.1.2 (new chromium browser) from today (12.05.2019):

Route calculation from ABRP was spot on. Taking winds, temp and load into account it fits perfect, whereas Tesla Nav was 5% off. Great work at ABRP!

ABRP still reloads every time you open the in car browser, but the last state is restored every time. GPS from car works meanwhile. You have to accept GPS access every time you open the browser (no cookies?), but that's better than not to have current position. In addition to that. ABRP now dynamically runs in real time, if you keep the browser open. That's fine.

Sharing next stop with the Tesla Nav works also, somehow. It does not take the next supercharger exactly, but it zooms the map to the supercharger position where you can choose the supercharger manually as next destination. Is there no opportunity to transfer the destination supercharger precisely? The supercharger as destination is needed by the Tesla Nav because otherwise the pre-heating will not work.

Overall a big step forward with some minor shortfalls:

- Approval for GPS access every time the browser opens. (Maybe a problem of the Tesla browser)

- "Unprecise" handover of destination (I think it's more a problem of the Tesla API)

- Still "arrive at" in the waypoint options is not taken into account (At least that is a ABRP problem, right?)

- No temperature information from Tesla Account in °C unit. If you choose metric, the calculation says "Planner error". Live data also shows no temp in °C.

Thanks for your great work.

 

 

 

 

 

Edited May 12, 2019 by Jojo