Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 03/02/2020 in all areas

  1. 2 points
    Now it's running 😎
  2. 2 points
    Definitely haven't given up, just not the top of the priority list yet. Need to get the app completely up to snuff with the website, then we can really start adding features like AA and CP.
  3. 1 point
    Hello, I'd like to explain here why I don't use the new website, so hopefully you can do something about it: - Reading the result is not as simple. A table format is a lot more readable and less space consuming to me than a thin column - Calculation is slower: calculation time direct comparison with the "classic" version shows that the new version is slower - When adding the options clicking the cog button, you never know what's been set already until you click - It does not work as good on smaller screens, like the one installed in the car (model 3), at least for me - I don't think you can do specific settings for you car per travel I think you switched to the new version as default too soon. Cheers, Alessandro
  4. 1 point
    Hey, I've tried to connect EVNotify to ABRP but the livedata doesn't show up. It seams that EVNotify is sending the data but ABRP can't recive it. Can anybody know this porblem or anysolution. I allready tryed dis- and reconected EVNotify and ABRP but it wasn't the solution.
  5. 1 point
    Barry hi, Just a thought could it be the presence of a "null" value before the ID 3 vehicle name be the reason why the ID3 does not work when used as the selected vehicle? Please see below circled in red. I have checked for a number of different cars and they work ok. But when i select ID3 it does not work. I have to select it as a "Quick Select" and not use it as a car owned by me.
  6. 1 point
    Same here the app should get data from OBD2 directly, so no other apps woulb be neeed.
  7. 1 point
    Ok, did a test charge this weekend in the cold - ambient a ball hair above freezing with high winds. Managed a consistent 45kW (from a 50 kW machine). Battery temp started at about 14 Deg C and peaked at 30 Deg C at the end. Took the vehicle from about 20% to 83 % SoC in a smidge less than 25 mins. Think I'll do another test at a higher powered unit next weekend (if I can find one that isn't Electrify Canada). Looks like my previous experience may have been down to the DCFC unit and not a cold battery.
  8. 1 point
    In my experience Evnotify on iOS does not keep working (uploading live data) once in the background. Therefor I switched to Android
  9. 1 point
    I think some German developers making an app with integrated ABRP. But it's not released yet. https://www.goingelectric.de/forum/viewtopic.php?f=69&t=54309&sid=2fc2cdb9b3f111f60fdfcefc427860d6
  10. 1 point
    Definitely something we're thinking about, main drawback is good live weather data costs money, so might end up being a premium feature.
  11. 1 point
    New feature - next charger alternatives We just released a new (beta) feature which allows you to see what your next charger alternatives are while driving. ABRP plans are most focused on getting you to your destination as fast as possible, but there are of course other factors which matter in the real world. Pressing "Next Charger Alts" on top of the plan list will give you a pop-up dialog with your top-5 charger alternatives from where you are right now, including how much longer it would take to go for that charger compared to the (time-wise) optimal one. Let us know what you think!
  12. 1 point
    Description: On the Android App you don't see a difference in the planned road and road that you already travelled Use Case: Mark already travelled road with a dotted line
  13. 1 point
    Chargeprice.net offers an APP and an API to retrieve charging costs. User sets up which MSP charging cards they have, and chargeprice.net tells them how much they will need to pay at a charge point if they want to charge from x% to y%. They can then pick the cheapest charge card for the charge. ABRP should use that information to determine how much each charging stop would cost (given the cards the user owns, it can find the cheapest option for each stop). Next, if there are different routes available, ARBP can optimise for cost, not only for travel time.
  14. 1 point
    We have long-term plans to support both! We want everyone to be able to drive with their EVs, regardless of phone choice. Back when we only had the website, I looked into (and successfully displayed the website using) that Android Auto hack. But it was incredibly glitchy, and Google closed the exploit in recent versions of Android Auto. That said, it's very hacky and not the kind of experience open to anyone we want to give. When we do bring ABRP to Android Auto / CarPlay we'll be playing in their rules, so we'll provide as many features as we can, while still being approved to run in the cars.
  15. 1 point
    Or just ignore carplay. Just Android Auto. I Switched away from Apple Years ago.
  16. 1 point
    The old system had links to GoingElectric and alikes. Please bring those back since I need to check which of my MSPs work with a charging point. Also I miss the option to prefer/block charging networks. I'd like to unprefer (not block!) Ionity for example.
  17. 1 point
    Now creating a plugin for OVMS to support ABRP. Documentation is available here: OVMS Documentation
  18. 1 point
    Is it possible to work ABRP with Open Vehicle Monitoring System like EVnotify. I use OVMS every day and it would be nice if i could use it with ABRP together. More info about OVMS can be found on https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3
  19. 1 point
    Sorry, wrong Information. 76 kW x 0.609 = 46,2 kW max charging rate for the small battery model !!!
  20. 1 point
    Definitely something we can think about, though not a capability yet. The question is how best to implement such a feature, perhaps once charging has stopped at a given waypoint push the next destination? I'd expect something like a checkbox "Auto-push to Tesla" or similar.
  21. 1 point
    I'd like ABRP to automatically push the next waypoint after I've reached the first one. Is this something ABRP can do or is working on? I usually have the ABRP webpage running on my phone (and sometimes the car's browser - albeit slow as dirt - not ABRP's fault) and would like the servers to auto push the next waypoint since it knows I have arrived at the location. This will allow the car to auto calculate how long I need to charge to reach the next w/p.
  22. 1 point
    Thanks to the 5 Bolt EV drivers contributing driving data to ABRP, we’ve finally got enough data points to define our first real world consumption curve for the Chevy Bolt EV! We can still use driving data to improve the model even further, so if you’d like to contribute your data, have a look at the instructions. Also, if you’ve got an electric car you’d like us to support, contact myself and Bo, and we’ll run you through what we need to add the car to the planner. Much of the data comes from day-to-day driving, with a few road trips sprinkled. Thanks to everyone who contributed their driving data! Bolt EV Power at Constant Speed The ABRP Model, as you know, is driven by calculating the power consumed for each leg of the trip by plugging in the speed, elevation, and other factors for each segment of the trip, determining how much power the car must output to drive that segment. It then adds up all the segments, and subtracts it from the battery to determine when a charging stop is needed. For this purpose, we need an accurate driving model on flat ground as a baseline, that turns speeds into power. Then we can add all the other driving factors on top of that: Bolt driving data fit to a third order polynomial The blue dots are consumption samples (30 seconds of driving), adjusted for elevation and speed changes, and the yellow dots are median points within a 1 m/s bin. This means that the red line consumption model is fitted to the median consumption which means that most weather issues, car defects, aggressive driving and so on is typically ignored. As can be seen, we mostly have data points from very low speed and from highway speeds, but that is where things are most interesting. For the Bolt EV, the bottom line is, it’s actually a quite efficient vehicle, though its somewhat unaerodynamic shape really hits it at high speeds. The model gives us a reference efficiency of: 6.06 km/kWh (165 Wh/km) at 110 km/h or 3.92 mi/kWh (255 Wh/mile) at 65 mph That’s pretty good for a boxy little hatchback! For comparison, that’s about halfway between the Model 3 (143 Wh/km) and the Model S (188 Wh/km). We’ve now updated the live model for the Chevy Bolt (and Ampera-E), so you should see the benefits of this higher efficiency in your route planning! Do note that we still set the default a little lower than that, just to ensure we give you a plan that’s not going to over-promise your car’s capabilities. Comparing to the Analytical Model Driving range vs speed comparison between the real world driving data and the original analytical model. Up to this point, we’ve been using an analytical model, using the drag characteristics, rolling resistance, and other parameters to determine an approximate driving model for the Bolt. Since we’ll be building a lot of these as more EVs come to market, we wondered how accurate the analytical model really is: As you can see, the models match quite closely! In fact, when building the Bolt analytical model, I added a 10% margin of safety to the model until we could validate using real world data, and you can see that at freeway speeds, the Analytical Bolt is about 10% lower than the Real World Bolt. Road Tripping in the Bolt With all the data we’ve got, let’s add the Bolt into the road table, and see where it falls: Model 3 Long Range: Total trip duration 09:43, of which charging 01:23 Model S100D: Total trip duration 10:05, of which charging 01:45 Model X100D: Total trip duration 10:29, of which charging 02:09 Model S60: Total trip duration 10:35, of which charging 02:15 Model X60: Total trip duration 11:28, of which charging 03:08 Bolt EV: Total trip duration 12:20, of which charging 04:00 This is using the “ABRP hypothetical road trip” is 1000 km (621 mi) in 200 km (124 mi) steps at 120km/h (75mph). The Bolt’s overall road trip speed is pretty slow. Even slower than the slowest Tesla. This is a consequence of the relatively slow charging that Chevy has built into the Bolt: Charge speed comparison, accounting for vehicle efficiency and battery size. Comparing the Bolt’s charge speed to that of the Model 3, we can see why our road trip takes so long! Accounting for battery size and driving efficiency differences, the Model 3 can charge nearly 2.5 times faster than the Bolt at each relative peak. All in all, the Bolt definitely can do those road trips, but it’s going to be at a much slower overall pace than the Model 3. The upcoming Hyundai Kona is a little bit faster than the Bolt, but not hugely, since it’s slightly less efficient. The larger battery makes for slightly longer range, but also means it takes a little longer to charge. Once we start getting some data, we’ll do a comparison to see how much faster the Kona really is than the Bolt. Appendix: Graphs in Imperial Units
  23. 0 points
    2019 Standard Range Plus I keep getting routes that keep randomly skipping different tesla supercharging stops. E.g. Golden, BC would allow this route to easily be made with shorter stops. https://abetterrouteplanner.com/?plan_uuid=7640dfc2-736d-4559-b7e3-1bf90e693719

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