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

1) All avionics software implements internal isolation to prevent one
part of the system from taking down another part.
2) A faulty fuel reading cannot cause the system to reboot. In addition
to testing every possible faulty fuel value, I've tested every
combination of faulty sensor readings related to this thread and am
unable to get anything out of the ordinary to happen. The picture of
the fuel sensor with the red X is correct behavior when a gauge is
fauly or giving erroneous data.
3) When the system reboots due to a software error, a very obvious
message with a very obvious color is displayed on the screen prior to
the reboot. Was this seen? I have seen no mention of it.
4) FYI to a few: the CO message is indicating an error in the detector,
not CO in the cabin.

What was going on with the second display?
Was the "Initializing System" message being displayed each time it
'rebooted'?
During the 15minute intervals between reboots, how operational was the
system?

I won't delve into the actual debate issues of whether to go glass,
realtime reliability vs. features demanded, benefits vs. risk of
various situational awareness methods, or anything like that. I'm just
trying to get the facts straight. No software engineer would claim a
flawless system, but the facts so far do not allow for a simple answer
such as the fuel gauge or airspeed indication being the only cause.
Something very strange had to be going with where that escaping fuel
was going. If it was affecting three gauges (airspeed, co detector,
fuel) in a measurable way, who knows what it could have been doing to
less obvious internal wirings of the aircraft. I've never heard of a
report of a continuously rebooting system, and there are a lot out
there. The somewhat drastic customizations and the newness of the
aircraft add to suspicion. That said, there's no excuse for a failure,
wherever in the aircraft that failure is determined to be.

PS: I appreciate the balanced feedback and analysis of most of this
group. Don't feed the 20% trolls.

"g1000_eng" wrote in message
ups.com...
1) All avionics software implements internal isolation to prevent one
part of the system from taking down another part.
2) A faulty fuel reading cannot cause the system to reboot. In addition
to testing every possible faulty fuel value, I've tested every
combination of faulty sensor readings related to this thread and am
unable to get anything out of the ordinary to happen. The picture of
the fuel sensor with the red X is correct behavior when a gauge is
fauly or giving erroneous data.
3) When the system reboots due to a software error, a very obvious
message with a very obvious color is displayed on the screen prior to
the reboot. Was this seen? I have seen no mention of it.
4) FYI to a few: the CO message is indicating an error in the detector,
not CO in the cabin.

What was going on with the second display?
Was the "Initializing System" message being displayed each time it
'rebooted'?
During the 15minute intervals between reboots, how operational was the
system?

I won't delve into the actual debate issues of whether to go glass,
realtime reliability vs. features demanded, benefits vs. risk of
various situational awareness methods, or anything like that. I'm just
trying to get the facts straight. No software engineer would claim a
flawless system, but the facts so far do not allow for a simple answer
such as the fuel gauge or airspeed indication being the only cause.
Something very strange had to be going with where that escaping fuel
was going. If it was affecting three gauges (airspeed, co detector,
fuel) in a measurable way, who knows what it could have been doing to
less obvious internal wirings of the aircraft. I've never heard of a
report of a continuously rebooting system, and there are a lot out
there. The somewhat drastic customizations and the newness of the
aircraft add to suspicion. That said, there's no excuse for a failure,
wherever in the aircraft that failure is determined to be.

PS: I appreciate the balanced feedback and analysis of most of this
group. Don't feed the 20% trolls.


Do you expect me to believe you are a Garmin Engineer using a hotmail e-mail
addy and a 1 time poster under this username :-)

It's kind of funny once the aircraft was on the ground for 24 hours and
there was no further fuel venting and every thing dried up the G1000 worked
flawlessly until the tach failed some hours later during the flight because
of a Bad Sensor "not confirmed yet just an educated guess" There was no
alert about the reboot it was like some one just cut the power to the
displays then restored power the system did a standard reboot things started
to fail then it would reboot again. I will be talking with the customer
again upon delivery of future aircraft and will report the avionics tech's
findings on that airplane that is if they have anyone that is certified and
has the knowledge to work on and diagnose the G1000 over there!

"NW_Pilot" wrote:
"g1000_eng" wrote in message
ups.com...
1) All avionics software implements internal isolation to prevent one
part of the system from taking down another part.
2) A faulty fuel reading cannot cause the system to reboot. In
addition to testing every possible faulty fuel value, I've tested
every combination of faulty sensor readings related to this thread
and am unable to get anything out of the ordinary to happen. The
picture of the fuel sensor with the red X is correct behavior when a
gauge is fauly or giving erroneous data.
[ ... ]

Do you expect me to believe you are a Garmin Engineer using a hotmail
e-mail addy and a 1 time poster under this username :-)

Just FYI, the poster used Google Groups, which tacks on a header indicating
the IP address of the poster; in this case that header is:

Injection-Info: e3g2000cwe.googlegroups.com; posting-host=69.247.168.62;
posting-account=YoF8rQ0AAABFBsk62Tpp2wBJ_FD_CVG_

I used the "dig" utility on one of my Linux machines to see what host name(s)
might be associated with that 69.247.168.62 address. It came up with this:

c-69-247-168-62.hsd1.ks.comcast.net.

Looks like a Comcast account in Kansas, based on my understanding of how ISPs
like Comcast assign host names to IP addresses. Garmin is headquartered in
Kansas. So the possibility can't be immediately ruled out based on where the
poster is posting from.

Jim Logajan wrote:
"NW_Pilot" wrote:
"g1000_eng" wrote in message
ups.com...
1) All avionics software implements internal isolation to prevent one
part of the system from taking down another part.
2) A faulty fuel reading cannot cause the system to reboot. In
addition to testing every possible faulty fuel value, I've tested
every combination of faulty sensor readings related to this thread
and am unable to get anything out of the ordinary to happen. The
picture of the fuel sensor with the red X is correct behavior when a
gauge is fauly or giving erroneous data.
[ ... ]
Do you expect me to believe you are a Garmin Engineer using a hotmail
e-mail addy and a 1 time poster under this username :-)

Just FYI, the poster used Google Groups, which tacks on a header indicating
the IP address of the poster; in this case that header is:

Injection-Info: e3g2000cwe.googlegroups.com; posting-host=69.247.168.62;
posting-account=YoF8rQ0AAABFBsk62Tpp2wBJ_FD_CVG_

I used the "dig" utility on one of my Linux machines to see what host name(s)
might be associated with that 69.247.168.62 address. It came up with this:

c-69-247-168-62.hsd1.ks.comcast.net.

Looks like a Comcast account in Kansas, based on my understanding of how ISPs
like Comcast assign host names to IP addresses. Garmin is headquartered in
Kansas. So the possibility can't be immediately ruled out based on where the
poster is posting from.
And I would not expect a engineer from Garmin to use his real name and
email address because as a engineer I doubt he is authorized to speak
for the company. That does not stop him from commenting in a much more
knowledgeable way then a lot of the posts about this issue.

"John Theune" wrote in message
news:M6jVg.8501$pS3.1688@trnddc01...
Snip And I would not expect a engineer from Garmin to use his real name
and email address because as a engineer I doubt he is authorized to speak
for the company. That does not stop him from commenting in a much more
knowledgeable way then a lot of the posts about this issue.

As I said in my last message If Garmin would like more info from me I am
instructed to tell them to put
it on paper and place the request in the mail!

John Theune writes:

And I would not expect a engineer from Garmin to use his real name and
email address because as a engineer I doubt he is authorized to speak
for the company.

I wouldn't expect him to use a pseudonym that creates the impression
that he is an engineer, either. Most companies have policies that
prohibit such behavior, because of liability issues.

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

"Jim Logajan" wrote in message
.. .
"NW_Pilot" wrote:
"g1000_eng" wrote in message
ups.com...
1) All avionics software implements internal isolation to prevent one
part of the system from taking down another part.
2) A faulty fuel reading cannot cause the system to reboot. In
addition to testing every possible faulty fuel value, I've tested
every combination of faulty sensor readings related to this thread
and am unable to get anything out of the ordinary to happen. The
picture of the fuel sensor with the red X is correct behavior when a
gauge is fauly or giving erroneous data.
[ ... ]

Do you expect me to believe you are a Garmin Engineer using a hotmail
e-mail addy and a 1 time poster under this username :-)

Just FYI, the poster used Google Groups, which tacks on a header
indicating
the IP address of the poster; in this case that header is:

Injection-Info: e3g2000cwe.googlegroups.com; posting-host=69.247.168.62;
posting-account=YoF8rQ0AAABFBsk62Tpp2wBJ_FD_CVG_

I used the "dig" utility on one of my Linux machines to see what host
name(s)
might be associated with that 69.247.168.62 address. It came up with this:

c-69-247-168-62.hsd1.ks.comcast.net.

Looks like a Comcast account in Kansas, based on my understanding of how
ISPs
like Comcast assign host names to IP addresses. Garmin is headquartered in
Kansas. So the possibility can't be immediately ruled out based on where
the
poster is posting from.

Well, this is Usenet and I think that if it was really a garmin rep/engineer
why would they hide themselves with a hotmail account!

It will take a lot for Garmin to win my opinion and respect of them and
their products/systems if ever. Due to maybe a software flaw in their system
it could have taken my life or someone else's and probably will take a
someones in the future lets hope it's not mine.

I will still fly the G1000 for customers that hire me me to fly them I will
Just be more cautious of them!

Would I take my family or friends in one IFR conditions no way not ever!!
Not until Garmin/Cessna can prove to me that the G1000 will operate for 100+
hours without some sort of bug or failure!! Asking me to place my family in
one in IFR conditions would be the same as asking me to put a gun to their
heads and play Russian Roulette with them and I take my family in IFR
conditions in my cessna 150!

I have also been in contacted by an aviation publication about my experience
on the G1000 not sure if I want to do the interview or not? I know I should
just to expose that there maybe a potential fatal bug/flaw in the system!

If Garmin would like more info from me I am instructed to tell them to put
it on paper and place the request in the mail!

Now I am done talking about the G1000 and it's problems, Lets all talk about
other aviation related things!

I have also been in contacted by an aviation publication about my experience
on the G1000 not sure if I want to do the interview or not? I know I should
just to expose that there maybe a potential fatal bug/flaw in the system!

I think you should. But... be sure it's a respected publication with
even handed coverage, and be sure you have all your facts right as well
as you can, all your speculations identified as such, and all your ducks
in a row.

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, NW_Pilot posted:

Well, this is Usenet and I think that if it was really a garmin
rep/engineer why would they hide themselves with a hotmail account!

It will take a lot for Garmin to win my opinion and respect of them
and their products/systems if ever. Due to maybe a software flaw in
their system it could have taken my life or someone else's and
probably will take a someones in the future lets hope it's not mine.

Your experience sounds to me more like a hardware problem than software.
For example, the continuous rebooting may be caused by an intermittent
ground connection to the G1000, causing its power to switch on and off.
Given that the panel was "hacked" by the same outfit that made the poorly
kludged aux tank system (a system that clearly does have a major design
flaw) and gave you the bogus operating instructions, I am far more
suspicious of them than Garmin. The G1000 was only the most obvious
indicator of a major problem somewhere in the aircraft.

I have also been in contacted by an aviation publication about my
experience on the G1000 not sure if I want to do the interview or
not? I know I should just to expose that there maybe a potential
fatal bug/flaw in the system!

If it were me, I wouldn't do such an interview, as there is no conclusion
about the real cause of the problems you experienced. To point the finger
on the basis of pure speculation would leave you vulnerable. As can be
seen from the discussion that this has generated, inuendo can go a long
way toward creating a lasting negative impression that has no basis in
fact -- yet.

Neil

On Fri, 06 Oct 2006 09:17:52 GMT, "Neil Gould"
wrote in
:

Given that the panel was "hacked" by the same outfit that made the poorly
kludged aux tank system (a system that clearly does have a major design
flaw) and gave you the bogus operating instructions, I am far more
suspicious of them than Garmin.

That is reasonable. With the fact that Mr. Rhine was operating
portable equipment on the flight, there is potential for some
interaction there too. And it's reasonable that a small metal shaving
produced during the Garmin installation may have been dancing on a
circuit board someplace.

Clearly we don't have enough facts to reliably diagnose the cause of
the infinite reboot, but I am thankful to be made aware by Mr. Rhine's
experience of the utterly unacceptable situation that is caused when
the Garmin system becomes inoperative.