Archives
 
 
 
  Special
 
 
 
  About Us
 
 
 

Newsletter
Free E-mail Newsletter from BYTE.com

 
    
           
Visit the home page Browse the four-year online archive Download platform-neutral CPU/FPU benchmarks Find information for advertisers, authors, vendors, subscribers Request free information on products written about or advertised in BYTE Submit a press release, or scan recent announcements Talk with BYTE's staff and readers about products and technologies

ArticlesThe Enemy Within


September 1997 / International Bits / The Enemy Within

Embedded systems may cause another year 2000 problem.

Geoff Lock

If your year 2000 plan seems to be on target, check again. Microprocessors in security systems, production control systems, or health-care equipment may crash systems when the year rolls over from 1999 to 2000.

At a hardware level, some microcontrollers count years in a single 8-bit register, referencing the year in just the last two digits. However, the problem is not restricted to 8-bit microprocessors. Much more threatening is the possibility that programmers of control software assumed that 8-bit or two-character years will be sufficient, whether or not hardware had offered greater precisio n. "It's been common practice when developing programs [for embedded systems] not to waste space on luxuri es like the century," says David Brook, an applications engineer for Motorola in the U.K.

Many systems will function without a problem, but how do you know which are afflicted? "For any system, even if the microcontroller hardware handles the date adequately or not at all, and the microcontroller's program handles the date adequately, there may still be a risk if systems are synchronized by a Supervisory Control and Data Acquisition (SCADA) program," says Clive Watts, product marketing manager at Arcom Control Systems (Cambridge, U.K.).

There is no way of guessing whether an embedded system will be OK, based on manufacturer, type, size, or age. If a system has no known date reliance and is not connected to anything else, it may be OK; but if it is a critical component, the only way to be sure is to check the code.

Only a few companies have acknowledged that there are problems with their embedded systems. Shell Exploration in the U.K., for example, is cu rrently replacing or upgrading systems in all critical areas. Says Stuart Officer, asset integrity manager with Shell Exploration, "It's like looking for a needle in a haystack. We won't leave anything to chance. If a vendor has gone out of business, we will replace the system."

The electronics industry has been quiet, and several chip suppliers believe it is not their problem. However, some vendors such as Mitsubishi Electronics are starting to address the issue in the trade press. Motorola's Brook is well aware of the problem but says "it is caused by custom-made software running on the chips."

One reason why the problem has kept such a low profile may be that many companies are often not aware where in their enterprise they use embedded systems. In addition, users recognize embedded systems only when they fail.


How to Address Year 2000 Problems in Embedded Systems


If the microprocessor cannot cope with the problem
, the only option
is to replace
 it completely. This may be realistic for an
air-conditioning unit but is less so for an oil refinery. As a
consequence, you may need to examine complete process units.


If the control program cannot handle the problem
 and you can locate
the vendor, there is a good chance that you can upgrade the program.
If you cannot find the vendor or program source, replacement is
required.


If the problem comes from a third party
, for instance a SCADA system
running a production line, you must check the complete control system.


Make sure the systems you don't want to replace are not critical
 to
your business and don't forget to test changes and upgrades.



Up to the International Bits section contentsGo to next article: What's in a Name?SearchSend a comment on this articleSubscribe to BYTE or BYTE on CD-ROM  
Flexible C++
Matthew Wilson
My approach to software engineering is far more pragmatic than it is theoretical--and no language better exemplifies this than C++.

more...

BYTE Digest

BYTE Digest editors every month analyze and evaluate the best articles from Information Week, EE Times, Dr. Dobb's Journal, Network Computing, Sys Admin, and dozens of other CMP publications—bringing you critical news and information about wireless communication, computer security, software development, embedded systems, and more!

Find out more

BYTE.com Store

BYTE CD-ROM
NOW, on one CD-ROM, you can instantly access more than 8 years of BYTE.
 
The Best of BYTE Volume 1: Programming Languages
The Best of BYTE
Volume 1: Programming Languages
In this issue of Best of BYTE, we bring together some of the leading programming language designers and implementors...

Copyright © 2005 CMP Media LLC, Privacy Policy, Your California Privacy rights, Terms of Service
Site comments: webmaster@byte.com
SDMG Web Sites: BYTE.com, C/C++ Users Journal, Dr. Dobb's Journal, MSDN Magazine, New Architect, SD Expo, SD Magazine, Sys Admin, The Perl Journal, UnixReview.com, Windows Developer Network