Jump to content

Witold Baryluk

  • Posts

  • Joined

  • Last visited


0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. In August Google and few other companies announced that third-party navigation apps are coming to Android Auto. There are beta tests of TomTom, MapFactor, SpotHero, PlugShare, Sygic GPS Navigation, ChargePoint, and two more navigation apps that I don't know the names. They are still in early access, as Google is finalizing rules and UI guidelines to make it non-distracting to the driver, etc. So they are not against competitive navigation solutions (other than Google Maps and Waze), it just takes a lot of time to set stuff up. I really hope the early access goes well and ABRP apply to the program soon. ABRP and OSMand would be super useful to have in the car.
  2. Not going to happen. Google only accepts audio media apps and messaging apps from third parties on Android Automotive OS. And even these are limited, i.e. arbitrary UIs are not allowed. No navigation, or other attentionion grabbing apps. The Android Auto is another option, but it also has limits, but things are being slowly relaxed. AFAIK, navigation is still not allowed fully. And you still need to go through the approval.
  3. Which one exactly? Name and address, and if needed screenshots from tesla and abrp. The one you provided the link is in ABRP map, it shows for me.
  4. @conny How is it going with reverse engineering PIDs? Are there some similarities to other existing cars?
  5. @chuq I made a copy of your sheet for testing, and imported into my Google My Maps, and got this: https://www.google.com/maps/d/edit?mid=1xOqOOr3deP93t6TFwTKEWVPoYBxcyuur&usp=sharing https://www.google.com/maps/d/viewer?mid=1xOqOOr3deP93t6TFwTKEWVPoYBxcyuur I just did that for fun (I don't even live in Australia lol), but you can make a map very quickly like that. I have no idea if it will update as the sheet is updated tho. It might or might not. Unclear to me from documentation.
  6. According to information I found, this location in Hammond, LA, has 7 CCS chargers. Shouldn't be too risky (it is unlikely all of them are broken, or all occupied, unless things change later based on real data, which should influence the reroute, but not the main planning). Anyhow, great you are doing these important fixes, and people are scrutinizing plans for any obvious issues like that.
  7. What browser are you using? Is this on a phone (what phone and browser?) or desktop / laptop (what browser, and how much memory). I don't have issues with rearranging waypoints in the list (even with 20+ entries). It is a bit slow and not super smooth, but it works just fine.
  8. Do you have some github repo maybe where you document it or something? Would be great. Thanks!
  9. What about preferring slower chargers 😉 A bit niche, but you might be fine with longer breaks on medium length trips, and slower charges usually prolong battery life in one way or another, and many EV charging stations doesn't really care about time spent charging.
  10. Even better an extra column that shows a cumulative time in minutes starting from 0 at the departure, would be very useful. As of the time, yes, hopefully full date and time are included. CSV with ISO 8601 would be super useful to have. I can't stand Excel or other spreadsheet formats.
  11. I agree. I learned of ABRP just few days ago. When I checked the suggested routes for the first time yesterday, I was really surprised it didn't suggest any speed for any of the trip leg to optimise the total trip time. IMHO this is a MUST TO HAVE feature. From my research and own calculations (spreedsheets and Python scripts), some cars do have optimum at very high speed (135km/h), if they have access to fast chargers (like 100kW), but when using 50kW, this drops significantly to about 110km/h. Obviously the exact values also depend on exact charging curves, elevation changes, ambient temperature, and other conditions, all of which can be mostly modeled too. The others like speed changes, overtaking, curves, wind, are a bit harder, but on average can be ignored IMHO. For short trips and city driving this optimisations and suggestions are mostly irrelevant, but for longer trips, it definitively is worth improving your effective trip speed. It can be 10-15% in the total time on a long trip.
  12. Hi guys, do you plan to share submitted data to community, to also do own modelling and learn things? This would be really useful. I.e. I do have a program that does try to predict optimal cruising speed to maximize long range trip effective speed. (including charging time and charging curves), but to make it effective one needs to know the power usage at any given speed. A github repo with some curated data point would be really awesome for research and discussion. I would also suggest to add few fields to the notes in the table:. Which car exactly is used, i.e. motor configuration, battery size, age of the vehicle, tires used, wet / dry condition, is it raining, outside temperature, is AC / heating on, is there extra cargo / weight in the car, any other high power devices on (i.e. laptop, fridge, non-standard lights). Cheers, Witold
  13. Hi Katya. It is not just a placeholder. It actually uses 31% as a default when doing a plan, if I don't fill that field. I cleared the cookies and opened abrt a new, selected some other car, and some new route. It assumed 90% initial Departure SoC, makes perfect sense. And it is 90% in the settings, and it also shows there as a placeholder, not a value. The placeholder in Deprature settings, SoC shows 90. But it should be a value maybe? Or does it have some weird interactions with settings? I am not sure why I got 31 yesterday. Maybe because I was using different car model for testing. Not sure.
  • Create New...