Same problem here.
1968
1968
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.
The first number to repeat, the same number of days as my car: 1968Same problem here.
1968
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 upThe first number to repeat, the same number of days as my car: 1968
Still only affecting cars with AU firmware.
Maybe, but some of us are 3 hours ahead of you in Perth. We are already 16 hours into 1 January.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
Yes but it’s 5am in the UK ATM. And just turned midnight in New York.Maybe, but some of us are 3 hours ahead of you in Perth. We are already 16 hours into 1 January.
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.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.
They should be waking up about nowIts 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.
All of a sudden, having owners being able to reset their own service interval, seems like a better idea.It might sort itself at Chinese new year?![]()