printer friendly version

What is an embedded system?

Dear Editor,

One of the simplest definitions of an embedded system as described by Open Systems Publishing, a US international leading embedded systems magazine, is a computer without the traditional desktop keyboard and display. Users can interface through keypad, alphanumeric display, serial interface RS232 or through an Ethernet port. In essence, any standalone system not used for regular day-to-day PC requirements can be classed as an embedded system.

In an embedded system there is also no standard embedded operating system - ie an embedded system can use any operating system. The aim is to keep the software as simple as possible to avoid complications and therefore the system failing. Since many embedded systems are built with standard off-the-shelf hardware, uniqueness is through custom-built application software. This is typically written in either C or C++ format! The same as Microsoft Windows.

The platforms used by most operating systems is MS-DOS - Microsoft Disc Operating System. In some cases some developers use others such as Unix, Beos, GPX; in essence most of these base operating platforms use similar or the same kernel structures - the differences being in the built up C or C++ software on top of this platform, be it Windows or Linux or other proprietary software.

There is unfortunately a great deal of misinformation on Microsoft and the Windows Operating Systems. Remember that Windows 95, 98 and Millennium were built for home and SOHO (small office, home office) operation and not for high data rates and continuous long-term operation! Whereas Windows NT (new technology) platforms were designed for corporate and industrial applications. Therefore do not be surprised should your system fall over, that you are using the wrong system in the wrong environment. Likewise with the generations of development from NT4, to 2000 and now XP, each stage is infinitely more stable (look how many service packs NT4 needed).

But that is not all to consider. If your proprietary software has anomalies; such as poor data basing structures, restricted LAN/WAN links, or other issues then your embedded system may still have problems - ask the questions as you shop around.

Finally, remember that most systems use similar hardware. Hardware components are designed for a set period of life and as with most of today's products, have an average life expectancy; some fail within days. Repair and swap out are simple, but what you need to confirm is the quality of hardware components being used, what guarantees are in place, and how quickly a repair under warranty can be completed.

Unfortunately in the South African market there is a tendency to belittle the installer, system integrator or project manager, and assume that they will not understand - "give them a plug-and-play system and they will be alright". With the fast developing pace of software-based solutions in open architecture formats it is now a case of you must learn or you will die! There are very few simple applications and most will involve some degree of computer understanding - better that we as distributors EDUCATE rather than DISCRIMINATE.

Niall Beazley, Vision Catcher

011 465 6396

Share this article:

Further reading: