Anyone try just tapping on the guage?

[esozr]

Maybe the needle is just stuck...

[Buck]

On Sat, 16 Jul 2005 00:53:21 GMT, "esozr" > wrote:

>Maybe the needle is just stuck...
>

That's right it would be a good idea to strap in two astronauts in
that fuel tank with oxygen masks while the shuttle is lifting off. Of
course the tank burns up in the atmosphere when coming back down to
earth but it's better losing 2 astronauts than 7. I wonder if NASA
would consider this.

[esozr]

"Buck" wrote in message

> (gauge inside fuel tank)

What a silly place to put it...

[Joe Delphi]

"esozr" > wrote in message
. ..
> "Buck" wrote in message
>
> > (gauge inside fuel tank)
>
> What a silly place to put it...
>
>

That's because its not a fuel "gauge" its a fuel sensor. I noticed during
the past week that some of the media have used these two words
interchangeably when they should not. This is causing confusion.

The sensor merely tells the computer when to turn off the main engines,
there is no gauge for a human being to look at.


JD

[esozr]

> Maybe the needle is just stuck...

*sigh*

(This was meant to be a joke.)

[J]

"rk" > wrote in message
...
> esozr wrote:
>
> > Maybe the needle is just stuck...
>
> Yeah ... but with the upgrade to the glass cockpit, can't tap on it to
clear
> up the problem.

But maybe if the crew had stopped playing video games on the cockpit screens
they would've noticed the needle was stuck at E.

I think they should upgrade to a transparent ET so that fuel levels are
visible at all times.

Here's another good idea: replace mission control staff with home compter
users across the globe. Even casual 28.8 dialup users could monitor
critical systems. Holds could be built in to ascent timeline to allow users
to reboot or to OK error messages on their possibly dated homebuilt systems.

Speaking of which, for the current sensor problems, why didn't someone just
hit ctrl-alt-del onboard the orbiter? I assume it runs Win98?

If anyone at NASA is reading this, here's a secondary fix: go to Device
Manager>Fuel System>ET>Sensors. You should see four instances of Depletion
Sensor. Choose each and click Properties and then update the drivers. If
you need to do this quickly during launch, here's a shortcut,
WindowsKey+Pause brings up Device Manager, or DM. I realize DM has a few
billion entries, but come on, get some people on this!

Another hot tip: assign SRB sep to the quick launch toolbar.

[Disclaimer: reinstalling SSME drivers during ascent could adversly affect
acceleration].

[esozr]

"J" wrote in message

> But maybe if the crew had stopped playing video games on the cockpit
screens
> they would've noticed the needle was stuck at E.
>
> I think they should upgrade to a transparent ET so that fuel levels are
> visible at all times.
>
> Here's another good idea: replace mission control staff with home compter
> users across the globe. Even casual 28.8 dialup users could monitor
> critical systems. Holds could be built in to ascent timeline to allow
users
> to reboot or to OK error messages on their possibly dated homebuilt
systems.
>
> Speaking of which, for the current sensor problems, why didn't someone
just
> hit ctrl-alt-del onboard the orbiter? I assume it runs Win98?
>
> If anyone at NASA is reading this, here's a secondary fix: go to Device
> Manager>Fuel System>ET>Sensors. You should see four instances of
Depletion
> Sensor. Choose each and click Properties and then update the drivers. If
> you need to do this quickly during launch, here's a shortcut,
> WindowsKey+Pause brings up Device Manager, or DM. I realize DM has a few
> billion entries, but come on, get some people on this!
>
> Another hot tip: assign SRB sep to the quick launch toolbar.
>
> [Disclaimer: reinstalling SSME drivers during ascent could adversly affect
> acceleration].
>

LOL -- good stuff.

I especially liked your idea of clear tanks! Thats genius. Just add some
flourescent neon food coloring and it should easily be visable from the
ground.

[J]

"esozr" > wrote in message
.. .
>
> "J" wrote in message
>
> > But maybe if the crew had stopped playing video games on the cockpit
> screens
> > they would've noticed the needle was stuck at E.
> >
> > I think they should upgrade to a transparent ET so that fuel levels are
> > visible at all times.
> >
> > Here's another good idea: replace mission control staff with home
compter
> > users across the globe. Even casual 28.8 dialup users could monitor
> > critical systems. Holds could be built in to ascent timeline to allow
> users
> > to reboot or to OK error messages on their possibly dated homebuilt
> systems.
> >
> > Speaking of which, for the current sensor problems, why didn't someone
> just
> > hit ctrl-alt-del onboard the orbiter? I assume it runs Win98?
> >
> > If anyone at NASA is reading this, here's a secondary fix: go to Device
> > Manager>Fuel System>ET>Sensors. You should see four instances of
> Depletion
> > Sensor. Choose each and click Properties and then update the drivers.
If
> > you need to do this quickly during launch, here's a shortcut,
> > WindowsKey+Pause brings up Device Manager, or DM. I realize DM has a
few
> > billion entries, but come on, get some people on this!
> >
> > Another hot tip: assign SRB sep to the quick launch toolbar.
> >
> > [Disclaimer: reinstalling SSME drivers during ascent could adversly
affect
> > acceleration].
> >
>
> LOL -- good stuff.
>
> I especially liked your idea of clear tanks! Thats genius. Just add some
> flourescent neon food coloring and it should easily be visable from the
> ground.

:) Wow good tip; you must have technical training. Problem is, astronoauts
have used up all such food coloring in an attempt to make their food look,
hence taste better. In fact that's what that tank near the launch pad is
all about: at T-2.8 sec., 6200 gallons of neon food coloring are pumped into
a secret tank in the cargo bay. Why wait until so late in countdown to do
this? It allows mission planners to delude themselves that they can reach a
higher orbit since they have a lower launch weight at planning stages.