Interesting. Please post any updates about your experiences and resolution - it will be helpful for others.
Since you asked, here is an account of yesterday's flight.
- Device version. After connecting to the Echo via the app, tapped the Echo logo repeatedly, and eventually got the device version on the Monitor screen. Interestingly, the Configuration screen shows a bunch of additional information, to include three tantalizing "advanced settings" (SDA, SIL, and Transponder Threshold). The SIL showed a "1", and since the FAA's PAPR User Guide says a 2 or 3 are required to pass, I changed SIL to 3 and updated the advanced settings.
-Flight. I accomplished one flight with SIL set to 3, requested a performance report, and got a "failed to generate a result" response. I did two other flights, with SIL 2, and then SIL 1, and got the same failed result. Because the performance request does not specify a time, only a day, it's possible I got the SIL 3 failure the next two times I requested a report.
- ADS-B in. I have the SafeFly wired to serial 2 in on the WS, so that I can see ADS-B in data in addition to seeing it in Foreflight on my Iphone and Ipad. Throughout the flight, this data showed up correctly on the WS. However, on the Iphone (I didn't have the Ipad on board yesterday) the data appeared and disappeared randomly. I got an "incompatible device" message on the Foreflight Maps page once, and "ADS-B disconnect" once also - although ADS-B in data disappeared more than once.
So... I emailed all this to Jeff at GRT, and he said he would forward the info to uAvionix. The GRT SafeFly appears to be working correctly, in that the In data shows up on the WS, and the Out GPS data shown on the Echo Monitor screen is complete. The EchoUAT ADS-B Out functionality, however, does not appear to be working correctly. I hope to hear back very soon from Jeff on what might be going on there. Regarding the ADS-B In functionality, the fact that it works consistently on the hard-wired WS screen indicates it's working reliably. The fact that it is intermittent in Foreflight seems to be a Foreflight issue, not a uAvionix one. I have observed numerous "ADS-B disconnect" messages in the past when I was using my Stratux with Foreflight. See conversation at
https://github.com/cyoung/stratux/issues/642 for further views on that.
As soon as I get a response from GRT I will post it. Hoping for good news...