The Grenadier Forum

Register a free account today to become a member! Once signed in, you'll be able to contribute to the community by adding your own topics, posts, and connect with other members through your own private inbox! INEOS Agents, Dealers or Commercial vendors please use the contact us link at the bottom of the page.

New Year Service Overdue Bug

There is something called the "2038 Problem" where millions of 32 bit processors will run out of code in January 2038. I suspect it may be something like that rather than Y2K.
When I was a lad in the 70s, the year 2038 seemed like a time when cars had been long superceded!
 
1625 here!! Sorry to steal the thunder @cook
 

Attachments

  • IMG_0848.jpeg
    IMG_0848.jpeg
    2.7 MB · Views: 14
I once had a problem with my W203 Mercedes: the (GPS-based) date display was malfunctioning. The problem stemmed from a number transmitted by the GPS that, for some reason, didn't use the actual year of the initial GPS setup, but rather a 10-bit counter that overflowed at 1023 and then to 1024.

At 1024, it was reset to zero.

As a result, the dates were incorrect - and remained so, since Mercedes never fixed this bug.
It's also possible that unusual GPS standards are involved here.

Just speculating ...
 
TALLY (Updated)
ResponsiblyReckless 1625 days
Chook 1840 days
Itsdchz 1841 days, first US car with the pox
BrandonADV 1852 days
TahoeGren 1852 days
Pat-Ard 1868 days
Rok Dr 1869 days
Sonoranrover 1875 days
Chem409 1890 days
Michael H 1889 days
Duncan McDonald 1892 days
joejet 1894 days
Korg 1899 days
GrenADV 1901 days
Grumpy 1906 days
HeavyFoot 1915 days
pedrogb1915 days
OGrid 1927 days
singlefin 1927 days
WhiteBear 1931 days, first car outside ANZ
ecohen2 1932 days
Happyoldgit 1933 days
OkGo 1937 days
NixGrenadier 1940 days
ddv 1945 days (Aug 2023)
Tergosa 1946 days
Johnb1950 days
Fred 1950 days
Camilondo 1953 days
Jeremy966 1967 days
Ex-defender driver 1968 days
TheDocAUS 1968 days (Feb 2024)
Denis M 1975 days
MattG 1989 days
Green Gren 1903 days
TJD 1985 days
Phred 1994 days
douggie 1995 days
Glen 2007 days
Badger4x4 2007 days
Adam 2007 days
Baron van T 2009 days
Silverjay 2022 days
Chris Hilton 2024 days
Tony H 2025 days
SaudiGR 2026 days
Landmannn 2044 days
acky 2048 days
Commodore 2057 days
NeoGTi 2057 days
Greasemonkey 2059 days
Lollo050968 2074 days
Wile E Coyote 2095 days
Dschubba 2097 days
Stu Barnes 2097 days
Manuel4x4 2106 days
Mazeman 2107 days
Tazzieman 2137 days
pipo 2149 days
Logsplitter 2150 days
Skymark 2156 days
slukell 2175 days
Emil 2190 days
bigleonski 2250 days
Ron50 2253 days
Clark Kent 2367 days
C-Mack 2458 days
mirwantandyo 2668 days

NET ZERO
Steve B, baders and Jean Mercier have no alert.

INEOS TALKS
INEOS has acknowledged the issue here.

SUMMARY
Chook gets roasted by ResponsiblyReckless at the bottom of the pile. First and only number below 1800.


68 members listed so far, from lowest to highest number of days. Plus 3 members with no alert.
 
Last edited:
TALLY (Updated)
ResponsiblyReckless 1625 days
Chook 1840 days
Itsdchz 1841 days, first US car with the pox
BrandonADV 1852 days
TahoeGren 1852 days
Pat-Ard 1868 days
Rok Dr 1869 days
Sonoranrover 1875 days
Chem409 1890 days
Duncan McDonald 1892 days
joejet 1894 days
Korg 1899 days
Grumpy 1906 days
HeavyFoot 1915 days
pedrogb1915 days
OGrid 1927 days
singlefin 1927 days
WhiteBear 1931 days, first car outside ANZ
ecohen2 1932 days
Happyoldgit 1933 days
OkGo 1937 days
NixGrenadier 1940 days
ddv 1945 days (Aug 2023)
Tergosa 1946 days
Fred 1950 days
Camilondo 1953 days
Jeremy966 1967 days
Ex-defender driver 1968 days
TheDocAUS 1968 days (Feb 2024)
Denis M 1975 days
MattG 1989 days
Green Gren 1903 days
TJD 1985 days
Phred 1994 days
douggie 1995 days
Glen 2007 days
Badger4x4 2007 days
Adam 2007 days
Baron van T 2009 days
Silverjay 2022 days
Chris Hilton 2024 days
Tony H 2025 days
Landmannn 2044 days
acky 2048 days
Commodore 2057 days
NeoGTi 2057 days
Greasemonkey 2059 days
Lollo050968 2074 days
Wile E Coyote 2095 days
Dschubba 2097 days
Stu Barnes 2097 days
Manuel4x4 2106 days
Mazeman 2107 days
Tazzieman 2137 days
pipo 2149 days
Logsplitter 2150 days
Skymark 2156 days
Emil 2190 days
bigleonski 2250 days
Ron50 2253 days
Clark Kent 2367 days
C-Mack 2458 days
mirwantandyo 2668 days

NET ZERO
Steve B and Jean Mercier have no alert.

INEOS TALKS
INEOS has acknowledged the issue here.

SUMMARY
Chook gets roasted by ResponsiblyReckless at the bottom of the pile. First number below 1800.


63 members listed so far, from lowest to highest number of days. Only 2 members with no alert.
my score is 1841 days - 'on the road since Dec 2024"
 
@TheDocAUS So far I haven’t bothered to list my rather nondescript 1889 days, but I’m starting to feel left out, so please add me to the list. 🙂

Also a good time to remind others that haven’t read the whole thread … you can stop the reminder constantly popping up by double clicking the TRIP button on the end of the indicator stalk, but you’ll have to do this every time you start the vehicle.
 
I noticed that there aww a few of us with the same number of days showing. I wonder if we can figure out the communalities and then the root cause from that data.
 
I have a hunch the current lead of “2668 days” is a very late ‘23 or early ‘24 production model with less than 1,500 miles on it and no software updates since rolling off the assembly line. In other words, completely original. Certainly prepared to be wrong though.
 
@TheDocAUS So far I haven’t bothered to list my rather nondescript 1889 days, but I’m starting to feel left out, so please add me to the list. 🙂

Also a good time to remind others that haven’t read the whole thread … you can stop the reminder constantly popping up by double clicking the TRIP button on the end of the indicator stalk, but you’ll have to do this every time you start the vehicle.
Added.
 
I noticed that there aww a few of us with the same number of days showing. I wonder if we can figure out the communalities and then the root cause from that data.
I think there are now 4 number with multiple cars, but only one number has appeared three times..
 
There is something called the "2038 Problem" where millions of 32 bit processors will run out of code in January 2038. I suspect it may be something like that rather than Y2K.
Thankfully all bmw control units /modules are 64 bit. So not that.
 
At this stage I have no alert West Oz based base model specced up wagon '23 build.
 
More wild speculation . . .

. . . so if INEOS only used a 10-bit two's complement for signed binaries, they would truncate values with modulus 1024 (keep subtracting 1024 until you get a number smaller than 1024). In other words, they don't expect someone to go more than 1024 days (2 years 9-1/2 months) without getting a reset. Using that scheme, I generated a table showing the error message days in the first column and your expected service date in the far right column. Does this jive with reality for anyone?

Code:
Error Msg / Modulo 1024 / 10-bit Binary / Days Since Service Due / Service Due Date

1840 816 1100110000 -208 Jul 28, 2026

1841 817 1100110001 -207 Jul 27, 2026

1852 828 1100111100 -196 Jul 16, 2026

1852 828 1100111100 -196 Jul 16, 2026

1868 844 1101001100 -180 Jun 30, 2026

1869 845 1101001101 -179 Jun 29, 2026

1890 866 1101100010 -158 Jun 08, 2026

1892 868 1101100100 -156 Jun 06, 2026

1894 870 1101100110 -154 Jun 04, 2026

1899 875 1101101011 -149 May 30, 2026

1906 882 1101110010 -142 May 23, 2026

1915 891 1101111011 -133 May 14, 2026

1927 903 1110000111 -121 May 02, 2026

1931 907 1110001011 -117 Apr 28, 2026

1932 908 1110001100 -116 Apr 27, 2026

1933 909 1110001101 -115 Apr 26, 2026

1937 913 1110010001 -111 Apr 22, 2026

1940 916 1110010100 -108 Apr 19, 2026

1945 921 1110011001 -103 Apr 14, 2026

1950 926 1110011110 -98 Apr 09, 2026

1953 929 1110100001 -95 Apr 06, 2026

1967 943 1110101111 -81 Mar 23, 2026

1968 944 1110110000 -80 Mar 22, 2026

1968 944 1110110000 -80 Mar 22, 2026

1975 951 1110110111 -73 Mar 15, 2026

1989 965 1111000101 -59 Mar 01, 2026

1903 879 1101101111 -145 May 26, 2026

1994 970 1111001010 -54 Feb 24, 2026

1995 971 1111001011 -53 Feb 23, 2026

2007 983 1111010111 -41 Feb 11, 2026

2007 983 1111010111 -41 Feb 11, 2026

2007 983 1111010111 -41 Feb 11, 2026

2009 985 1111011001 -39 Feb 09, 2026

2022 998 1111100110 -26 Jan 27, 2026

2024 1000 1111101000 -24 Jan 25, 2026

2025 1001 1111101001 -23 Jan 24, 2026

2044 1020 1111111100 -4 Jan 05, 2026

2048 0 0000000000 0 Jan 01, 2026

2057 9 0000001001 9 Dec 23, 2025

2057 9 0000001001 9 Dec 23, 2025

2059 11 0000001011 11 Dec 21, 2025

2074 26 0000011010 26 Dec 06, 2025

2095 47 0000101111 47 Nov 15, 2025

2097 49 0000110001 49 Nov 13, 2025

2097 49 0000110001 49 Nov 13, 2025

2106 58 0000111010 58 Nov 04, 2025

2107 59 0000111011 59 Nov 03, 2025

2137 89 0001011001 89 Oct 04, 2025

2150 102 0001100110 102 Sep 21, 2025

2156 108 0001101100 108 Sep 15, 2025

2190 142 0010001110 142 Aug 12, 2025

2253 205 0011001101 205 Jun 10, 2025

2367 319 0100111111 319 Feb 16, 2025

2458 410 0110011010 410 Nov 17, 2024

Notice that users who got an error message of >=2048 would have already received a legitimate service due message on or before Jan 1, 2026.
As one of the 2097’s I didn’t receive a reminder in Nov 2025
 
At this stage I have no alert West Oz based base model specced up wagon '23 build.
A third person joins the elite class of no service overdue alert.

Two from Australia and 1 from Belgium.
 
Last edited:
Back
Top Bottom