iFly GPS Forum

Thanks Walter. I do have a (relatively) new ads-b system with wifi installed (Free Flight). But this problem didn't exist prior to this flight, and then only after about 400 nm into it. On the return trip next week I will try to isolate rf noise by turning off sources. 

I appreciate the feedback and find it interesting that other users of iFly have had similar experiences. I occasionally had brief NMEA dropouts with the 700 and Trio but after discussing this with the Trio guys we decided the very tight integrity filters in the Trio device was rejecting a random incomplete or faulty sentence. After the Trio sees several good data sentences it restores the NMEA handshake.

But it got more interesting when I connected the Dynon to the same 720 NMEA feed. When the Trio rejects data the Dynon continues to display NMEA data. But what I'm seeing now is *both* devices going down simultaneously and the iFly deleting NMEA from the settings page.

Since the problem is intermittent and always shows an absence of NMEA being ported when looking at the iFly settings during a failure, I still am inclined to believe the problem resides in the Win tablet firmware but I have been unable to determine a pattern or trigger for the failures. However....to eliminate one possibility I will replace the adapter cable. I have used the same USB/serial data adapter since first flying the 700 several years ago and it has no physical damage....but maybe the chip has gotten flakey.

Thanks again for the feedback!

Flew this morning with the new serial/USB cable I received from the mothership. First flight was fine but NMEA feed failed during the second flight. I exited the application and saw the following message (didn't write it down, depending on memory...):

esectional.exe  has experienced an I/O failure; error code int32

After rebooting the application NMEA data stream returned. Both the Trio and Dynon lost data when the serial feed stopped. I still think something is going on with the software that is failing NMEA on a random basis. This is happening nearly every flight now and has reached the point of being unreliable. If anyone can shed light on the error code I would be interested in knowing what is happening.