I have IFD Type set to IFD540, IFD Chassis set to #1, which was the same as the IFD540 Sys ID.  I only have 1 iPad had had iPad # set to 1.  I had WIFI ADS-B Support turned on and never thought to disable that during troubleshooting.  I'm not sure what the does anyways, I haven't found any information on that setting.  I only have a stratux providing ADS-B with no panel source.

Here is a video using the stratux network.

https://youtu.be/AL1hXBMgfu4

Here is a video using the LIO_WIFI network.

https://youtu.be/PCyRo_hAr_s

Here is a picture of the wifi setup from the maintenance mode.

https://drive.google.com/file/d/10KeyF3yG5sz5N9mOYLVfGiHDIzCR-c-B/view?usp=sharing

I sure hope not, I just bought this for the sole purpose of the IFD100 app and it meets all the requirements specified...  I'll contact customer support tomorrow and see if they can help.

Thanks for the link to the other thread, I saw that when searching the forum.  I was hoping the 3 I got would be OK because it sounded like you had the original.

I deleted the IFD100 app and the IFD trainer.  I reloaded the IFD100 app, called Jepp to reset my account, and redownloaded my navdata.

I went back to the airplane to try again, but with the ADS-B Support turned off.  I set the IFD540 to LIO_WIFI gave it a spin.  This time everything worked as expected.  I turned ADS-B support on and it didn't work.  I went back and forth a few times and it seemed repeatable that ADS-B support prevented the app wifi to stay locked up.  I switched the 540 to stratux and tried the same thing.  The wifi connection was solid with LIO_WIFI, but this time it did connect with ADS-B support enabled although the grey crossed out circle would flash over the wifi symbol once and a while although it never completely lost is connection.  I was seeing ADS-B traffic when using ifly, but not when using the IFD100.  I decided to take the airplane out to see if the IFDs needed GPS to display traffic.  Sure enough, I was able to see ADS-B traffic on the IFD100 via my stratux.  I don't recall seeing the grey lined out circle this time.

Bottom line is that it appears that the ADS-B support, which enables traffic via stratux/stratus, makes the wifi connection between the 540 and the 100 less stable.

I don't think I was seeing an ADS-B tower and was only getting data from aircraft in the area.

I was seeing TIS-B crossed out on the MAP page the entire time and going to the datalink page showed no towers.  Even with just the local aircraft, I was overloaded with CAS alerts for aircraft well over 100 miles away.  I'll have to figure out how to limit this so that unimportant traffic doesn't overwhelm the system.

Overall is that I think I'm up and running, especially with ADS-B support disabled, and hopefully the ADS-B support capability will mature in future updates making that another awesome feature.

My Cellular Data setting is grey'd out and says No SIM so I assume it is all disabled - I can't do anything to further disable it since it's greyd out.

Yes, tried both with it running and without it running, both last time and today after the reinstall, I couldn't tell any difference.  Only issue is that while the IFD100 is working, and I go to iFly, then come back, it takes a few seconds for the IFD100 to resync to the 540.  In the meantime it loses the entire flight plan and repopulates once it reconnects.

Because it was connecting with ADS-B support while on stratux today, I think the reinstall is at least partially to credit.  I didn't work to isolate it, but I'm assuming that ADS-B Support prevented the connection when trying to use LIO_WIFI.

Does the IFD100 by chance log data in the background where we could send you the logs for more in depth analysis?

Nothing more than the IFD itself.  Also, I'm not sure how you would extract them.

I wasn't sure how to extract them either since going to Download Logs sends you back to the Jepp screen and exits.  If you'd find it useful, you may consider modifying that part of the interface to allow us to extract the logs for you.

"Bottom line is that it appears that the ADS-B support, which enables traffic via stratux/stratus, makes the wifi connection between the 540 and the 100 less stable."

Not sure but this might help:

With my dual IFD540's, I usually use 540#1 (with ADSB, traffic, etc) WiFi ti talk with IFD100 & FF & FlyQ.  Last few flights, I noticed  on iPad, no matter which App, the ADSB via WiFi dropped out, and on IFD100, no traffic or Wx despite all good on data blocks and FP.

So, I changed to my IFD#2 WiFi (change iPad IFD100 Chassi to #2, etc), and all good on two more flights!

My conclusion is the WiFi from my IFD#1 is "weaker" or somehow less able to handle the bandwidth of all the data... and the WiFi in y IFD540 #2 much more capable or stable??

On my wiring of the IFD#1 vs #2, certain data-block items will not port to IFD100 from my #2 (even though ok on #2 IFD via Synch Port-3), like Fuel Data, but not an issue for me as I display fuel info on my #2IFD.

Hope that's not TMI, but basically, my #2IFD540 WiFi seems much more robust and handles the data bandwidth.

Tom W.

I *think* I have found my issue, at least I was able to repeatably create and resolve the issue a few times on the ground.  I only say I think this is it since I thought I fixed it once before and was wrong.  Totally user error.  I have a VPN on the tablet and it appears that when I turned wifi off and on again, there would be a window of time after wifi is reconnected and before the VPN attempted to connect.  This is the small window where the IFD100 would work.   I added my airplane's network to the trusted wifi list so the VPN no longer tries to auto connect to its servers when on this network and no more issues.

I was hoping to test it out flying this morning, but a wildfire decided to change my plans.  I'll update this post if I find anything different once I get up flying.

On 2 separate flights, both FF and FlyQ Apps "lost" WiFi reception.  Tried re-booting Apps, but NoJoy.

Had to re-boot my IFD #2 supplying WiFi and then all good.

Not sure why spontaneous WiFi drop-out... any ideas?

Tom W.

Works awesome. Anything can connect to the IFD wifi and get ADS-B data from the stratux. 

It's not perfect yet (sometimes get CAS alerts from a guy 10k feet above and you get the No TIS-B flag) but I understand it's improving.