Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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 : Year 2000 - Urban Legends -- Ignore unavailable to you. Want to Upgrade?

To: Sawtooth who wrote (7)	12/23/1998 5:04:00 PM
From: J.L. Turner	Read Replies (1) \| Respond to of 31

Hi Tim, This is the best response on cars and y2k that I have seen.Doesn't seem to be a significant problem.Sorry I don't remember the source. It is very important to understand the nature of embedded chips in automobiles. The instances in which one might have a y2k problem are very few and far between. The reasoning here is based upon the role these chips are playing in the car. Most of the embedded systems with real time clocks are used for synchronization and integral monitoring of conditions over time. In these cases, the actual date the embedded system's calendar thinks it is becomes irrelevant. The chip has some epoch date burned onto the chip as a starting date. This date may be the date of design, manufacture or installation. The, whenever the ignition is engaged, the chip is ticking off seconds and moving the date forward. When the ignition is not engaged, the chip is dormant. As a result, the chip itself may have a y2k date problem, but the calendar isn't moving forward at a rate anywhere near 1 digital day per calendar day. In this scenario, there will be little or no problem. There is the case in which computers keep track of service times of the vehicle and warn the user when it's time to go get your car fixed. In most cars, this will result in a "dummy light" on your dash board turning on or an annoying "bing" sound like the door-ajar sound. I know this because my friends Toyota Pickup has this problem. The chip thinks it's the wrong date and he is late for service and so it "bings" all day. Annoying? Yes. Drivable? Yes. There have been very few realistic scenarios in which a car would not operate correctly because of date, WITH ONE VERY IMPORTANT NUANCE: If your car has embedded systems which keep real dates (ie the clock is ticking when the car ain't running), then the moment of rollover from 31 Dec 1999 to 01 Jan 2000 can cause the computer to fail with unpredictable results. If you dished out less than $30K for your car, I would personally not fret about it as you are not into the high-end of cars that have these super fancy braking systems, suspensions systems, climate control systems, etc, which closely monitor conditions over time and respond accordingly. So, with many words, the summary should be - call your dealer and listen to their lawyer approved innoculous song and dance, then, if you have a newer model car, don't drive it from 23:59:59 of 31 Dec 1999 to 00:00:01 of 01 Jan 2000, and chances are very good that everything will be just fine. J.L.T.