NW_Pilot's Trans-Atlantic Flight -- All the scary details...

but it pumped gas into an overfull
tank causing the fuel to go overboard and read "more than full".
While the wing tank did lose fuel through its drain system, I believe
it stopped "reading" all together. Where did Mr. Rhine indicate in
his narrative, that it was "reading" more than full?

He didn't - that was speculation as to the cause later on. With the
fuel "more than full", the sensors would be reading "more than full" and
sending that info to the Garmin.

The Garmin went nuts.

OF course, cause and effect has not been determined, but it's a
reasonable starting point for Usenet quarterbacking.

Jose
--
"Never trust anything that can think for itself, if you can't see where
it keeps its brain." (chapter 10 of book 3 - Harry Potter).
for Email, make the obvious change in the address.

Recently, Jose posted:

but it pumped gas into an overfull
tank causing the fuel to go overboard and read "more than full".
While the wing tank did lose fuel through its drain system, I believe
it stopped "reading" all together. Where did Mr. Rhine indicate in
his narrative, that it was "reading" more than full?

He didn't - that was speculation as to the cause later on. With the
fuel "more than full", the sensors would be reading "more than full"
and sending that info to the Garmin.

The Garmin went nuts.

OF course, cause and effect has not been determined, but it's a
reasonable starting point for Usenet quarterbacking.

What I find interesting in all this Usenet quartebacking is ignoring the
shoddy installation job of other panel-mounted devices:

NW_Pilot
"The chances of myself refering or using this company for tanking is slim
I
did not pick this company the customer did and the customer was not happy
with their services anyway they did a **** poor job at cutting the panel
when they installed the ADF and PS eng. entertainment system. (I could
have
done a better job with a hack saw and a drill) and the painting on the
Horton kit they installed looked like orange peal!"

I think its reasonable to think that some of the G1000's wiring or the
unit itself was damaged during this hack. Even attaching the power to the
ADF or entertainment system in a way that caused the power to the G1000 to
be flaky or intermittent could account for the drastic failure modes he
experienced.

Neil

I think its reasonable to think that some of the G1000's wiring or the
unit itself was damaged during this hack. Even attaching the power to the
ADF or entertainment system in a way that caused the power to the G1000 to
be flaky or intermittent could account for the drastic failure modes he
experienced.

Good point.

Jose
--
"Never trust anything that can think for itself, if you can't see where
it keeps its brain." (chapter 10 of book 3 - Harry Potter).
for Email, make the obvious change in the address.

Neil Gould writes:

I think its reasonable to think that some of the G1000's wiring or the
unit itself was damaged during this hack.

That would not generally cause software reboots.

It's much more realistic to think that there are fundamental defects
in the G1000.

Even attaching the power to the
ADF or entertainment system in a way that caused the power to the G1000 to
be flaky or intermittent could account for the drastic failure modes he
experienced.

There should be no drastic failure modes at all, under any conditions.

--
Transpose mxsmanic and gmail to reach me by e-mail.

On 2006-10-06, Mxsmanic wrote:
Neil Gould writes:

I think its reasonable to think that some of the G1000's wiring or the
unit itself was damaged during this hack.

That would not generally cause software reboots.

Unless, of course, it was the power wiring. I suspect a momentary power
interruption could reboot a G1000. There's not much you can do about
that either (short of stuffing a 20 farad supercapacitor in the back of
the device or a fully fledged UPS).

--
Yes, the Reply-To email address is valid.
Oolite-Linux: an Elite tribute: http://oolite-linux.berlios.de

Dylan Smith writes:

Unless, of course, it was the power wiring. I suspect a momentary power
interruption could reboot a G1000.

It would not do so in synchronization with the software.

--
Transpose mxsmanic and gmail to reach me by e-mail.

Recently, Mxsmanic posted:

Dylan Smith writes:

Unless, of course, it was the power wiring. I suspect a momentary
power interruption could reboot a G1000.

It would not do so in synchronization with the software.

What gives you the impression that there was some "synchronization with
the software"? Nothing NW_Pilot reported would suggest it, and the
frequency and number of reboots implies something completely different.

Neil

Neil Gould writes:

What gives you the impression that there was some "synchronization with
the software"? Nothing NW_Pilot reported would suggest it, and the
frequency and number of reboots implies something completely different.

His description suggests that the system booted and went through the
same software process over and over. That is not a hardware problem.

--
Transpose mxsmanic and gmail to reach me by e-mail.