Thanks for the reply. I’m using a Avionix 1090 UAT with 802 11b/g/n wi-fi
I assume you mean a "uAvionix echoUAT".
The good news is, I know that others here successfully use that combo of devices (iPad + uAvionix echoUAT), so I think you should be able to solve this.
The bad news is, it may take some fiddling to figure out what your issue is.
First, if it's not already there, please add the "ADSB" instrument to your display:
- In the lower-left area of the iFly screen, tap "Inst Group" > Customize > Add Instrument, then select "ADSB Status" from the list.
- Place the ADSB instrument wherever you want it on the display
- Tap "Save", and either "Save Current" if you're okay changing your current config, or "Save as New" if you want to make a separate configuration file from your normal config.
Then, the next time you fly, monitor this instrument. I forget exactly what it looks like when it's receiving data, but it should be intuitive (I think maybe it's the number of towers being received?). You can tap on the instrument to get a pop-up box with some diagnostic details. When ADSB data is being received, you should see your Uavionix device selected and "Status: Connected", and you should see numbers incrementing next to some/all of the data items listed.
When you experience the "data stops" problem, tap this instrument then:
- See what it says:
- Does the Status still say, "Connected", or does it say, "Waiting for Device"?
- If "Waiting for Device", is the iPad still connected to the echoUAT wifi?
- Are the "Heartbeats" still incrementing?
- Do you see anything else there that might be a clue?
- Tap Options > Reset / Reconnect. Give it a sec, and see if this gets ADSB data flowing again
- If the Reset doesn't fix the problem, try exiting out of iFly and re-launching the app
- If the iFly restart doesn't fix the problem, try tapping the ADSB instrument > Options > Change Selected Device
- If not currently set to "AUTO-DETECT", try changing to "AUTO-DETECT" and see if that changes anything (you might need to restart iFly for that to have an effect)
- Report back here what device had been selected if it wasn't "AUTO-DETECT". Maybe other echoUAT users will be able to confirm your setting was good or not.
Finally, if you are unable to resolve this issue and this problem is consistently repeatable (you seem to indicate that it is), a bug report may be in order. Please review
this post for instructions on how to capture an ADSB log file and use it to submit a bug report to Adventure Pilot.