Swear the upgrade has done something bad...

[james_scott22]

Check this out. 80% charged, range 134 miles! So at 100% I could expect another 26 miles. Awful.

[MarkB]

Looks like the usual mixing up of units km and miles .. mine does it all the time the first time I had a real what the hecks going moment!... I make that an estimated 215miles

[Bryanmet]

Had mine done on Thursday. All vehicle data was reset to zero so GOM now estimates on last journey. If miles per kWh are low then perhaps that explains low estimate. Suggest you look over the next few days and see if it improves.

[Vasarolli]

215miles is 344km. On 80% soc that would be really great, not sure if I ever had that good value seen. This is an iv60 after all?

[MarkB]

My app currently shows 137miles the car shows 220miles at 80%, 1.6x higher,. Seems the app gets muddled up ... Would 215mile on 80% for a 60 unreasonable depending on circumstances?

[ChangoMutney]

My app currently shows 137miles the car shows 220miles at 80%, 1.6x higher,. Seems the app gets muddled up ... Would 215mile on 80% for a 60 unreasonable depending on circumstances?

The app frequently has the 1.61 error, but I've never seen the error in the car. Could be, as others have mentioned, a low economy short, cold trip from the dealer after a reset has messed up the value because there's no other information to base the range on until some more representative longer trips are performed.

[HarryHuk]

Looks like the usual mixing up of units km and miles .. mine does it all the time the first time I had a real what the hecks going moment!... I make that an estimated 215miles

Not for an iv60, which would normally have an estimated range of around 160miles @ 80% charge, depending on how you drive. The km/miles mixup would result in around 100 miles @80% charge.
As others have suggested, more likely the recent driving data has been reset during the update, and the estimated range will settle down with more miles driven.

Also, my car was delivered with ME3.0, and I've never seen the km/miles mixup in the car, only the app, and then only on completion of charge, and it resolves when you get in the car and start and then refresh the app.

[james_scott22]

Hi all. Definitely not a confusion of units, this is miles, and not the app, as the data is from the car, as you can see. I've done about 1000 miles since the upgrade, and commute 50 miles per day at an average (cruise control) speed of 64 mph.

It's crap

[Erakettu]

That looks completely normal.

(57kWh * 0.8) / (134mi * 1.61km/mi /100) = 21.1 kWh/100km

21kWh at 100km/h speeds is to be expected. At summer it might be a tad smaller consumption due to ambient conditions.

See attachment. Drove 107km/h highway for about 150km and the remaining trip at 50-80km/h. Outside temp around 5c, dry roads, no pre-heating. 19" summer tyres. Old 2.4 software.

[Goaty]

Hi all. Definitely not a confusion of units, this is miles, and not the app, as the data is from the car, as you can see. I've done about 1000 miles since the upgrade, and commute 50 miles per day at an average (cruise control) speed of 64 mph.

It's crap

Do you have some miles per kWh data to share too? I’ve not been driving my iV80 particularly efficiently recently, but still getting a prediction of 264 miles on a 100% charge. I’m on ME2.x.

A Trip Computer ‘average’ speed of 64 mph is quite high though; even when I think I’ve been mostly driving at 70mph, my average speed on a 100 mile run might only be around 55mph (according to the Trip Computer)