trip computer glitch ?

[mysoulev]

the 8.1km trip was just another normal trip, but the energy consumption history was way out of whack.

after that the GOM has been fluctuating a lot: showing only 150km after a full charge, then jumped up to 170 after a short 5km trip, then dropped to 140 after another short trip........

has anyone seen something like that?

 

[JejuSoul]

Yes. After resetting the trip meter the first few trips sometimes have really strange numbers. It settles down after a day or two.
Here's one from six months ago. Coincidentally 102.3 but completely different units. (Mine is the inverse of yours)

 

[mysoulev]

Coincidentally 102.3 but completely different units. (Mine is the inverse of yours)

interesting, 102.3 must be a meaningful number to some KIA programmer.

i ran the battery down to about 15% SOC and got about 160km so i'm still getting the same range, no worry here.

 

[Leafer]

Coincidentally 102.3 but completely different units. (Mine is the inverse of yours)

interesting, 102.3 must be a meaningful number to some KIA programmer.

i ran the battery down to about 15% SOC and got about 160km so i'm still getting the same range, no worry here.

Just guessing here ... but how about 102.3 ==> 1023 (with decimal point) == the highest decimal number representable with 10 (ten) bits (binary digits) ? ( 0 - 1023 ) ...

Why use 10 (ten) bits ? No idea ... unless 100 is the maximum they expected in the fuel efficiency results -- expressed in varying sets of units.



P.S.: A widely circulated mathematical joke: "There are only 10 types of people in the world: those who understand binary, and those who don't." And programmers are the "worst offenders" of the first kind ;-)

 

[JejuSoul]

Just guessing here ... but how about 102.3 ==> 1023 (with decimal point) == the highest decimal number representable with 10 (ten) bits (binary digits) ? ( 0 - 1023 ) ...

A good guess. I'll go with that. They store the trip number as a 10 bit binary.
The other more common glitch is to see the time as Thursday, 1 January 1970. This is zero Unix time.
Older programmers have a big advantage in figuring out the quirks of this car.

Here's the Unix Time glitch on a French car.

 

[JejuSoul]

In only a week of driving an Ioniq EV I have already seen two similar glitches.
The system is slightly different because it gives an average for the whole day rather than for each trip.

The error value for Energy Economy is no longer 102.3 but 99.9

The value 3516.00km is bogus. Probably I drove 351.6km that day.

Here's a glitch in the Ioniq EV - someone drove further from here.

 

[mysoulev]

The value 3516.00km is bogus.

a Guinness record, the most distance driven by an EV in a day ...

the SoulEV's energy History is too simplified, it would be nice to have all 3: per trip/day/reset.

 

[SoulEV2016]

perhaps a simple GPS bug (1970 date to start a schedule clock without the sync. of the local date and hour).

 

[Leafer]

The value 3516.00km is bogus. Probably I drove 351.6km that day.

Hmmm ... not only a record of most EV km driven in one day ... but it also appears they increased the top speed by just a hair ... (3,516.00 km / 24 hours = 146.5 kph).

 

[JejuSoul]

The trip computer glitch in the Kia Soul EV seems to have been updated in one of the recent software updates.
We now have the same glitch as the Ioniq EV.
Wish they would actually fix the software while they are working on it.

This car in Germany must have the older software version. It's the 102.3 glitch.

Here's the same old glitch in France

And the same in Spain.