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

Its exactly 6 years out from my service date (1995 days) (as if the date were 01.01.2032 but the cxar clearly shows 01.01.2026 in system time)

Guess we will know if it is AU only when the Europeans come online and take their Grenadiers for a drive.
 
The first number to repeat, the same number of days as my car: 1968

Still only affecting cars with AU firmware.
probably because we were close to first into the new year. Let’s see what happens in a few hours when Europe and the uk wake up
 
probably because we were close to first into the new year. Let’s see what happens in a few hours when Europe and the uk wake up
Maybe, but some of us are 3 hours ahead of you in Perth. We are already 16 hours into 1 January.
 
Also got the bug.
2057 days overdue.
Only had it since new from may 25 with 0023km on clock.
I know Ineos did long term testing on mechanical but obviously not on computer systems.
 

Attachments

  • 20260101_125250.jpg
    20260101_125250.jpg
    4.5 MB · Views: 7
Also got the bug.
2057 days overdue.
Only had it since new from may 25 with 0023km on clock.
I know Ineos did long term testing on mechanical but obviously not on computer systems.
Ineos needs to re-test every line of code that the developer of the service date bug wrote and then have him/her dispatched with prejudice, and then fire their testing team and test manager.

I sold my software company after 32 years back in 2019 so have a special place "in my heart" for software devs...
 
Its exactly 6 years out from my service date (1995 days) (as if the date were 01.01.2032 but the cxar clearly shows 01.01.2026 in system time)

Guess we will know if it is AU only when the Europeans come online and take their Grenadiers for a drive.
They should be waking up about now
 
I have reset my current date back to 31/12/25, now waiting 30mins and will see what happens. If this works I will then reset the date back to 1/1/26 manually avoiding the automatic tick over of midnight. If the current test (to be checked after 30mins fails) I will set the date back a couple of days and let it midnight tick over to a new day in 2025 to see if the service interval bug clears and if so then perform a manual date reste to the current day in 2026. My major concern is that this must a bug in the library of functions used for the firmware as there is no need to have different code for calculating the service due date after a year tick over - my service due date has calculated correctly for the last couple of years. The firmware must have code that resets at midnight that has corrupted a system date which has then defaulted to a manufacture date.
 
Setting the date back to 31/12/25 and turning the car off for 30mins does clear the error.....until you set the date back to Auto and bingo you are overdue. This means that a hack of setting the dates back to clear the error does not work. My next test is to set the car back to 25/12/25 and let it clock over a day overnight and then manually set the date to the correct date tomorrow. If this fails then we are likely looking at a firmware update. Perhaps we should all take our cars back to Ineos HQ in Australia on the same day.
 
1931 days overdue. 😠
EU firmware, latest software update September 25
Ok so not just Australia. What a monumental f**k up. Perhaps they can fix a few other firmware bugs while they are at it like allowing us to reset the service interval.
 
Back
Top Bottom