I have been using Seattle Avionics’ FlyQ efb on an iPad Pro normally WiFi connected to my IFD540 (currently sw 10.2.6.1) for quite some time. I also normally use a second iPad (mini 5^th gen) that is WiFi connected to my IFD540 dedicated to running the IFD100 app. With my setup, the IFD540 hosts the WiFi network. I also have a SkyTrax200 connected to my IFD540 for ADS-B in. Recently I have noticed the following:

• When the FlyQ efb app is connected and running on one iPad, the connected iPad running the IFD100 app has a repetitive “Traffic Sensor Fault” caution message. This fault lasts only a couple of seconds, then disappears for approximately 30 – 60 seconds before reappearing. This “Traffic Sensor Fault” also only occurs on the IFD100; the IFD540 never displays this fault message. If I don’t WiFi connect the FlyQ efb app to my IFD540, then I don’t get the “Traffic Sensor Fault” caution on my IFD100. I have even run the IFD100 app on both iPads WiFi connected to my IFD540 for hours without ever getting a “Traffic Sensor Fault” caution message on any of the IFD’s.
  
  
• I have had quite a few recent instances where my WiFi connected iPad running FlyQ efb will appear to lock up and lose the WiFi connection with the IFD540 after being WiFi connected for approximately 15 – 45 minutes. When this happens, the other iPad running the IFD100 continues to work normally with the IFD540. The only way I have been able to restore WiFi connectivity between the IFD540 and the iPad that was running FlyQ efb was to cycle the IFD540 WiFi off / on. I had tried restarting the locked-out iPad, closing FlyQ efb, cycling the locked-out iPad WiFi, running the iPad100 app (with FlyQ efb closed) all to no avail. Only cycling the IFD540 WiFi restores WiFi connectivity to the locked-out iPad. After hours of testing, once again, this WiFi connectivity issue seems to only occur when the affected iPad was running FlyQ efb while WiFi connected to my IFD540.
  
  I have tried running FlyQ efb Bluetooth connected to a DUAL XGPS190 during my last couple of flights and that combination operated without fault. Unfortunately, this loses any flight plan transfer capability between FlyQ efb and my IFD540 and adds another gadget to the mix.
  
  
• While uploading flight plans from FlyQ efb flight plans to the IFD physically works; I tested this recently and noticed that the uploaded flight plan created user waypoints in the IFD for each waypoint in the flight plan. This included IFD created user waypoints for already identically named and located waypoints in the IFD database as well as created IFD user waypoints for the “begin cruise” and “begin descent” predicted waypoints (both named “BEGIN” in the IFD). Flight plan downloads from the IFD to FlyQ efb work well.