New Year Service Overdue Bug

[OkGo]

2098 here.

Winning?

 

[ECrider]

A bit rough mate. I don't believe in " karma" any more than a dog does.
Keep ya hair on, as my dad said

how a bout a chicken karma with pilau rice?

 

[Krabby]

how a bout a chicken karma with pilau rice?

As long as there’s lots of naan I’m in.

 

[ECrider]

I had been driving around with the service overdue notice since I self serviced the truck back in September, finally got it reset last week when had the front shaft replaced - bam now have it again!! Mind you, two poles on the left arm cluster and all is well.

 

[Tazzieman]

As long as there’s lots of naan I’m in.

Leave her out of this

 

[ECrider]

As long as there’s lots of naan I’m in.

Do you like an older woman?

 

[Krabby]

Hahaha.

Note: n - a - a - n (not nana).

 

[Tazzieman]

Hahaha.

Note: n - a - a - n (not nana).

The word comes from the Persian word for bread = NAN

 

[Phred]

A bit rough mate. I don't believe in " karma" any more than a dog does.
Keep ya hair on, as my dad said
View attachment 7917998

Not at all…

There are ZERO reasons to not allow us to reset other than a money grab. So now, it will cost THEM money.
That is KARMA.

 

[Tazzieman]

Not at all…

There are ZERO reasons to not allow us to reset other than a money grab. So now, it will cost THEM money.
That is KARMA.

 

[Glen]

So this gets a little deep into math, so hang in there.

1) Suppose my 2025 Grenny was built on February 11, 2025. This seems reasonable since it's a 2025 model.
2) A service interval due date might be calculated as February 11, 2025 + 365 days = February 11, 2026.
3) On January 1, 2026, I am 41 days from needing a 365-day service due message.
4) Another way to calculate a service interval, shown here in pseudocode:

daysSinceServiceDue = todaysDate - (lastReset + 365)
if daysSinceServiceDue > 0 then show the number of days

For my vehicle, this calculation would be
-41 = January 1, 2026 - (February 11, 2025 + 365)
So it's 41 days before I need service and no message should be displayed.

Here's the hard stuff:

5) Binary numbers can be stored as signed or unsigned. An unsigned binary can only store POSITIVE numbers. A signed binary can store POSITIVE or NEGATIVE numbers. There's nothing special about a bunch of 0's and 1's strung together to represent a binary . . . you need to know if you're dealing with a signed or unsigned binary and do the right conversion.

6) The decimal number -41 as a signed binary is 11111010111. But if you make a mistake and treat 11111010111 as an unsigned binary, the decimal equivalent is 2007.

7) Here's the conversions for the signed binary equivalent of
-41 = 111 1101 0111:

Bit   Value   Power of 2    Decimal Contribution
---   ------   ------------    -----------------------
0        1              1                  1
1        1              2                  2
2        1              4                  4
3        0              8                  0
4        1             16                 16
5        0             32                  0
6        1             64                 64
7        1            128                128
8        1            256                256
9        1            512                512
10       1           1024               1024
                                      ------
                                    SUM 2007

The sum of these numbers is 2007 and that is the decimal value of the UNSIGNED binary. To yield the SIGNED binary, we subtract 2^11 (= 2048) from the result (where 11 is the number of digits in the binary number). So 2007 - 2048 = -41.

So in my case, it might be the INEOS programming treated the binary number of days before service due as an unsigned binary. This would yield 2007 days since service due and display a message since 2007 > 0 (see the pseudocode at item 4 above). But the program should have treated the binary number of days before service due as a SIGNED binary . . . this would yield -41 and no message would display.

Cheers!

edit: took a bunch of edits to make the table readable since this BBS won't support more than a 10-row table. Good grief!

 

[MattG]

Check and reset your date, it may have been automatically set to 2032. You can disable Automatic date, set the correct date, then enable Automatic date back (also don’t forget to enable DST setting, if applicable)

Mine had also set the date to 1/1/2032, resulting in an overdue service reminder of 1989 days or so. Changing the date to 1/1/26 did not get rid of the service reminder however. Annoying.

 

[Logsplitter]

So this gets a little deep into math, so hang in there.

1) Suppose my 2025 Grenny was built on February 11, 2025. This seems reasonable since it's a 2025 model.
2) A service interval due date might be calculated as February 11, 2025 + 365 days = February 11, 2026.
3) On January 1, 2026, I am 41 days from needing a 365-day service due message.
4) Another way to calculate a service interval, shown here in pseudocode:

daysSinceServiceDue = todaysDate - (lastReset + 365)
if daysSinceServiceDue > 0 then show the number of days

For my vehicle, this calculation would be
-41 = January 1, 2026 - (February 11, 2025 + 365)
So it's 41 days before I need service.

Here's the hard stuff:

5) Binary numbers can be stores as signed or unsigned. An unsigned binary can only store POSITIVE numbers. A signed binary can store POSITIVE or NEGATIVE numbers. There's nothing special about a bunch of 0's and 1's strung together to represent a binary . . . you need to know if you're dealing with a signed or unsigned binary.

6) The decimal number -41 as a signed binary is 11111010111. But if you make a mistake and treat 11111010111 as an unsigned binary, the decimal equivalent is 2007.

7) Here's the conversions for the signed binary equivalent of
-41 = 11 11101 0111:

SIGNED BINARY
The input has 11 digits. Proceeding from right to left:
Bit Value Power of 2 Decimal Contribution
--- ----- ----------- -------------------
0 1 2^0 = 1 1
1 1 2^1 = 2 2
2 1 2^2 = 4 4
3 0 2^3 = 8 0
4 1 2^4 = 16 16
5 0 2^5 = 32 0
6 1 2^6 = 64 64
7 1 2^7 = 128 128
8 1 2^8 = 256 256
9 1 2^9 = 512 512
10 1 2^10 = 1024 1024

The sum of these numbers is 2007 and that is the decimal value of the UNSIGNED binary. To yield the SIGNED binary, we subtract 2^11 (= 2048) from the result (where 11 is the number of digits in the binary number). So 2007 - 2048 = -41.

So in my case, it might be the INEOS programming treated the binary number of days before service due as an unsigned binary when it should have treated the binary number of days before service due as a SIGNED binary.

Cheers!

That’s gone straight over my head after 1/2 bottle of red.
Mine was built on the 19 January 2023 and I now have a 2051 day overdue service date. Work that one out if you can . cheers.

 

[Krabby]

 

[Tazzieman]

@Glen are you sure about you're calcs?
Have you accounted for those of us that drive RHD and are on the bottom half of the globe?

 

[Phred]

Glen man, slow your roll…it’s Jan 1.

You are going to use up all your maths on day 1.

 

[Michael H.]

@Glen are you sure about you're calcs?
Have you accounted for those of us that drive RHD and are on the bottom half of the globe?

And, very importantly, why are the Aussie reminders in the format xxxxDay, whereas others are expressed as xxxxd ??

 

[Mazeman]

How do you folks see what your build date is?

 

[Tazzieman]

And, very importantly, why are the Aussie reminders in the format xxxxDay, whereas others are expressed as xxxxd ??

A fine observation and one that requires detailed analysis, and a refund.

 

[Logsplitter]

How do you folks see what your build date is?

Your certificate of conformity has your build date on it