When I got in my truck after New Year’s, it actually had the correct date of 2026 January 1. Is that other people are seeing? I tried moving and head by one day thing that might affect it but it didn’t.
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.
I'm still laughing my ass off at your reply. It is so on point for SJ, and hilarious visualizing him throwing a Grenadier at somebody.
I’m really enjoying reading your analysis of the issue, although I prefer the original phrase “champing at the bit” over your modern corruption “chomping at the bit”. And are we taking bits or bytes?
It'll be this when our OMG service reminder disaster is resolvedI’m really enjoying reading your analysis of the issue, although I prefer the original phrase “champing at the bit” over your modern corruption “chomping at the bit”. And are we taking bits or bytes?
To calculate the actual date the next service is due, don’t we first need to determine the date of our previous reset (using your column 3 and going back that many days) and then add 12 months to that?
. . .
I started the vehicle and found my (automatically set) clock showed the correct date. I set it to manual and wrote date data for year = 2027, then wrote it again with the current correct date (I assume it was written since I backed out of the menu each time). I locked the doors, waited 90 minutes, the unlocked the doors and started the vehicle. The service overdue message was displayed with the same expected value. I set the date / time back to auto and the error message was still displayed.
It's only corruption if I know it is and I intended it. I thought it was chomping. But we have a new rescue dog with some Frank Sinatra teeth, so maybe I'm channeling him? My mother is a Brit BTW, and we lived in DE and the UK for 9 years total so I should know better. But look at those teeth!I’m really enjoying reading your analysis of the issue, although I prefer the original phrase “champing at the bit” over your modern corruption “chomping at the bit”. And are we taking bits or bytes?
Only 2 bottles?
The 2054d mine displays is 5 years of days plus the distance from 21 May 2025 to today. I was 140 or 141 days past my last reset, plus the 5 years of days (incl leap days) that were inadvertently added on 1 Jan 2026.
I would argue that corruption, both in terms of linguistics and data, can be accidental, but out of a strong desire for self-preservation, I won’t argue with your dog.
But doesn’t your table show me as due on March 6 ?
He is a miscreant to the max. I find one of my shoes in the living room, my underwear on the deck, my eye drops container in 20 pieces in the kitchen. Love his spirit and craziness.I would argue that corruption, both in terms of linguistics and data, can be accidental, but out of a strong desire for self-preservation, I won’t argue with your dog.
I haven't posted any tables. I think that's someone else. I wrote a Tcl script that takes the date you read your days of service overdue, and the number of days overdue, and calculates your last service reset date in Eastern time zone.
My mistake. The table I was looking at (on page 25) was posted by @Glen in response to one of your posts. I’ll get him to check it. All the best to you (and your dog).
I tried the above method with the engine on confirm to be not working. I'll try now with the engine off.
Thanks for confirming. No sense in others doing this. I think dealer service reset must be done.
I don't know, members complaining because they haven't got a fault. We seemed to have turned the out come of the forum upside down
. We could start threads help " there is nothing wrong with my Grenadier"
and I have the issue. )
not.
