Viewing page 3 of 47

This transcription has been completed. Contact us with corrections.

Steve Carnes, 6:25 AM 1/4/9...,Your report                                                            1

Received: by macvax.UCSD.EDU (5.57/UCSDGENERIC.4)
        id AA22869 to ride; Wed, 4 Jan 95 06:19:49 -0800
X-Sender: scarnes@128.54.27.128
Message-Id: 
Mime-Version: 1.0
Content-Type: text/plain; charset-"us-ascii"
Date: Wed, 4 Jan 1995 06:25:08 -0800
To: ride@macvax.ucsd.edu, wiskerchen@eureka.ucsd.edu
From: scarnes@ucsd.edu (Steve Carnes)
Subject: Your report
Cc: mbaine@ucsd.edu

Dr. Ride and Dr. Wiskerchen,

FYI, here's an email I received from Steve Wall today.

1) Do you have a specific response to this?

2) Do you know who "Barbara and Al" are?

3) Do we still want a debrief on 13 Jan? (I say yes, to share the info 
while our memories are still fresh) I don't know if Steve Wall is 
referring to Mike Baine or Mike Wiskerchen when he says "Mike C." Do you?

Today we're going to spend time on one of the new MCC consoles. We also 
plan to meet with the KidSat PIM, Sharon Castle. This afternoon we're 
going to capture some images from one of Phyllis Ground's older ESC's onto 
floppy disk and also try to send the files to CalSpace via the internet. 
Tomorrow we're going back to the KCA group for another look and to ask some 
more questions.

Let us know if there is anything else you want done.

-Steve


>From: Stephen.D.Wall@jpl.nasa.gov
>Date: 03 Jan 95 15:23:00 -4544
>To: scarnes@ucsd.edu
>Cc: Jo.BEA.Way@jpl.nasa.gov, rreed@bithound.jpl.nasa.gov
>Subject: Your report
>
>Steve-
>
>Some notes on your 12/30 report follow. By the way, please put
>rreed@bithound.jpl.nasa.gov
>on your mailing list, and, if you haven's change my email to
>Stephen.D.Wall@jpl.nasa.gov.
>
>1. We investigated the KCA for our two flights in 1994, and while I agree that
>it is a neat solution to a lot of problems, you must be careful here. As long
>as the KCA is the KCA (that is, a piece of "test objective", or "DTO", 
>hardware), you will find the Flight Directors not so anxious for you to use it.
>This is because as a DTO it will have its own opportunity to impose
>requirements
>on the flight, which complicates things (and, by the way, is not in Kidsat's
>interest either). We wanted to use it until JSC management told us (very late
>in the integration process) that they weren't going to let it fly. The higher
>we tried to take the issue the more resistance we ran into, and we finally gave
>up. Don't pin your experiment on it unless and until you get a Flight Director
>assigned and he says he will accept it!!!
>

Printed for sride@ucsd.edu (Sally K. Ride)                                                            1