I'm wondering whether this issue is actually based on data that is onboard.
I tried changing my Date to actual current date and to a date in the past, and it had no impact on my "overdue" days. Is it possible that the service due information is somehow kept offline?
I suspect that changing the date manually in the console to be the real date today, and turning off the vehicle, locking the doors, waiting some time, I don't think that will fix this issue, but it's worth trying. You did this and it didn't fix the issue.
I'm confident that this is based on data that is on board, in the ECU most likely. The date/time might be fed in from outside, via the GPS unit perhaps. The center console is a separate unit, and there are other computers in the vehicle, they all get information from and send data to the ECU over the CANbus, a vehicle 'ethernet' network if you like. Think about how Teslas are updated over the internet, but for this vehicle, you have to visit a dealer to get updates to software, to reset things, or you yourself have to plug in a USB drive to the car for it to see an update and then load it when you tell it to. So it is very unlikely that there is any data or comms happening between the vehicle and the 'cloud' or back to INEOS, the only input from outside in a network sense is coming as input-only from the GPS sensor, no data is going out from the Grenadier over the airwaves or internet. Well, unless you have a tracker planted in your car.
It is possible that an erroneous input from GPS that fed a date in 2032 to vehicle systems caused this, and that GPS now giving correct dates can't undo it.
Things in an ECU and other computing components in a vehicle are simpler than you'd see on a PC or Mac or even a mobile phone, space is limited, memory is limited, I've seen this in software written for space vehicles -- a lot of constraints.
To determine if service is due, there is either a computation done within the ECU that compares the last service reset or date, with today's date, or there is a simple memory location that acts as a counter, and increments by 1 each day, and that another part of the code reads and an 'if' statement that says: "if COUNTER is > 365, tell console to display COUNTER - 365 days overdue for service". Could be other ways to do this.
I'm betting on the latter, as date adding and subtracting is tricky, and a counter that can be reset to 0 and count up by 1 daily is much, much simpler for the purpose of determining how many days since your vehicle service has been done (and service counter reset).
The days overdue for service increments at 1800 Eastern time, which is UTC+1 midnight time (most of the EU, incl. France), and the ECU I think updates the counter by 1 at that time. It's possible that the ECU will take the new date at that time and calculate the difference between it and the service reset date, and increment the service counter by that many days, but that seems unlikely as it's more complication than needed to do this function. Still, maybe there are vehicles that they expect may be de-powered for long periods, maybe in shipping, and they coded it to take the date from GPS and do those calculations.
Having said that, this is all speculation based on experience with embedded systems, but not any knowledge or experience with the internals of the Grenadier's systems. I am chomping at the bit to get access to the embedded systems architecture and software, I'd even sign an NDA if necessary, to understand what happened in this case and help improve these systems. The Grenadier platform is brilliant, and I think it should be stuck with mostly, with changes coming as fixes, improvements, iterating evolution, not start over or make huge changes like you see with between the 5th and 6th gen 4Runners, but you didn't see between 4th and 5th gen.
My best guess is that 5 year's worth of days was added to the internal ECU time and it incremented the service counter by that many days. Could have been that a date in 2032 was provided to the ECU, could be that something jumped that Service counter by that many days, no idea.
Whether changing the date manually in the console and having the ECU pick up on that and then adjust the service counter, I don't know -- I hope so, would then be easy to fix this.
I trust IA engineers are working this, and we'll hear relatively soon what happened and what to do about it.
I wonder how bound IA is to proprietary hardware and software that is limiting and constraining what they can do. Engine management and other systems, would be nice to have open source alternatives.
/s.
'
