Jump to content

Jason (ABRP)

Administrators
  • Content Count

    382
  • Joined

  • Last visited

  • Days Won

    26

Everything posted by Jason (ABRP)

  1. 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.
  2. 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
  3. 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!
  4. 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.
  5. 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.
  6. 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
  7. 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.
  8. Both of those issues are related to our routing engine (OSRM), and I'm working on resolving both soon, hopefully. If you click on the route, you can see the speed and consumption we've planned for at that point along the trip, and wherever the speed limits are wrong, fix it in OSM (we provide a link at the bottom of the plan preview popup which will take you to the OSM edit page for that road). Long-term, I'm also working on improving our initial speed estimates for roads, because they're very often wrong (especially in Texas!)
  9. Those are both likely due to closures marked on Open Street Map. We have yet to implement a way to display those on our map. If those roads aren't closed anymore, or the maintenance is complete, you can get an Open Street Map edit link by clicking on the route and selecting the link at the bottom of the popup. We should pick up the updates within a few days (Takes some time to approve the update and re-cook the routing engine)
  10. At the moment we have no data on how the 62kWh Leaf will perform, but we did boost the charge curve by a little (assuming it has a similar shape to the 40kWh leaf curve, just charges faster). It should have a similar SoC time profile, but since it's a bigger battery it means a higher power (kW) at each step.
  11. It seems we had an issue importing the TeslaCCS spreadsheet last night, but I've re-imported and the server is reprocessing the distances between all those chargers. Routes with TeslaCCS seem to be working again! Let us know if you run into more issues.
  12. Thanks for the report, we are investigating.
  13. Yes, we issue a new token every time you open that subpage, you don't need to re-enter it once you have a valid token.
  14. This is intentional, for a couple reasons. Once Tesla finishes retrofitting all sites with CCS (Combo is redundant, as CCS = Combined Charge System) we will drop the Tesla CCS secondary selector. Additionally, everywhere else in the world the Model 3 does use the Supercharger plug, so it would be a lot of work for a temporary configuration.
  15. Tesla only provides the external temp when the car is on and the climate controls are running, so if you're planning at home or away from your car you may not see it.
  16. It's certainly possible, but we'd need some more information first: Could you provide a few more efficiency data points? Perhaps at intervals of 20km/h? That would give a sense of the consumption curve. What kind of charging inlet does the Zero have? CCS / J1772 / Type 2? Does it draw the full 9.9kW all the way from empty to full? Or does it taper as it approaches full? Is the 14.4kWh the usable capacity? Or is some of it reserved to protect battery health?
  17. He said he was going to get to it in not too long, so I'm hopeful. It did sound like LeafSpy wasn't his main project anymore, so I'm glad he was willing to put the fix in.
  18. Hmm, my tests work fine now, perhaps an inadvertent rollback on my bugfix last night or something?
  19. Thanks for all the data @XavDoug! Based on your feedback, I changed the PID I'm pulling from the rapid_charge_port to the HV_Charging parameter, and changed the Max Deterioration parameter too, perhaps that'll provide a better status: https://raw.githubusercontent.com/Felger/OBD-PIDs-for-HKMC-EVs/master/Hyundai Kona EV %26 Kia Niro EV/extendedpids/ABRP_Kona%26Niro_PIDs.csv If you wouldn't mind re-downloading the ABRP PID list and updating those two parameters? Also, could you double check that when those get selected the PIDs are still ea9e51 and ec3d7f (Data Logging & Upload > Select What to Log), if not please tell me what the new ones are so I can add it to the server.
  20. Interesting, do you have a second phone running LeafSpy? I know LeafSpy will shut down server logging not too long after being put in the background (I have a request out to the developer to fix this behavior, keep your eyes out for an update).
  21. Thanks for the suggestions! NativeScript, as well as React Native were on our radar as possibilities, it also seems that both might offer the capability to run on the site as well, reducing the number of codebases by one more.
  22. Yep, caused by a fix to the fix I put in for your lack of SoH data, you know the old Programmer song (to the tune of 99 bottles of beer): 99 little bugs in the code, 99 little bugs Take one down, patch it around 103 little bugs in the code In any case, should be all better now!
  23. Indeed it was, you know the drill, fix a bug for another user, cause a bug for someone else. Or in this case, everyone else.
  24. @Bill N - yes, forgot to reply to that thread, but one of our items in the pipe is an Account Management page, which I think would be a good place for that kind of setting.
  25. Thanks! Very helpful to get the full error message, made it very easy to fix.

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