I received my repaired unit back from Zaon today (12/02/08). I have not had a chance to test it.

The repair notes on the Service Receipt state:

"Found suspected issue. Tightened up cpu socket. Added silicone to corners to prevent vibrating loose."

I will follow up once I've had a chance to test fly the repaired unit.

Chad

I received my unit also, with the same note from tech support. I will let everyone know how it works.

by the way Dan (technician) at Zaon was great and the turnaround was fast.

Well I tested my "fixed" unit...it isn't fixed. 1 1/2 hour flight...traffic not available atleast 5 times...I guess it is back to the drawing board.

I'll try to note all the circumstances next time it happens to me:

o what's the temperature like
o how long since startup did it happen
o what's the power source for the ZAON and the GPS
o any vibration, maneuvering, etc. going on
o associated with radio transmissions?
o was it aquiring traffic at the time - or was there nothing around

One thing we don't know is how long a data interruption the Garmin GPS will tolerate before
reporting Traffic Unavailable. Is it allowing one second? 5 milliseconds?

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 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.

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.

My dropouts occur mostly when I am within about 500 feet above the airport on final. I don't get many drops in cruise.

I've spent 30+ years selling, installing and servicing electronic equipment and my days of doing free field testing for manufacturers stopped years ago. This is their job, not ours. My responsibility ends when I bring them a bona fide problem that has been duplicated by others. If they then elect to sit on their heals, focusing on sales and not service, my next responsibility is to the future purchasers, informing them of my honest experiences.

I callz them as I seez them...