..year 2023 'problem'..

[Ecc0]

..im sorry, year should be 2028, not 2023 as i stated in thread....i just had some talkie from some folks in industry, and during discussion of how to solve some software problems, we came across issues, described herehttp://en.wikipedia.org/wiki/Year_2038_problem..so, to cut it short, why is that important for cars?? Well, to make it all cheaper, embedded systems as well as modern vehicles, using 8bit, 16bit and if really 'advanced' 32 bit data scheme. And thats the problem, because system clock based on those data sets will 'reset' itself, and thats going to be a bit problematic, depending on corresponding software system is rigged on. Vulnerable systemsEmbedded systems are most likely to be affected by the 2038 bug. Telecommunication systems and transportation systems from flight to automobiles increasingly use embedded systems. Automobiles, electric vehicles, and hybrid vehicles are increasingly using embedded systems to maximize efficiency and reduce pollution. Other automotive safety systems include anti-lock braking system (ABS), electronic stability control (ESC/ESP), traction control (TCS) and automatic four-wheel drive. New aircraft contain advanced avionics such as inertial guidance systems and GPS receivers that also have considerable safety requirements. Another major use of embedded systems is in communications devices, including cell phones and Internet appliances (routers, wireless access points, etc.) which rely on storing an accurate time and date and are increasingly based on UNIX-like operating systems.As of 2011, most embedded systems use 8-bit or 16-bit microprocessors, even as desktop systems are transitioning to 64-bit systems. Despite the modern 18–24-month generational update in computer systems technology, embedded systems are designed to last the lifetime of the machine in which they are a component. It is conceivable that some of these systems may still be in use in 2038. It may be impractical or, in some cases, impossible to upgrade the software running these systems, ultimately requiring replacement if 32-bit time_t limitations are to be corrected.The use of 32-bit time_t has also been encoded into some file formats[citation needed], which means it can live on well beyond the life of the machines on which such file formats were originally supported.

 

[BlackCat]

Intresting! I shall dwell and read more on the subject...

Thanks for sharing this!

 

[ramsing]

hmmm...reminds me of the Y2K scare. hype created, companies offer solution, customers pays, but in the end nothing happens. hahaha.

 

[Ecc0]

yeah..this depends how software is written, because ABS and DSC for instance, are heavily time dependable features..if system is based on real time clock of given processor and you are about to use brakes when thing start reseting itself in the loop (or stuck, and need manual reset , depending on software), it can be rather dangerous..i believe these kind of things were 'thought out' by software designers at BMW, in advance, but again..you never know

 

[erica34]

just like y2k, probably just take leave on the day, watch tele and wait/watch for news of crashing cars in NZ and Australia.

 

[haywire]

So which year is it? Your title says 2023, your correction note says 2028 and your quoted article says 2038.

Dont worry so much, a planet is coming to crash earth end of this year, the world is gonna end anyway so the car software bug wont be allowed to happen.

 

[seewai]

I guess we could overcome date/time issues by leaving out the "year factor" in all software calculations in our cars. Make the "year" display as a "text only". Less bits required, headache free and can be used for centuries to come.

Just like some of our watches, only display month and day, no year.