Usenet 1994 January/usenetsourcesnewsgroupsinfomagicjanuary1994.iso/answers/realtime-computing/faq

Text File | 1993-09-13 | 12.5 KB | 301 lines

Newsgroups: comp.realtime,news.answers,comp.answers
Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!usc!cs.utexas.edu!chinacat!nominil!linimon
From: [e-mail] (Mark Linimon)
Subject: Comp.realtime: Frequently Asked Questions (FAQs)
References: <[e-mail]>
Followup-To: poster
Approved: [e-mail]
Organization: Lonesome Dove Computing Services
Date: Mon, 13 Sep 1993 07:10:15 GMT
Supersedes: <[e-mail]>
Message-ID: <[e-mail]>
Summary: Answers to real-time frequently asked questions (periodic posting)
Expires: Mon, 25 Oct 1993 07:09:48 GMT
X-Posting-Frequency: every 4 weeks
Reply-To: [e-mail]
Lines: 282
Xref: senator-bedfellow.mit.edu comp.realtime:4538 news.answers:12419 comp.answers:1950

Archive-name: realtime-computing/faq
Version: 1.09 (September 1993)
Last-Modified: Sat Sep  4 18:43:44 EDT 1993

This posting provides an overview of newsgroup comp.realtime by summarizing
the history, common past topics, and frequently asked questions.

A companion posting to this one, "Comp.realtime: Welcome to comp.realtime"
<[e-mail]>, complements this
one by providing a concise introduction to the group.  Another posting,
"Comp.realtime: A list of real-time operating systems and tools",
<[e-mail]>, provides references to
available operating systems and software tools.

These articles are repeated periodically for the benefit of new readers.

[Editorial comments may be found in brackets.]

[This FAQ is still somewhat preliminary, based on a couple of years of
saved-off postings scattered here and there.  Further contributions
are welcomed, see below.]

----------------------------------------------------------------------

Subject: table of contents

    Subject: What is the charter of comp.realtime?
    Subject: What is considered good net.etiquette on comp.realtime?
    Subject: What exactly is meant by real-time?
    Subject: Where should I ask questions about real-time systems?
    Subject: What other net.resources are available on real-time systems?
    Subject: What are some references to the theory and practice?
    Subject: Contributions to comp.realtime FAQs.

------------------------------

Subject: What is the charter of comp.realtime?

The charter of comp.realtime is to provide a forum for discussion of both
the theory and practice of real-time computer systems.  The group is
unmoderated; participation is open to all.

[If there was a formal charter for the newsgroup at the time of its
creation, we don't have access to it at the moment.  Readers?]

Note that the listing in the canonical "newsgroups" file is:

comp.realtime    Issues related to real-time computing.

------------------------------

Subject: What is considered good net.etiquette on comp.realtime?

Here are some etiquette reminders that will help us all to make the group
an ever-friendlier place:

-- Please, before posting, ensure that you've read the basic Usenet
   etiquette guide in news.announce.newusers.

-- Please set the Followup-To: line in your post.  This is especially
   true if you are cross-posting.  If you are requesting information,
   consider setting Followup-To: poster, and then summarizing the replies
   to the net.

-- When following up, please change the Subject: line if the subject has
   really changed.

-- Some sites that receive comp.realtime are on branches of the net that
   frown on overtly commercial announcements.  These postings are welcomed
   on comp.newprod and anywhere in the biz.* hierarchy.  However, short
   offers by vendors to provide further information by email are usually
   seen as acceptable.

------------------------------

Subject: What exactly is meant by real-time?

The definition of a real-time system (as it has been published many times,
so I don't know the original author) is the following:

"A real-time system is one in which the correctness of the computations not
only depends upon the logical correctness of the computation but also upon
the time at which the result is produced. If the timing constraints of the
system are not met, system failure is said to have occurred.  Hence, it is
essential that the timing constraints of the system are guaranteed to be
met.  Guaranteeing timing behavior requires that the system be predictable.
It is also desirable that the system attain a high degree of utilization
while satisfying the timing constraints of the system."

A good example is a robot that has to pick up something from a conveyor
belt.  The piece is moving, and the robot has a small window to pick up
the object.  If the robot is late, the piece won't be there anymore,
and thus the job will have been done incorrectly, even though the robot
went to the right place.

Another example is the servo loops in an airplane when on auto-pilot.
The sensors of the plane must continuously supply the control computer
with proper measurements.  If a measurement is missed, the performance
of the airplane can degrade, sometimes to unacceptable levels.

One will occasionally see references to "real-time" systems when what is
is meant is "on-line", or "an interactive system with better response time
than we used to have".  Often, this is just marketing hype.  For instance,
although some have queried whether running "rn" is real-time, it is not, as
it is interacting with a human who can tolerate hundreds of milliseconds of
delays without a problem.  Similarly, on-line stock quotation systems
interact with humans.

One will also occasionally see discussions of "soft" vs. "hard" real-time
systems.  In many of these discussions, "hard" real-time means the type
of real-time system discussed above, and "soft" real-time means systems
which have reduced constraints on "lateness" but still must operate
very quickly and repeatably.  However, the definition is controversial,
as some mean by "hard" and "soft" the degree of time constraints.  For
instance, a real-time process attempting to recognize images may have
only a few hundred microseconds in which to resolve each image, but a
process that attempts to position a servo-motor may have tens of milli-
seconds in which to process its data.

Unfortunately the topic is controversial, and there doesn't seem to be
100% agreement over the terminology.

------------------------------

Subject: Where should I ask questions about real-time systems?

Comp.relatime is certainly the place.  However,  if you are asking about a
particular real-time system, see below for a (possibly) better place to start.

For topics that are only somewhat related to real-time systems, also consider
comp.arch and/or comp.os.misc.  For instance, topics about bus-based computer
systems are best asked in comp.arch, or, if they're about the VMEbus,
comp.arch.bus.vmebus.

------------------------------

Subject: What other net.resources are available on real-time systems?

There are at least two other newsgroups devoted exclusively to a particular
vendor's real-time operating system:

comp.os.os9        Discussions about the os9 operating system.
comp.os.vxworks         The VxWorks real-time operating system.

Here are some other related newsgroups:

comp.arch        Computer architecture.
comp.arch.bus.vmebus    Hardware and software for VMEbus Systems.
comp.os.misc        General OS-oriented discussion not carried elsewhere.

There are too many other newsgroups devoted to computer operating systems
that support some form of real-time scheduling to list here.  The interested
reader is advised to check the "newsgroups" file on her or his local machine.

There is a realtime-related mailing list for embedded computer systems
developers.  It is not strictly real-time, but there is some overlap.
To subscribe, send your email address to [e-mail].

------------------------------

Subject: What are some references to the theory and practice?

Several people recommended as a starting place the article "Tutorial on
Hard Real-Time Systems", John A. Stankovic and Krithi Ramamritham, IEEE
Computer Society reprint series, Computer Society order number 819.

Here are some other suggestions from various net.sources, in no order:

@inproceedings{Mok:PRTS84,
author = {A. K. Mok},
title = {The Design of Real-time Programming Systems Based on Process Models},
booktitle = {Proc. 1984 Real-Time Systems Symposium},
month = {Dec.},
year = {1984},
pages = {5-17}
}

@article{Kligerman:TOSE86,
    author =    {E. Kligerman and A. Stoyenko},
    year =      {1986},
    journal =   TOSE,
    month =     {Sep.},
    number =    {9},
    pages =     {941-949},
    title =     {Real-Time Euclid: A Language for Reliable Real-Time Systems},
    volume =    {SE-12}
}

@book{Stoyenko:Diss,
        author =        {A. Stoyenko},
        title =         {A Real-Time Language With A Schedulability Analyzer},
        address =       {Computer Systems Research Institute,
            University of Toronto},
        publisher =     {Dissertation},
        month =         {Dec.},
        year =          {1987}
}

@article{Leinbaugh:TOSE86,
    author =        {D. W. Leinbaugh and M.-R. Yamini},
    year =          {1986},
    journal =       TOSE,
    month =         {Dec.},
    number =        {12},
    pages =         {},
    volume =        {SE-12},
    title =         {Guaranteed Response Times in a Distributed
                    Hard-Real-Time Environment}
}

@article{Kopetz:MICRO89,
        author =        {H. Kopetz and A. Damm and Ch. Koza and M. Mulazzani
                         and W. Schwabl and Ch. Senft and R. Zainlinger},
        title =         {Distributed Fault-Tolerant Real-Time Systems:
                The {MARS} {A}pproach},
        journal =       {IEEE Micro}
        volume =        {9},
        number =        {1},
        year =          {1989},
        month =         {Feb.},
        pages =         {25-40}
}

Caxton Foster's "Real-Time Programming: Neglected Topics," despite the
title, is a very good introduction to the basic topics of real-time control,
starting with simple things like interrupts and debouncing switches, all the
way through digital filters.  It's a thin paperback (Addison Wesley MicroBooks),
and a (somewhat) experienced programmer can get through it in a couple of days.

Vickery, C.  Real-Time and Systems Programming for PCs.  New York: McGraw-Hill,
    1993.  604 pp.
    The thesis is that the development environment for real-time systems
    is ideal for studying systems programming, too.  After some introductory
    material, the book deals exclusively with Intel's iRMX operating
    systems, with particular emphasis on iRMX for Windows.

iRUG.  Proceedings of the Intel Real-Time User's Group. Annual, back copies
    available from iRUG, P.O. Box 91130, Portland, OR 97291, [phone].
    Annual conference proceedings dealing primarily with Intel's family
    of real-time OSs, iRMX.

Lawrence, P. D. and Mauch, K.  Real-Time Microcomputer System Design.  New York:
    McGraw-Hill, 1987.  568 pp.
    The emphasis is on the design of I/O circuits and assembly language
    interfaces for small microprocessors used for embedded systems.

Mellichamp, D. A.  Real-Time Computing.  New York: Van Nostrand Reinhold, 1983.
    552 pp.
    Twenty chapters by 11 authors on topics ranging from signal processing
    to managing real-time computing facilities.

Burns, A. and Wellings, A.  Real-Time Systems and Their Programming Languages.
    Wokingham: Addison-Wesley, 1990.  575 pp.
    Ada, Modula-2, and occam 2 are used throughout the book, which covers
    topics ranging from basic programming techniques, fault tolerance,
    exception handling, concurrency, resource management, and distributed
    designs.

------------------------------

Subject: Contributions to comp.realtime FAQs.

The following net.folks, among others, have contributed to this posting:

    A. Lester Buck <[e-mail]>
    Tim Chambers <[e-mail]>
    Chuck Cox <[e-mail]>
    David Hansen <[e-mail]>
    David B. Stewart <[e-mail]>
    Alexander Vrchoticky <[e-mail]>
    Christopher Vickery <[e-mail]>

I welcome reactions, additions, and corrections to this posting via email
at [e-mail].
--
    Mark Linimon / Lonesome Dove Computing Services / Roanoke, Virginia
   {chinacat,uunet}!nominil!linimon   ||    [e-mail]
--
    Mark Linimon / Lonesome Dove Computing Services / Roanoke, Virginia
   {chinacat,uunet}!nominil!linimon   ||    [e-mail]
         "It's a small town, son, may I ask what you're doing here?"
I am coming to believe that Netnews is the digital equivalent of junk food...