Join our newly restarted iOS Beta and try out new features sooner: https://testflight.apple.com/join/PDzBYbJw
Read more about ABRP beta at Installing the ABRP Beta version
Hello Any info, when the B03x will be added to the car data pool? Greetings from Switzerland, Philipp
ABRP report User reports (original wording): "Hello ABRP Team, I'd like to suggest a feature that I believe would significantly improve the Android Auto experience for electric vehicle drivers, especially during long-distance trips. 1. Display Charging Station Brands Directly on tDisplay Charging Station Brands Directly on the Map When navigating along a planned route, I would like to see the names or logos of charging networks (such as ZES, Eşarj, Trugo, etc.) directly on the Android Auto map, without having to tap on each charging station individually. This would make it much easier to identify available charging options at a glance while driving. 2. One-Tap Access to Charging Stations Along the Route I suggest adding a dedicated "Charging Stations Along Route" button to the Android Auto interface. With a single tap, this button would display a list of upcoming charging stations, including: - Charging network name or brand - Driving distance from the current location (e.g., 5 km, 12 km) - Charging power (e.g., 60 kW, 180 kW) - Real-time charger availability, if available - Additional detour distance required to reach the station 3. Filter Stations Based on the Actual Route and Direction of Travel This is probably the most important part of my suggestion. Currently, when using the "Nearby Chargers" feature, the app also displays charging stations that are behind the vehicle or located in areas unrelated to the planned route. Although these stations may be geographically close, they are not necessarily useful during an ongoing journey. When navigation is active, I would prefer to see only charging stations ahead of my current position, either directly along my route or accessible with a reasonable detour. Ideally: - Charging stations already passed should be excluded. - Stations unrelated to the current route should not appear. - Stations should be sorted by actual driving distance along the route, rather than driving distance along the route, rather than straight-line distance. - Any additional detour distance should be clearly displayed. - Selecting a station should allow it to be added to the active navigation route as a charging or rest stop with a single tap. 4. Real-Life Use Case Imagine driving on a highway during a long trip without having planned a charging stop in advance. At some point, I decide to take a break and possibly charge my vehicle. Instead of searching the map, tapping individual charger icons, or interacting with my phone, I simply tap the "Charging Stations Along Route" button on Android Auto. I would see something like this: - 5 km ahead — ZES — 180 kW — Directly on route - 12 km ahead — Trugo — 180 kW — 1 km detour - 24 km ahead — Eşarj — 120 kW — Directly on route I could then immediately decide, "There's a ZES station 5 km ahead. Let's stop there." 5. Main Goal: Simpler and Safer Charging Decisions While Driving My main expectation is to be able to quickly identify relevant charging stations ahead of me, without unnecessary information about stations behind me or outside my route. I believe this feature would make ABRP even more practical for everyday EV driving, especially when drivers want to make spontaneous charging or rest stops rather than planning every stop in advance. It would also help minimize screen interactions and distractions while driving. Thank you for considering this suggestion. I really appreciate the work your team is doing to improve EV navigation, and I hope this feature can be considered for a future update. Best regards"
https://abrp.featurebase.app/p/add-voyah-frree-2024/comment/6ade492c3c4f957a24be8567 Earlier I had contact with Mahde on above ticket, but this ticket is closed, so maybe any new reactions are not triggered. Therefore I created this new ticket with the below question: ABRP User #1373137 25 okt Ok I have scripted (python) the search for possible candidates for sensor commands (read 19800 values out of the module and had AI analyse it ) that could represent SOC , and I have a few now that actually give values back that are corrresponding with the car’s app . So I found the actual command for the Voyah Free’s SOC, and I can either put the command and calculation in an existing Carscanner sensor or I can create a custom sensor with a certain name. How do I make sure that ABPR takes that sensor into the live data read? Just name it ‘SOC’ (currently it only shows Location??
already visible in ionity app but not in ABRP please check location here:
Last week (October 21 to 22) I took my little Fiat 500e on a 930km Roadtrip (2× 465km). I run the the Beta Version with Premium subscription and OBD connection. On the plus side: The Android Auto seems to be less resource hungry than it was back in july when I did my last roadtrip. On the negative side: On day one, the weather was bad. We were mainly driving toward west with a strong wind (about 20 km/h with 50km/h gusts) coming from the south west so roughly hitting the car front at and angle of 30 to 45°. Each stretch between charges was roughly 150 to 180km with 15% planned charge level at charging stop. What actually happened is that we ended up having 5 to 10% offset to what was initially forecast by ABRP. We hit one charger with only 5% battery left whereas at the beginning of the stretch ABRP calculated we would arrive at the charger with 15%. On Day two we still had strong winds, but since we were heading eastward the wind would hit the car from behind with an angle of 30 to 45°. Even there we reached each charger with 7 to 9% level lower than what was initially expected. When leaving a charger the estimated level was ok. We left a charger with 90% charge level, estimated level at arrival was 15%. While driving, the estimated arrival level would stay stable until we had reached about half to two third of the stretch, than it started dropping. IMHO ABRP did not take the weather conditions into consideration and/or just stuck with the consumption curves it had since the last 2 years I have been using instead of adapting live to the bad weather. I could understand that it gets the first stretch wrong, but the second one it should get it more accurate. I hope this feedback will be helpful.
I don’t believe this car has an lfp battery as your comparison says.
Engie Vianeo has a 9,9€/m subscription for a 0,33€/kWh and I can't find it to the available cards
Need to search by 1) direct payment credit card and 2) direct payment debit card.