Questions answered...

what's the temperature like
inside the cabin was comfortable (70) degrees.

o how long since startup did it happen
happened within 10 minutes of taking off.

o what's the power source for the ZAON and the GPS
airplane throug garmin interface cable.

o any vibration, maneuvering, etc. going on
straight and level flight.

o associated with radio transmissions?
no.

o was it aquiring traffic at the time - or was there nothing around
one question I can't answer for sure...but I think no traffic.



One thing we don't know is how long a data interruption the Garmin GPS will tolerate before
I think this might be our issue


reporting Traffic Unavailable. Is it allowing one second? 5 milliseconds?
I have watched the garmin tis screen no data available only lasts a second or two.


In my case, every time I've gone to the TIS setup screen on the Garmin after receiving the lost

data alert, the screen reports Data Available. So this is a transient for me - the data isn't lost for long.



Do you suppose this is a case where Garmin's tolerances are too tight for the ZAON? And it's false alarming very brief data interruptions?
I think this is our problem...the tolerances are too tight...I don't think this is a safety issue...more of an annoyance issue.

I wish I had the ability to fly a serial line analyzer in my plane connected to this system and recording. Then maybe I could report how long the dropped data incident is. But of course, when

we do something like that the problem never happens. I suspect the "watched pot" syndrome is one reason ZAON's having trouble finding this.