SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Discuss Year 2000 Issues -- Ignore unavailable to you. Want to Upgrade?


To: Richard Babusek who wrote (1058)2/11/1998 5:12:00 AM
From: C.K. Houston  Respond to of 9818
 
Ricardo,

Check out this thread: "Year 2000: Embedded Systems & Infrastructure Problem".
Subject 18990

Click on "CK HOUSTON's Embedded Systems Index. You'll find what you need to know there. The "Technical" section may be of most interest to you. But, you should probably also check out the "Problems & Failures" section to get a good overview of some of the problems different industries are having.

Cheryl



To: Richard Babusek who wrote (1058)2/11/1998 10:41:00 PM
From: David Eddy  Respond to of 9818
 
Richard -

Most process control systems I'm aware of have no notion of "year" as such

But the problem here is that as the architect you viewed the system from 50,000'. Did you monitor the folks as they wrote the code that went into the chips that went into the machines in your systems?

While I haven't looked into any chip code, I'd be willing to bet hard money that they provide a bunch of time functions that very likely produce a number string looking something like yymmddhhsstthhkk, where
yy is year
mm is month
dd is day
hh is hour
ss is second
tt is tenths of seconds
hh is hundredths
kk is thousands

Depending on how the code was written (you won't know unless you test), when that year flips from 99 to 00, the following mathematical operations could get quite confused if way out of range or negative.

- David