Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. Power is the kW output of the battery. It's optional, but highly desired. Carmodel can be acquired from the "get_carmodels_list" method of the API, but for the ipace it's: "jaguar:ipace:19:90:other" "manufacturer:model:year:capacity:other parameters" Saw your email, and generated one for you, let me know if you run into any issues with that.
  3. Jason, What should I set the ‘carmodel’ value to for the i-Pace in the telemetry API? Also, what is the ‘power’ variable in the request? I need an API key to test with. I emailed you yesterday requesting it. Thanks, Dunravin
  4. Yesterday
  5. Sounds similar to my issue:
  6. Last week
  7. gday

    OBD Live Data Setup

    2020 Kia Soul EV - is there a preferred OBD device? Anyone tried it?
  8. Hello ABRP within Model 3 browser does still not aquire GPS info direct from the car, does it? It still locates me in the netherlands, asking to replan, each time I open the browser. Obviously it acquires GPS info from the Tesla account. Today this account was not updated with information for 30min+, so ABRP has no chance to locate me and replan accordingly. Should the GPS, acquired from the car, work? Thanks
  9. Hi, quit question: Is there a way to include other chargers than Superchargers when (Chademo or CCS) when the car is a tesla? Greetings -Batman-
  10. Now that Tesla Model 3 can charge at 200kW it would be great if I could instruct ABRP to prefer chargers that can deliver >200kW.
  11. JT1

    Waypoints Not Working

    Description: Planning a route without waypoints seem to work except I want to adjust my charging time at each specific Supercharger and the only way to do that seems to be to add them as Waypoints, but when adding Waypoints, the plan seems to add totally unnecessary charging stops to the plan. I've tried telling it to not use that charger, but it just adds another charger even further out of the way. Is there a way to adjust charging time at each stop without adding waypoints or is there a way to manipulate waypoints better like on evtripplanner? You don't go from Cincinnati to Columbus through Dayton. See image. Link to Plan: https://abetterrouteplanner.com/?plan_uuid=703e3b39-91cf-48f8-87e5-4daab71051a6
  12. PS I just tried Share from ABRP sending my route to Google maps. The modifications were very easy to make so an import button would reverse the process? I realize that this "sounds simple" and there are complications that only the programmers know!
  13. Description: This is a sort of follow up to the idea of making routes in ABRP editable like Google but may be an easier way to achieve that end. Google maps is a very versatile model for creating a route, e.g. it allows you to change a route if you have preferences about missing an area and the ability to use satellite or streetview for checking details if necessary. Use Case: I would plan a route on Google, import into ABRP and get the data I need. I guess I could then export it back to Google maps and run in Android Auto.
  14. Herman

    MyAudi Connection

    Hi Jason, No idea what it would take, effortwise, but did you make any progress? Regards, Herman
  15. [This is a cross-posting from my post on the Tesla Motors Club Model S Forum at https://teslamotorsclub.com/tmc/threads/variation-in-predicted-kwh-among-online-route-planners.156386/ ] Background: on Aug. 10, 2019, I'd like to make a trip from Cal Northern School of Law, Chico, CA, U.S.A., to the Tesla Supercharger at Donner Pass, CA, without charging en route. Question: can I make it with a reasonable margin for safety? I'm the original owner of the car, so I have some experience with road trips. This is a 132.3 mi. trip with a net elevation change of 5,710 feet. I used these online trip planners, listed in descending order of their age: evtripplanner.com ("EVTP") evtripping.com ("EVTG") abetterrouteplanner.com ("ABRP") Results in kWh used: EVTP: 49.4 EVTG: 52.9 ABRP: 60.7 I tried to make the inputs as equal as possible among the three. Since EVTG uses seasonal weather data and reported a predicted en route temperature of 72.5F, I specified 73F in the other two. I specified a speed multiple of 1.14 or 114% , with the resulting average speeds (and driving times) of: EVTP: 61.5 mph (2:09) EVTG: 64.6 mph (2:03) ABRP: 60.1 mph (2:12) I figure I can begin the trip with a charge of 90-95%, or about 66-69 kWh. If ABRP's 61 kWh usage result is accurate I'm too chicken to make this trip without an off-route charge en route at Yuba City that would add about 45 min. total to the duration. But if usage of 53 kWh or better is accurate, I'd not charge en route. I'm curious about the difference is results, and in particular the outlying difference of ABRP from the other two.
  16. Rav

    IOS & Android App ?

    @Jason (ABRP) An Indigogo funding campaign would probably be successful to help you hire app developers. The nice thing about indigogo is the extended goals so you can tier the fundraising goals.
  17. The quickest plan for that journey (2h30m) is to limit the max speed to 130km/h so that you don’t need to stop to charge. That’s an average speed of 97km/h (based on a 241km route). That compares with your suggested 110km/h average in a polluting diesel car, which would save you 17m30s (12% quicker), but cost substantially more in fuel and pollute the areas through which you drive. Budget permitting, you don’t need to wait for a bigger battery - just a get a Model 3 LR instead of a SR+.
  18. If it was point A to B and then point B to point A via the same route then my understanding is the wind (and elevation profile) would *mostly* cancel each other out; however, my understanding is the benefit gained from a tailwind (and/or a down hill) is not necessarily equal to the losses incurred due to a headwind (and/or an up hill). Also, when I started this thread, I had in mind a route that went from point A and back to point A, bit via points B, C, D etc... i.e a ‘circular’ round-trip, rather than a bi-directional, linear ‘round-trip’. In the case of a circular round-trip, the winds may be completely different for different sections of the route, and even if they weren’t and the route was a perfect circle, I’m not sure the impact of the wind would be negated.
  19. This You Tuber has some videos on Leaf 40 battery temps etc which my be of some help:
  20. Slightly off-topic, but I wonder whether at some point you may be able to give users the option of choosing what they wish to optimize in favour of. For example, some users may wish to optimize in favour of efficiency, or minimal total energy consumed, rather than time - both for the environmental benefits but also the financial benefits.
  21. Hello Great website! I need to register and also want to make a small donation! But I miss a importent option to choose, wheel/tire size. As i know it´s make a big difference if you use the 21" Turbine Wheels or the 19" Slipstream! Look at this (in german) I hope for such a implementation i the future.
  22. I've had the same thing on avoiding highways. Something we should probably try internally when the routes fail on the first try. It's all fairly complicated, but it boils down to the fact that we time-optimize the route planning, so it'll almost always choose driving faster and charging more frequently when possible. It does lead to a few odd behaviors like what you're saying, where it initially picks the "faster" route that uses a highway, then later on in checking that route fails, but the non-highway route is rejected because it's too much slower than the highway route. Thankfully such cases are fairly rare (in my experience), and we're aware of them and constantly improving the algorithm, so they should (hopefully) happen less as time goes on. On the first note, though, I checked over the planned speeds on your route, and they're all under 55mph, which is much slower than you would expect to drive out west of Austin. (From experience). I've been meaning to create a thread to solicit feedback on the US speeds, and this is the kick I need to go do it! Link to that Thread
  23. One of the most important things for accurate planning is getting the speeds right. As anyone who's driven an EV knows, an extra 5-10mph can mean the difference between making it to your destination, and stopping for an unplanned break at an extra charger. I've noticed that our planned speeds are often incorrect, especially in rural areas. With that in mind, I'd like some help from the community. At the moment, these are the speeds we assume in the US when we have no known speed limit: motorway = 65 mph, # A restricted access major divided highway, normally with 2 or more running lanes plus emergency hard shoulder. Equivalent to the Freeway, Autobahn, etc.. trunk = 55 mph, # The most important roads in a country's system that aren't motorways. (Need not necessarily be a divided highway.) primary = 45 mph, # The next most important roads in a country's system. (Often link larger towns.) secondary = 35 mph, # The next most important roads in a country's system. (Often link towns.) tertiary = 25 mph, # The next most important roads in a country's system. (Often link smaller towns and villages) unclassified = 18 mph, # The least important through roads in a country's system – i.e. minor roads of a lower classification than tertiary, but which serve a purpose other than access to properties. (Often link villages and hamlets. Holdover from UK system) residential = 18 mph, # Roads which serve as an access to housing, without function of connecting settlements. Often lined with housing. living_street = 6 mph # Residential streets where pedestrians have legal priority over cars, speeds are kept very low and where children are allowed to play on the street. Of course, when someone's taken the time to go into Open Street Map and set a speed limit, we use that instead of our defaults. (For reference, you can contribute those speed limits using the link at the bottom of the route-click popup. You can tell if we have a known speed limit for a route if the "Speed Limit" field shows up on the route preview popup in addition to "Planned Speed") I've prepared an update to our US speeds based on roads near me, but since speeds vary significantly throughout the US, I wanted to solicit feedback prior to rebuilding the routing engine around these speeds: motorway = 75 mph, trunk = 65 mph, primary = 65 mph, secondary = 55 mph, tertiary = 45 mph, unclassified = 35 mph, residential = 25 mph, living_street = 15 mph To compare to roads around you (and know how we classify them) create a route that drives a segment of road, then click on the route to get this popup: If you click on the "Speed Limit or Elevation incorrect? Edit Open Street Map." link, it'll take you to Open Street Map, and you can click on the road to see the type: Thanks in advance for the feedback!
  24. Yes, indeed, the various HKMC 38kWh cars use the same charge curve. I need to compare @Sameless's curve against the one I'm currently using, but it looks fairly similar to what I recall.
  25. Ah, I'll double check the link, but it's on the planner now. Under Settings > More Settings > Live Data > Setup (make sure you have the right car selected). The instructions should be pretty quick! We'll take all the data we can get! We're still working on getting enough data to start taking battery temperature into account (still don't understand why Nissan doesn't cool their batteries...), but that takes a lot more data to characterize because of the large number of factors that go into that.
  26. Interesting, when you added it as a waypoint it got set with a charge power of 3kW (instead of the 350kW it ought to have). I'll investigate that, but in the meantime you don't actually need to pick it as a waypoint if you don't want to, the planner finds it on its own: https://abetterrouteplanner.com/?plan_uuid=4c7734f6-0443-4498-a169-0cba5ca23be3
  27. That would be great! Spare moments are a thing I find myself ever lacking. There's two ways we could end up deploying an API tool in the end, should you write one up: Send us your code, and we run it on our server, and add a login field (like the MyTesla login) on the site to provide the API credentials Individuals run it on their own, and you send it directly to our Telemtry API If you want to use 2 for a bit to test it out and see how well it works, shoot me an email at jason@iternio.com and I'll set you up with an API key.
  1. Load more activity

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...