Jump to content

Tesla Coil

  • Posts

  • Joined

  • Last visited

  • Days Won


Tesla Coil last won the day on September 13 2020

Tesla Coil had the most liked content!


2 Neutral
  1. Description: ABRP should calculate the optimum speed for each segment. Use Case: Currently, ABRP uses the speed limits of the road or live traffic and the maximum speed as set by the user. Whilst ABRP tries to optimise the time, it only drops the speed when this is necessary to reach the next charger. Example with the Model 3: https://abetterrouteplanner.com/?plan_uuid=e58b6959-18d8-43e4-b82e-f8c9b22b6153 I set a max speed of 198 km/h. This results in a time of 9 hours and 17 minutes. If you drop the max speed to 165 km/h, time taken is only 9 hours and 8 minutes. Same route with the Ampera-e: https://abetterrouteplanner.com/?plan_uuid=85feb0d7-6eb6-456d-9a74-a330c6a2f74e With a max speed of 160 km/h, this takes 12 hours and 38 minutes. At 130 km/h, it's only 12 hours and 19 minutes. These times could probably be optimised further by having different speeds on each segment. Whilst optimising this globally would be the best solution it is probably tricky as this introduces are many degrees of freedom. There could be a "light" optimisation by taking the charging locations as given and only varying SoC to charge to, and speed. You could then display an "optimum speed" at all times while navigating. Example: based on the charging curve of the Ioniq 28 kWh, it is always never good to charge to more than 83% as the charging power drops a lot above that (from ~48 kW to 22 kW). ABRP happily charges to a higher amount and then drives at full speed (e.g. 130 km/h as set in the default, which is close to optimal in general) if that is enough to reach the next stop. However, it is almost always better to charge to 83% only and drive a bit slower than 130 km/h. What do you think?
  2. Quick question: do you assume that there is a linear relationship between the displayed SoC and the energy in the battery? At least for the Ioniq 28 kWh this does not seem to be the case (and unfortunately, less energy is included in the lower SoC range).
  3. I leave an old Android phone in my car permanently to do the EVNotify uploading. This way I also get information while charging (when I take my normal phone with me). On short trips where I don't need ABRP, my normal phone then display EVNotify; on long trips ABRP.
  4. For Android Auto, you would be the first mapping/navigation app to get approval besides Google Maps and Waze (both Google-owned of course). So while I would support your efforts, I also want to make clear that nobody should get their hopes up too much that this will be implemented anytime soon. Apple Carplay is a bit more likely, there are some navigation apps on Carplay.
  5. Same issue in Germany with variable limits on the motorway. In many cases, those will show "130 km/h" or "unlimited". However, I believe that ABRP uses 110 km/h for those stretches. I typically drive 130 km/h (when allowed), which is also my speed setting, so this almost caught me out once as it suggested a significantly longer stretch than advisable at 130 km/h (not a lot of buffer in my Ioniq 28 kWh). I would suggest you switch those stretches to "unlimited" internally. Better to show a slightly too low travel time or send someone to a charger too early than suggesting legs that are not possible. In any case, when live traffic is used, if a limit is in place, this should automatically calculate everything correctly even if you treat it as unlimited internally.
  6. I have exactly the same problem on Android 10 (Pixel 2), also on the latest version of ABRP (3.9.12). Whenever I use "my location" instead of an address, I get the error message "we could not calculate your plan - plan not found". To be first, this is when I plan the trip when I'm sitting on the couch. My location (blue dot) is shown correctly on the map. I have my car (Ioniq 28 kWh) connected using EVNotify, and the app now works perfectly when driving. When the transmission of the phone is active, planning a route with "my location" sometimes works but not always.
  7. The old website view without map works well on a phone already so no need to wait.
  8. Same problem on Ioniq with EVNotify. Works in browser.
  9. Thanks for adding the current actual speed in no map mode. However, the speed is shown with at least 10 digits past the decimal point most of the time (sometimes, the number is round as well), like: 129.47363695742578 km/h. This then impacts the formatting further down below, where I can then not completely see the estimated SOC at the destination. I'm using ABRP as a Chrome Web App on Android 10 with a Pixel 2 in portrait mode.
  10. That's a shame. With the HPC chargers, this can have a massive effect since some of them are 900+ V and others are around 400 V only. If both have the same power, the 400 V ones have double the current meaning double the charging power for all cars except the Taycan. I'll check in the Going Electric forum whether the current and voltage can be made available. I think it was only possible to enter those into the station details in the last five months or so so maybe the API hasn't caught up yet.
  11. The maximum charging speed seems to be based only on the maximum power of the station, but current limits seem to be ignored. For a European Model 3 LR, the route planner suggests a stop at a allego CCS HPC charger. Arrival charge is 18%, departure charge is 59% and the charge duration is shown as 13 minutes. This averages out to around 140 kW. Unfortunately, even though the charger has a maximum power of 175 kW, the Model 3 will charge with around 70 kW only, because the charging station is restricted to 200 A and the battery of the Model 3 (at least at a SOC where it can take more than 200 A is less than 400 V). The 175 kW of the charging station are only reached at much higher voltages (around 900 V, more than double the maximum voltage of the Model 3) and will only be able to be used by the upcoming Porsche Taycan. The maximum current, voltage and power are included in the Going Electric data. See example station here: https://www.goingelectric.de/stromtankstellen/Deutschland/Bernau-am-Chiemsee/Shell-Station-Theodor-Sanne-Strasse-1/29316/ I think it would be important to address this in an update as those chargers are getting more and more common in Europe. And Model 3 owners (and some other cars as well) would get incorrect suggestions on where to charge fast. Do you have the charging curves for both voltage and current? If so, it should be possible to implement this.
  • Create New...