ABRP 6.x a real improvement !

JIS

Established Member
Joined
Nov 10, 2024
Messages
105
Reaction score
75
Points
47
Location
Chenac, SW France
Driving
MG4
So I use the OBDLink to transfer live data from the car to ABRP but, until now, the forecast consumption was poor; ultra conservative or totally inaccurate! However today we have done a 250 km trip and I was VERY impressed that ABRP's forecast there and back was accurate to within 1% ! Amazing; previously it was around 15% out.
So with this major improvement and the fact that ABRP is now usable from the Apple AirPlay screen (to add stops etc), the product becomes so much more useful. So, in my view, it has bettered Google Maps for long journeys. The only aspect that Google Maps still wins is realtime traffic alerts re traffic jams etc. However you will each have your own favourite :-)
 
Too bad some ABRP features are still behind a paywall though. While it's a nice app, i don't think it's worth 50€/year. If they offered a one time payment, at least that would be something to consider.

Until then, sideloaded to the infotainment (so you get around the free version restriction for carplay/aa) and using saic-mqtt to feed it data (no need for an OBD dongle) works pretty well, albeit in some limited capacity.
 
I used 1 time the free trial and 2 times a one month payment, so for that amount it seemed ok back than, even though it is adament to take me down country roads thinking if the speed limit is 90kmh i will somehow take all those windy roads at that speed flat out.
 
i fear that my point was missed. I am not questioning ABRP's cost, merely pointing out that it used to be very inaccurate and now it seems super accurate PLUS it now offers touch screen option to add a stop to the planned journey.
I also like the fact that towns and villages are clearly named on the ABRP screen which is a big failure of Google maps where I often wonder where I am !!
If they could just add a compass then it would be nigh-on perfect for me. Yes it costs but we need to fund the developers !
 
It is sort funny that we now rely on Apps to navigate when a little planning can often be the only thing to think about before you start a journey.
Like finding out where the chargers are along your intended route.
People need to be a little more aware of how far your EV can go on a full charge and plan to recharge when at say 50% or there about to get the next planned charger.
 
I recently noticed you can adjust fuel consumption in there so that might make it more accurate than allowing the app to estimate it. That should help the leadfoots.....
 
It is sort funny that we now rely on Apps to navigate when a little planning can often be the only thing to think about before you start a journey.
Like finding out where the chargers are along your intended route.
People need to be a little more aware of how far your EV can go on a full charge and plan to recharge when at say 50% or there about to get the next planned charger.

that's actually a pretty terrible idea. Charging from 50 to 80 or even 100% is really slow. You're better off planning your charger stop to be as close to 10% as possible for maximum charging speed.

Unless of course you drive in a country where CCS charger are few and far between.
 
So I use the OBDLink to transfer live data from the car to ABRP but, until now, the forecast consumption was poor; ultra conservative or totally inaccurate! However today we have done a 250 km trip and I was VERY impressed that ABRP's forecast there and back was accurate to within 1% ! Amazing; previously it was around 15% out.
So with this major improvement and the fact that ABRP is now usable from the Apple AirPlay screen (to add stops etc), the product becomes so much more useful. So, in my view, it has bettered Google Maps for long journeys. The only aspect that Google Maps still wins is realtime traffic alerts re traffic jams etc. However you will each have your own favourite :-)
I'm a fan of Waze. It's underlying maps are Google Maps but users can, and do, update traffic information.
 
It is sort funny that we now rely on Apps to navigate when a little planning can often be the only thing to think about before you start a journey.
Like finding out where the chargers are along your intended route.
People need to be a little more aware of how far your EV can go on a full charge and plan to recharge when at say 50% or there about to get the next planned charger.
Yes up to twenty years ago I used my trusty Michelin maps all the time. Now however,, with ABRP taking live data from my MG4 it now forecats with incredible accuracy my trips. Today we went to the beautiful town of Cognac and back. It's not very far from us but, neverthess ABRP forecast the SoC within 1% which, for my money is fantastic.
I do agree that it's important to always have a fallback charger if there is a problem with the one planned but, again, with realtime data I know how many charge points are in use and their speed and what payment options they accept. All of which makes for a very comfortable experience.
 
ABRP for me will always have a place during a trip planning, especially if the trip requires 2 or more charge stops. It is not the only tool though, but at the beggining as a newbie it helped with the range anxiety.

While the Netherlands is one of the flattest countries and i can calculate my consumption, i still face highway congestion and driving at 70, 80 km/h or traffic jams and start stop traffic.

However, once i leave NL, things change drastically and having OBD2 available in ABRP, i get quite a good estimate.

Routing though is still completely weird. The other day i did a round trip of about 180km one way. For the route tobthe location, it routed me through 100km highway and 80 km or national roads at 80km/h speeds. I wondered where did we go that is so remote that there is no highway in the NL!? The route back took me to a highway within the first 10 km and i stayed on a highway for the entire trip back. I checked google after i got home and it routed me the same. My theory is that navigation software seems to favor either a left or a right turn, and when it comes to a point it needs to take a turn it favors say right turns. That could explain why we get a different route back maybe.

Another thing that is hard to do is say i want to visit friends, and i want to reach them with a high statebof charge in case we decide to go somewhere by car. I have to plan only a one way trip with a high level 80+% SoC at destination to get a charger near the end. If i simply started a route and did not set arrival SoC to be high, there is no way to skip a charge that i feel is too soon since it takes me to a charger in the middle of my rrip at 40% . If i drive past the charger, it routes me back to it.

But, still it helps in combination with PlugShare.

I wonder if the new Android Auto Live Data will change something though? Has anyone tried AA without an OBD2 dongle and was able to get SoC and consumption from AA? Does MG4 support that?
 
.

I wonder if the new Android Auto Live Data will change something though? Has anyone tried AA without an OBD2 dongle and was able to get SoC and consumption from AA? Does MG4 support that?
It didn't appear to. This would be the best solution.

Regarding the cost discussion above. I think the developer deserves some payment for the free service provided to us all so I subscribe 2-3 times a year for a month to get additional features and to support the development.

Regarding accuracy, I often find that it's give back to 5% degradation and my battery has 100% SoH so changing that to zero fixed the accuracy for me. It improves with usage as it father's more data from the dongle.
 
ABRP for me will always have a place during a trip planning, especially if the trip requires 2 or more charge stops. It is not the only tool though, but at the beggining as a newbie it helped with the range anxiety.

While the Netherlands is one of the flattest countries and i can calculate my consumption, i still face highway congestion and driving at 70, 80 km/h or traffic jams and start stop traffic.

However, once i leave NL, things change drastically and having OBD2 available in ABRP, i get quite a good estimate.

Routing though is still completely weird. The other day i did a round trip of about 180km one way. For the route tobthe location, it routed me through 100km highway and 80 km or national roads at 80km/h speeds. I wondered where did we go that is so remote that there is no highway in the NL!? The route back took me to a highway within the first 10 km and i stayed on a highway for the entire trip back. I checked google after i got home and it routed me the same. My theory is that navigation software seems to favor either a left or a right turn, and when it comes to a point it needs to take a turn it favors say right turns. That could explain why we get a different route back maybe.

Another thing that is hard to do is say i want to visit friends, and i want to reach them with a high statebof charge in case we decide to go somewhere by car. I have to plan only a one way trip with a high level 80+% SoC at destination to get a charger near the end. If i simply started a route and did not set arrival SoC to be high, there is no way to skip a charge that i feel is too soon since it takes me to a charger in the middle of my rrip at 40% . If i drive past the charger, it routes me back to it.

But, still it helps in combination with PlugShare.

I wonder if the new Android Auto Live Data will change something though? Has anyone tried AA without an OBD2 dongle and was able to get SoC and consumption from AA? Does MG4 support that?

Just setup a MQTT bridge with the saic python script and feed the data directly to ABRP.

And i agree fully; as a navigation, ABRP is absolutly terrible.
 
Support us by becoming a Premium Member

Latest MG EVs video

MG ZS EV Retrospective & First Look at the MGS5 EV | Live Q&A with Owners & MGEVs Panel
Subscribe to our YouTube channel
Back
Top Bottom