3 ms·
I'm with you on this, and that would explain the bug if Honda hadn't said the code will return to its correct output in August.
by kingcharles 5y ago
I'm with you on this, and that would explain the bug if Honda hadn't said the code will return to its correct output in August.
- rightbyte 5y agoYe I was figuring which algorithms might give that bug behaviour but I could not think of any. Maybe they have a "Y since X", hit the Autosar reserved range at 0xfd..., and it wraps around 0xff... to 0 in August? A free running counter through the "non physical" range is the only thing I could think of that would behave like this and fix it self by a date. The timer could be any bit width or unit really.