Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 06/26/2021 in all areas

  1. Loving the improvements, starting to feel much more polished. One thing I think would be good was if there was a permanent display of distance to the next instruction (or even the full instruction, so I know what road/junction it's going to be onto). It's something I miss from Google Maps, when I've got 100 miles to go down a motorway I always like to see what progress I'm making.
    3 points
  2. I've been navigating a route with guidepoints in it, and I don't think they're being handled right. The distance/time remaining and predicted arrival SOC are being shown to the next guidepoint, not to the next waypoint/destination. Also, I had a guidepoint placed just before a motorway exit that I had to take, and the instruction to take the exit did not show until I had passed the guidepoint.
    2 points
  3. New beta available, please try if it fixes your logout problems.
    2 points
  4. Hi, we as a family did a lovely roundtrip through Italy. All chargers worked fine (mainly 50kW Charges). IMG_2479.HEIC
    2 points
  5. Hello, When you're in Google maps application, we can click on "share location" and send it to the Tesla app. It would be very nice if we would send the location to ABRP app so we can create a new route to this location.
    1 point
  6. How about making it possible to display the route to follow with directions on the display in front of the driver as it is integrated with Google Maps ?
    1 point
  7. Hi @dspanogle, In my response to OP I stated that the globally set value should be overridden but that it is not in cases with lower values. This is a bug which we're investigating. No - there are not any hidden global settings you cannot change, all settings including global minimums are available in: Settings (detailed). Settings are saved when the plan is created, ie you click 'plan' (big blue button). Yes, you can have settings transfer across different devices, we'll always load your most recent plan (from anywhere) when logging in or starting the app. Manual is coming. /Katya
    1 point
  8. @cent The values on this screenhot seem all to be correct 😀
    1 point
  9. Great, i agree that we could improve on editing the addresses for favorites. Will add an internal note for that.
    1 point
  10. I just managed to edit it. Thanks for all your help! Job done. I can now go home from anywhere!
    1 point
  11. Whoa! I hadn't even considered using an OBD2 link (too used to not needing it in the Tesla). I called up my sister and got my OBD2 dongle out of the LEAF that I sold her (she didn't even know it was there, even though I told her what it was for at the time!), plugged it into the ID.4, and after some relatively simple setup and linking EVNotify and ABRP, it seems to work GREAT! Even though we haven't actually headed out on our trip yet (we leave in a few hours), the live data in ABRP is working great (we were charging the car at the time, and this is clearly shown in ABRP). Mind is blown. Very nice job on this integration. Looking forward to seeing how this all works on the trip, but no doubt this is a game changer compared to the previous trip we took. This trip will be quite an adventure...over 1800 miles and going through a few areas that frankly are quite underserved in terms of charging stations.
    1 point
  12. Hi, you need to enable beta access in play store, scroll a bit below the comments, activate beta, wait some time and check back to update to beta version. Might take an hour or so until beta is active. Samuel
    1 point
  13. Hi Katya, you are absolutely right! My mistake! Thanks! By the way, any news on my Premium subscription?
    1 point
  14. Driving Model: https://www.dropbox.com/s/u1mybenqwoajun8/Rav4rangeChartV100.2.pdf Charging Model: https://qccharge.com/products/jdemo-for-2012-2014-toyota-rav4-ev 1) How many miles / kms of range autonomy will JdeMO add? Answer: JdeMO adds about 2 miles (3 km) per minute while charging between 20% and 80% battery State Of Charge (SOC%). A normal 30 to 45 minute charge session will add 60 miles (96 km) up to 90 miles (144 km) of range, in about the time that you will have lunch, dinner, coffee, etc. 2) How fast will the Rav4 EV be able to charge? Answer: It will charge at up to 386 volts DC at a maximum of 125 amps, or about 45kW. That means that it can charge from 20% to 80% of the battery usable capacity in approximately 30-45 minutes. Most CHAdeMO compliant chargers are 100 to 125 amps "50kW".
    1 point
  15. Hi, "Not drivable" means that there is an alternative route that you can not take. It seems that the marker is at a wrong position or maybe too big and covers the exit to the crossing road at that position? If the road itself is not red it means you can still drive it. "Not Drivable" mostly comes from closed roads nearby. That is a pretty new feature, we are still working on adjusting the overlays. Samuel
    1 point
  16. That is GPS jitter. We already improved logic on that but it seems that some devices jitter more than others. We will look into it again.
    1 point
  17. Hi again Katya, Yes, you succeeded in getting Google to refund me the Premium price. If ABRP on AA works better than the built in satnav I'll gladly pay it. All working now with Tronity link to live data. I resubscribed to Premium to get weather and traffic. Please consider the topic closed Cheers and thanks Colin Begg
    1 point
  18. Can we add more favourites to ABRP. At the moment it's just home/work but would be good to be able to add a list of destinations so routes can be planned from favourites in AA.
    1 point
  19. Hi @cent, Thank you for your feedback! We'd love to be able to show the plan summary and provide options to change charing stops and display the next stop/charger in CarPlay. However, we are currently somewhat limited by the CarPlay template and the size of the screen. We will keep your suggestions in mind when planning coming updates to CarPlay. /Sofia
    1 point
  20. Hi @cent, Thank you for your feedback! It does indeed look very confusing. I will make sure to forward your suggestion. /Sofia
    1 point
  21. @Jason-ABRP I suggest that the Reference Consumption be changed to 205 WH/km @ 110km/H. I guess you should be starting to build up real data now from the 3 or 4 of us who are contributing via Torque but it's worth noting that the default value of 178 is almost exactly what I get around town. I don't even get close to that at 110kmph on the freeway!
    1 point
  22. Hi @cent, Thank you for reporting this bug to us. We'll make sure to take a look at what's causing the CarPlay app to show more than 100% SoC. Did you see 106% in the mobile ABRP app as well or only in CarPlay? /Sofia
    1 point
  23. Where the data comes from is dependent on the car. Some cars are supported via Tronity for example. Others only via OBD dongle. You can always also inject your own live data if you get it from another API for example.
    1 point
  24. I don't use premium. My route is both shortest and fastest route. Also, the third+fourth plans chose my route, even while the only difference was that Allego chargers are preferred (the first plan also uses an Allego charger, so I did not add any reason not to pick it). The point is that I cannot trust ABRP to come up with the best route for me. Why then should I use ABRP? I can use any route planner to manually plan a route to chargers. I provided the route links. I expected that a developer would give me a good reason why it chose the out-of-the-way charger. Not speculation on why the route it chose might be the best route anyway. That's basically saying "the program chose it, so it must be the best route" instead of verifying if the route is actually the best. It becomes even weirder (something I just tried). In Chrome, if I enter the first link in a tab, it comes up with the long route. I then, in a new tab, enter the second link. It comes up with the short route (it is 15 minutes shorter). If I switch to the first tab, the route is updated to the short route. This does not happen if I switch to a different tab. It does not happen if I wait a while. It only happens if I show the better route in a different tab.
    1 point
  25. Last night we got the update in the playstore. Now it's going perfectly. Many thanks for the help
    1 point
  26. Hi @rossjmccarthy, That would be nice yes, though I'm not quite sure we can fit a separate indicator in AA. We have looked into implementing the same subtle indication as in web/app, the dashed line around SoC but it wasn't as simple as we thought. We hope to come up with a solution eventually. /Katya
    1 point
  27. Hi, please can you look into showing the distance to next manoeuvre in yards or miles when above a certain distance. At the moment it only shows in feet, so for example you might get an instruction like: in 11735 feet take the first exit. This instruction would be much more useful if it said in 2.2 miles take the first exit.
    1 point
  28. Hi @InDie.3, Thank you. CarPlay and Android Auto works slightly different. Android Auto is a separate instance running while CarPlay is more of a direct mirroring of the iOS app. However, the data sent to CP needs to be correctly converted before displayed and this is where things seem to have gone wrong. Normally we shouldn't be displaying yards for longer distances. I can see this is a bug we've actually already noted and we'll be looking into it. /Katya
    1 point
  29. ABRP Beta on Android Auto does not require Premium right now. When you registered for Beta it should roughly take 30mins and then you should be able to update to beta. Please check in Playstore if it offers an update.
    1 point
  30. When you activate beta it still takes a while until it is active and then you need to update the app after a while. Did you do that already?
    1 point
  31. We'll look into it.
    1 point
  32. @Samuel-ABRP had a chance to test today and bug appears to be fixed. Thank you!
    1 point
  33. I am seeing the same unexpected behaviour of the bottom bar (Android 11).
    1 point
  34. Thank you Katya for your very detailed reply. The functionalities you describe would be amazing and I’m looking forward to seeing those into production. I have free charging at the moment from about 7 vendors, that’s why I had them set up as my exclusively preferred chargers. Many thanks
    1 point
  35. Ok. Thanks for your respons. Lets hope Volvo allow the app soon.
    1 point
  36. Hi @varadipeter, Thank you for reporting this! I can see values lower than the globally set min arrival SoC are not taken into account but values that are higher do properly override the globally set value. We'll be looking into it! /Katya
    1 point
  37. Since Update to Version 4.0.45 and clearing the cache (Apps --> ABRP --> storage & cache --> clear cache) ABRP runs without problems on my PS2 🙂
    1 point
  38. Since Update to Version 4.0.45 and clearing the cache (see first picture above --> storage & cache --> clear cache) ABRP runs without problems on my PS2 🙂
    1 point
  39. So I have linked my Tesla to the APP. Other than saving drives, what else does linking provide. And Many Thanks
    1 point
  40. delay and freezing; I used ABRP for my Italy 5500km trip with tronity.io: 1) (strong) delay in route: I am alredy on the motorway while ABRP is still "navigating" me through the city 2) phone freezes 3) iPhone becomes very hot Quick fix so far: I put the phone in the Aircondition outlet - it cooles down and navigation seems to be almost on time.
    1 point
  41. @Brian D, @alan stone, Ok thank you! It seems to be specific to the AA beta and we're currently investigating. /Katya
    1 point
  42. This is exactly why we are not so enthusiastic about API support for non-Teslas. For whatever reason, most car manufacturers have decided to leave any useful information out of their APIs. At best you get very slowly-updated position and SoC, and at worst you get completely stale data while driving, which is precisely when you need updated information. Using the on-screen adjustment buttons is the "right" way to do it, but it's cumbersome and takes your attention away from driving. I would actually recommend using an OBD dongle like the OBDLink LX and EVNotify or some other app. You'll get a much more Tesla-like experience without having to interact with the car screen. For what it's worth, I've used EVNotify with my ID.4, and it works well enough if you turn on the "run in the background" secret option (and disable the auto-termination of apps in the background). This should be improved in future versions of the app. Our eventual hope is that Android Auto opens up the same hooks to us that Android Automotive has (like you see in our Polestar 2 implementation), and the detailed driving data is immediately available when you plug your phone into the car / hook up to wireless. Apple and CarPlay unfortunately haven't given any indications that this will be available in the future, but we can hope there too!
    1 point
  43. @Bill N Precisely, for the new features to be available in the iOS app we need to push a new update. We're working on it, just making sure everything's stable before release. Reason web goes first is because if any mistakes would slip past we can fix those and push updates immediately, while with iOS and Android we'd have to have the update pass Apple's and Google's review processes again, which can take several days. /Katya
    1 point
  44. For a lot of people, the main purpose of using abrp is the annual vacation trip and maybe 3 or 4 other occasions, where they need navigation planning with charging and stuff. For those, a close to 50€ price per year or 5€ per month, might seem to be to much for the benefit gained or simply too much to spend. So I would like to suggest a third premium option: One time usage for 1,2,3 or 4 weeks, no reoccurring payment. Starting at 1€ for 1 week 2 for 2 4 for 3 and 8 for 4 for example. The service should be available for booking up to 3 times per year, so it won't challenge the monthly subscription by booking week after week. Numbers are of course just examples for description purposes. What do you think?
    1 point
  45. We at the ABRP team are happy to share with you some insight regarding what different wind conditions have on the power consumption of vehicles in different winds. Vehicles in general are highly affected by weather conditions, and for EVs this is actually clearly visible due to the high efficiency - anything which makes it easier or hard to push the vehicle forward will - noticeably - affect consumption. An ICE car with 25-30% efficiency will see the same weather effects, the bad efficiency of the engine will simply hide it. As some of you may know ABRP collects anonymous driving and charging data to improve the quality of our service (see our reader-friendly Integrity Policy), and as mentioned in a previous blog post Tesla Model 3 Performance vs RWD consumption - Real Driving Data from 233 Cars, we want to share with you when we find something worth sharing. By studying the collected data from our most common car model - the Tesla Model 3 - we have been able to assemble a graph that gives some insight into how the wind is affecting power consumption, the result of which can be seen below. The graph is entirely based on data reported from the live data connected vehicles of ABRP users - there is no modeling or other assumptions at all. The diagram shows the effect that wind has on the instantaneous power consumption of vehicles traveling at highway speeds, 100 to 120 kmh (62 to 75 mph). Each square illustrates three components: wind speed, wind direction, and the influence they have on the car's power consumption. Both wind speed and wind direction are relative to the car's heading, where each square can be imagined to be the origin of a wind blowing at a car located in the middle of the graph. What that means is the further away a point is from the center the stronger winds are acting on the vehicle, i.e., the point furthest to the right is a direct headwind and, the left-most point is a direct tailwind. The color of each square addresses the additional power consumed by the when that wind is acting on the car. A negative number means that the wind is helping and the opposite is true for positive numbers. This relates to the colors of the image, where the bluer a square is the more wind is helping, and the redder it is wind is a hindrance. See the example below explaining how to read the result. Based on this we can answer a few important questions When are tailwinds beneficial? What are the worst kinds of winds? The effect of crosswind Firstly, let’s start off by exploring what winds are helping the car. Notice that the area where the wind helps the car is relatively smaller than the rest of the circle. Remarkably, some tailwinds are even bad for the effectiveness, for a tailwind to be helpful it must almost always come straight behind. Secondly, to answer the question of what the worst kinds of winds are, we look at the places where the graph is as dark red as possible, that is on the right-hand side of the circle. It can be hard to figure out exactly where the worst wind is hail from. But winds that originate either directly in front of the car or in the closest proximity to it seem to be the most unfavorable origin. Lastly, what are the effects of crosswinds? Intuitively, it may seem like crosswinds would have no effect at all, but it has been known for a long time by aerodynamics engineers that crosswinds harm the efficiency of an object traveling through the air, and we can just confirm that. Some things we can note from the graph is: A nice tailwind of 10 m/s (36 km/h, 22 mph) decreases consumption of a typical Tesla Model 3 by 6% at highway speeds A headwind of 10 m/s increases the consumption a Model 3 by 19% Direct cross winds of 10 m/s can increase the consumption by 8% A model of this effect of winds model has already been implemented into our vehicle consumption model and the full weather prediction is available for ABRP Premium members, and any user can enter the wind assumptions manually. Wind really can affect the consumption of your vehicle quite a lot, and ABRP helps you plan for it with zero effort. Thanks to the vehicle data provided by ABRP users, we made your experience with the app even better!
    1 point
  46. Description: On a roadtrip you may want to stop at a waypoint (POI) and spend some time there even if the waypoint has no charging. To get more accurate time predictions (ETA), add the possibility to add a time spent (duration) at a waypoint. (I know you can set departure time from a waypoint, but I want duration since that will remain the same even if you fiddle with start time etc) Right now the only way to force a duration at a waypoint is to use the feature for charging time at a waypoint and set the duration you want and set the charge rate to 1 kW (the lowest) to not affect the SoC too much. And since ABPR takes live/estimated traffic and weather into account, the predictions will be better if the duration spent at a waypoint is significant e.g. an hour or more.
    1 point
  47. Hi @Jojo, If a charger is still occupied when you are close by the planner may suggest another charging stop. It can also suggest that you stop at the occupied charger if it predicts that it will still result in the shortest trip (the planner will make a prediction on how long you will have to wait). Yes, premium users will get access to charger availability in the planning, both in real-time and forecasts based on historical use. We are actually working on the feature that you are suggesting. You can look forward to using it in one of our coming updates. /Sofia
    1 point
  48. Description: Please provide separate options for "Avoid Ferries" and "Avoid Car Trains" Use Case: I use Eurotunnel regularly. I do not want to use ferries. While "Avoid Ferries and Car Trains" does still route via Eurotunnel, it is not intuitive - it would be cleaner to have them as separate options.
    1 point
  49. I think sometimes a problem occurs when a charger is included in the map several times because of multiple sources knowing of the charger. Example: https://abetterrouteplanner.com/?plan_uuid=e5e47c6a-6603-4847-bfd0-9693ed2f6f40 i have told the planner not to charge at "Angath" (goingelectric source). I might prefer to charge at "Trafostation Schnelllader". Still it chooses Angath, but the Uppladdning.nu source one. I might not realise there were two sources of which i only disallowed one ant think the planner is broken. Sometimes there are even three sources. Even for someone knowing this "problem" it then becomes combersome to actually exclude the charging spot from planning.
    1 point
×
×
  • Create New...