To: B.K.Myers who wrote (3263 ) 1/27/1999 4:07:00 PM From: B.K.Myers Respond to of 9818
When will embedded systems fail because of Y2K rollover problems? According to Embedded Systems and the Year 2000 Problem, written by Mark A. Frautschi, Ph.D, “most of their failures will occur after 1 January 2000.” He further states, “One manufacturer has released documentation to its customers that some of their systems will not fail until 2006.” "In the case where no external agent sets the date, the system defaults to its "epoch" [10] date. This could be the design date, the date of manufacture, or some other, arbitrary, date. Non-compliant systems are subject to failure when the internal date reaches 1/1/2000, which in general will not be in step with actual time. There is no means, or need, to input actual time at the turn-on point. In general, such a system will reach 1/1/2000 internally after 1/1/2000 actually occurs. This is due to natural delays introduced by the production life cycle, shelf life and possibly the duty cycle (the fraction of the time the system is "powered up"). For non-Year-2000-compliant architectures, these delays increase the likelihood that most of their failures will occur after 1 January 2000. One manufacturer has released documentation to its customers that some of their systems will not fail until 2006. [11]"tmn.com I believe that this can be viewed as both good news and bad news. My biggest concern about the embedded systems problem is that they would all fail on 1/1/2000. This simultaneous failure would hamper efforts to repair the failed systems. However, according to this paper, 1/1/2000 will be the first day of the Y2K rollover failures. Embedded systems will continue to fail over the course of several years. The good news is that embedded systems with a Y2K problem will not all fail on the same day (1/1/2000). The bad news is that the Y2K embedded system problem will be with us for a long time to come. Any other opinions as to whether this is good or bad news?