Jump to content

Jojo

Members
  • Content Count

    76
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Jojo

  1. If you need someone to test, I would be happy to help. Thanks
  2. Hello Bo Good to know. I would really like to see that. Is Model 3 browser version still planned? Thanks
  3. Hello Bo Can't tell. Most time I'm using the Model 3 browser. To be honest. I stopped using ABRP in Model 3, because it does not work reliable. - Login problems with Tesla login - nonsense automatic rerouting after a while, when only position is acquired from GSM - time schedule not usable - many other issues over the last month, see forum (bug in routing, but with waypoint order, bug with abrp login...) - losing my route and get an old one was the last straw that breaks the camel's back I think you have to decide how to proceed. A. Building up a service for free with limited resources => concentrate on reliability, no new features, keep it stable. Maybe no support for Model 3 browser, if it's too complicated to get this stable. B. Building up a service professionally with a monthly fee => leading service, reliable, feature rich. C. As you said in the interview with Björn. Sell the algorithm, close ABRP and leave the field to other people. Your choice. Right now, it is frustrating for us all. My choice would be B.
  4. Hello I can confirm this. I had the same issue in Model 3 browser on Sunday. I followed a plan and after reopening the browser ABRP presents an old planning from some time before. Maybe it picks up another planning done before on any other device with ABRP account logged in and does not take the latest one.
  5. Jojo

    ABRP Login is not saved

    Hello Bo I have still problems with live data acquiring via Tesla Login. I now have more details. 1. Starting a planning. Live data acquiring needs some time, but than position and SoC is given and the route is calculated. Tesla Login works. 2. Than I close the browser to navigate with Tesla Navi. 3a. If I open the browser with ABRP again after a short while (1min, 2min...) the burn down chart is updated right away and my position is also shown correctly right away. 3b. If I open the browser after 10min again, no burn down chart appears and after a while I'm located in the Netherlands. And I get the Replan Popup. !!! If I than not react to the popup and close the browser and than reopen it in the next moment, everything is fine again. Burn down chart, SoC, position ok. So between 2min and 10min ABRP "forgets" the access to the Account and is not capable to reestablish it after the next reopening of the browser in the first place. Only after the next opening again it works or after only 2min to ?min from the last opening. Hopefully it helps to find the problem. Thanks
  6. Hello Bo, Jason Something is happening, right? Since today the first starting point gets no time update anymore, when reopening the Model 3 browser. Good, well done. Nevertheless the ETA is still calculated based on the browser opening time. I started at 19:36 and the initial ETA was 19:55 (19:36+19min). Short before home I opened the browser (19:59) and the ETA was 20:18 (again +19min added to the opening time of the browser) That's not right. Thanks
  7. Description: The time schedule behind a planning is not getting updated correcty in Model 3 browser Replication Steps: Plan a route with first position "my position" Begin to drive according to route planning Everytime you reopen the Model 3 browser the burn down chart gets updatet with SoC Live data correctly (now ;-)). But also the time of the first beginning point where you started is set to the current time of reopening the browser. The rest of the time schedule is calculated with the segment duration based on the beginning time. With this beginning time always set to browser reopening time, the schedule is constantly shifted to later and does not fit in any kind to your trip progress. Estimated time of arrivals are all wrong at all following points. Hello Bo, Jason. I really want your tool working well. I love it and want to use it as reliable tool. This is the reason, why I push, like I do, Thanks See picture: Originally we started the plan at 7:45 in Frederikshavn, Denmark. Because of a problem with ABRP we have to recalculate the plan somewhere between Frederikshavn and Rodekro at 56% SoC. On this recalculation, the time schedule should be based on and the initial planning told us to be at Bispingen at 13:33. See the right line at the burndown chart, which is correctly not "updated" when reopening the browser from initial planning. Whereas the plan at the top gets everytime you open the Model 3 browser, an update of the time for the first position of the plan. Here you can see, that I opened the browser at 12:06. Based on that Bispingen ETA is calculated at 15:11. All Locations in a plan that you already passed should show either the original ETA or better, the real time of arrival. All followup locations should be recalculated when opening the browser. So we need a mixture of not recalculating the whole route everytime we open the browser , because this undermines the functionality of the burn down chart. But we need an update of the time schedule to the current progress and follow up ETAs. Thanks
  8. Jojo

    ABRP Login is not saved

    PPPS.: After resetting my login it works again. Lets see the next days, if it forgets the login again or we are facing new problems. Thanks
  9. Jojo

    ABRP Login is not saved

    PPS.: Or show the letters for a second and than mask it. We need the opportunity to check input
  10. Jojo

    ABRP Login is not saved

    Hello Bo Yes, Tesla API is nuts today. I tried to relogin 20 times today. Login wrong. Currently I cannot login via Model 3 browser at all. ABRP was not usable today in the car. Keyboard input is also strange. I have to open login popup twice, because after clicking in the next input field, the keyboard doesn't open. I have to close the popup and reopen it. I cannot check if I input my password right because I cannot see it plain text. Please add a show password button. I had problems in the past with Model 3 keyboard, that it writes capital letters despite small letters should appear and the other way around. All these problems I had with 24.4 software and before. Since yesterday I have 28.3. and the Tesla login doesn't work anymore. Status today with 28.3.: ABRP is unusable. Keep the head up, thanks. PS.: Tesla locked my account Because of to many failed Logins. Could there something be wrong with your forwarding of the login?
  11. Jojo

    ABRP Login is not saved

    Hello Bo I'm on the road again today. Time schedule is still not working, but currently not so important. Update of plan when browser reloads works in principle. Two problems today: 1. ABRP forgets Tesla login after a while. Then the update of burn down chart doesn't work because no live info. When I login again (just clicking FIN number) it works again. 2. Maybe because of problem number 1 or even if the login is not forgotten, the localisation begins again with Amsterdam (dutch provider issue). Thanks for fixing the issues. Bye
  12. Jojo

    ABRP Login is not saved

    Hello Bo Yes, it's working better now. Not recalculating the route when just reloading the browser makes more sense. The burn down chart is getting updated, the first point stays the starting point. Well done. Did you change something on the time schedule? It still updates the time of the first point (starting point) to the opening time of the browser. The time of the route points should stay as we reached them, all route point of the future should be recalculated time wise. So you get an updated plan each time you open the browser. Is it clear, what I mean? Thanks
  13. Jojo

    ABRP Login is not saved

    Good, good, I will try that. Thanks
  14. Jojo

    ABRP Login is not saved

    No, no. As I wrote above, I never used uuid bookmark. The valid current plan is loaded according to the settings within my account on your server. That worked fine. I give you feedback, when I tried your fix. Thank you
  15. 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
  16. Jojo

    ABRP Login is not saved

    Hello Bo, hello Jason Sorry to bother you again, but I'm really frustrated. Until around two weeks ago, ABRP planner works great in Model 3. Thanks for your effort and your commitment to this project. I know, it is not easy to do something like that besides a day job. Since two weeks ABRP doesn't work as it should, unfortunately exactly the two/three weeks, I'm on a roadtrip through norway, but this is my personal bad luck. There was the problem with too fast replanning after opening the Model 3 browser, before the live data was aquired. See posts before. Yesterday morning Bo fixed it and it works, but only yesterday. Today it doesn't work anymore. To be honest, I don't know if it's me or you changed the behavior by intention. Until two weeks ago all my plans always began with "my position". When I started they day trip in the morning, ABRP planner plans the route from the current position. After each browser reload, the start of the trip was still the initial starting point of the day with the initial "my position". The SoC burn down chart began with the initial SoC, the time schedule began with the starting time of the day trip. With the "recalculation", that is done when opening the browser, only the SoC was updated and the green line went along to the right side if the chart as the progress of the trip. I could see the same behavior yesterday after the fix of Bo, despite, that the beginning time in the time schedule for "my position" was always updated to the current time of reopening the browser. Today the behavior was different. With each reopening of the browser, the complete plan was recalculated and the current "my position" was set as the new starting point. Consequently the green line of the SoC chart was always on the left at the beginning. I could not compare the planning with the actual SoC, which makes the chart useless. I think we need three different trip/plan "refresh" strategies: 1. If the browser in Model 3 is reopened during a running plan. No new calculation, only update of SoC chart with live data. No update of initial "my position". No update of the current starting time. 2. Replan button appears: Without knowing the conditions for "Replan" exactly, I think it appears when I leave the path of the planning or the SoC deviates with a certain amount from planning. Recalculation of charging stops and time schedule. No new initial "my position". 3. Complete new calculation: Taking new current "my position" as starting point, new time schedule, new route. Strangely, I think, this it how it works until two weeks ago, but it does not right now. Thanks
  17. Jojo

    ABRP Login is not saved

    Hello Bo It nearly works, how it should. The SoC is now correct, burn down chart works and the route is not newly calculated from the latest "my position". Great job, thanks. But: the time schedule is wrong now. Each time I open the browser the plan begins with the current time, not with the time, when I started the plan. With the time it should be the same as with the position. First entry in the plan is the base with the location and time the plan was started at. Thanks
  18. Jojo

    ABRP Login is not saved

    Hello Bo Thanks, but I'm not sure. You will know it better. But the current SoC is shown in the chart in green right from the reload if the page. But it is not taken into account by ABRP in that first moment. Let's see, what your fix will bring. Thanks
  19. Jojo

    ABRP Login is not saved

    Sorry, I wrote something wrong here.
  20. Jojo

    ABRP Login is not saved

    See the behavior.
  21. Jojo

    ABRP Login is not saved

    Hello Thanks for your response. Now we can discuss. I use Abetter... and beta.abett... as bookmarks in Model 3. I already renewed these because of the issue, but it doesn't help. I never used an UUID link as bookmark. Currently (three weeks Norway roadtrip) I exclusively using saved plans. Everytime I reopen the Model 3 browser the right plan is loading correctly, no issue. But the burn down chart (right name? SoC chart) is always starting at 90%. It also shows the current SoC correctly and also at the right location/position within plan. But you than see planned SoC 88% and current SoC 63%. It only gets in line again after hitting replan (if it is presented) our hitting plan again. But than the plan starts with current position and the burn down chart is pointless. Video follows. Thanks
  22. Jojo

    ABRP Login is not saved

    Hello About which problem do we talk? Mine is not solved. After each browser start in Model 3 the plan starts newly with 90% and not with the current state of charge. After replan or doing plan route it works, but this starts the planning with current position and current state of charge and so the burn down chart always begins new, which makes it pointless. Will upload a video of that issue. Thanks Bye
  23. Jojo

    ABRP Login is not saved

    Hello Jason You did two updates of ABRP meanwhile. But ABRP is still not working in Model 3. Is it only me or does nobody else using ABRP in Model 3? To rephrase it: If I follow a plan on tour, each time I open the browser the plan calculates newly with a SOC of 90%. The browser does not start in the status of acquiring current live state of charge and showing it in the burn down chart. I have either to tap replan or even have to plan it new. It worked in the past. What's the problem? Is is the last Model 3 update? Thanks
  24. Jojo

    ABRP Login is not saved

    Hello Yes,I think, I know, what you mean. If I reload ABRP the first time, ABRP login is green right away. If I reload the browser during a running trip and want to look how my SOC compared to the planning, the login is gray. So the bug has something to do with a running trip. Thanks
  25. Jojo

    ABRP Login is not saved

    Any news on this issue? The login is also not "stored" within Chrome Android browser. Whereas in Model 3 browser the input fields for the credentials are always empty after reload, in Chrome Android the credentials are stored within the browser, but you are not automatically logged in anymore. Something changed. Thanks

Contact Us

Bo - Lead Developer and Tesla owner: bo@abetterrouteplanner.com

Jason - New Car Models, Developer and Bolt owner : jason@abetterrouteplanner.com

Idreams - Forums Administrator, Forums Developer and Tesla owner : idreams@abetterrouteplanner.com

×
×
  • Create New...