Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!spool.mu.edu!news.cs.indiana.edu!ariel.unm.edu!pprg.unm.edu!topgun!mustang!nntp-server.caltech.edu!iago.caltech.edu!carl
From: carl@iago.caltech.edu (Lydick, Carl)
Newsgroups: sci.space.shuttle
Subject: Re: Mission Control Reports #13 - 14 (6/11/91)
Message-ID: <1991Jun14.074535.22050@nntp-server.caltech.edu>
Date: 14 Jun 91 06:44:44 GMT
Article-I.D.: nntp-ser.1991Jun14.074535.22050
References: <1991Jun14.045132.4950@rs6000.cmp.ilstu.edu>
Sender: news@nntp-server.caltech.edu
Reply-To: carl@iago.caltech.edu
Organization: California Institute of Technology
Lines: 18
News-Software: VAX/VMS VNEWS 1.3-4x

In article <1991Jun14.045132.4950@rs6000.cmp.ilstu.edu>, ejbehr@rs6000.cmp.ilstu.edu (Eric Behr) writes...
>CAPCOM Kathy Thornton told the crew that ground flight 
>controllers had seen a second link error in the Spacelab 
>Experiment Computer Operating System (ECOS). The 
>computer experienced its first link error on flight day four 
>(Sat., June 6). A trouble shooting procedure was performed and 
>the computer was recovered within 10 minutes.

Just what is a "link error"?

>Commander Bryan O'Connor radioed to Mission Control that the
>crew apparently had traced the communication problem that the
>two payload specialists encountered yesterday to a faulty
>audio interface unit.

Is that a speaker or a microphone?
--------------------------------------------------------------------------------
Carl J Lydick	HEPnet/NSI: SOL1::CARL	Internet: CARL@SOL1.GPS.CALTECH.EDU