Could not connect my IFD100 to my panel mount IFD440 this morning.  Could connect the iPad to the WiFi, but the IFD100 would not connect to the IFD440.  Rebooted the IFD440 and shut the app off, tried again - no joy.  WiFi connects, app will not connect to panel.

Worked fine last week.  Since then, I updated the iPad iOS to 15.  That's been the only change to either the iPad or panel mount.

Thoughts?

Thanks!

Are you able to connect to wifi (other than in your plane), and demonstrate that you have a good connection by using, for example, a browser on your iPad?

Any chance that you have VPN client software enabled on your iPad, unexpectedly?

* Orest

Yes, I can connect to regular WiFi and browse the Internet.

I have no idea how I would know if I have VPN client software enabled unexpectedly.  But I'm pretty sure I don't.  I can say that the VPN under Settings/General/VPN & Device Management is not connected.

Thanks for the suggestions.  I just updated the iOS to 15.0.1 and will try again.  Also, had another pilot report that they connected fine so it may just be me.  :)

If you don't know about a VPN client, then it is not a factor. I have accidentally left mine running, and couldn't figure out why I couldn't connect to the IFD.

* Orest

I was in Melbourne this weekend at your hangar taking Gary Reeves IFD and Foreflight Courses. I talked to Mike Salmon about this issue. Went through the same issues. I actually attempted to connect to your demo unit you have set up but got a software mismatch error. You have 10.3 running on your demo, my IFD100 app is still 10.2, however, the fact it saw and attempted to connect was encouraging.

Anyway (short of a beta version of 10.3) is their anything I can do to make this work? After using it for the last few months I really miss it.

Claude Allen 

If you are still having issues connecting to your IFD440, there are a couple things that you can try. First, make sure that your "Chassis ID #" and "iPad ID #" are correct in iPad Settings->IFD100. Chassis ID should be "1" if configured to talk with IFD 1(top box) and 2 if configured to connect to your IFD 2(bottom box) if installed. "iPad ID #" should be 1 if this is the only iPad you are connecting to the system.

Turning off the use of "Private Address" for the IFD's network may also help. When connected to the IFD, press the "i" next to the network name in the iPad Settings for additional information. There is will be a toggle for "Private Address" that can be turned off. That Apple setting is on a network basis, so it will turning it off will not persist across different WiFi networks.

Lance

Software Engineer

So went back to my IPAD 7 running IOS 15.01.02. Private Address is on this OS, so turned it of and....... Success, logged right on. Was able to run both Ipads at the same time.

This is running through my Levil BOM mounted on my wing. Also loaded and worked through the Stratus box.

Will try it in the air tomorrow.

Claude

 

I currently have two iPads, and iPad mini 5 and an iPad pro - both are running 15.0.2 - both have "private address" setting turned off, and both are running IFD100 12.9. They are connecting to a single IFD440.

The iPad mini (Chassis#1, iPad#1) connects fine. 

The iPad Pro (Chassis#1, iPad#2) receives the the following error when trying to connect to the IFD:

I've removed and re-installed both IFD100 and IFD Trainer. The only IFD100 app I see available to download in the app store is "IFD100 10.2" (with the AviOS 10.2 on the icon), although the version history of the app states 10.3.0 release of IFD 10.2 (go figure as mentioned above).

Do you think this may be related to the way the newer iPad is seeing or registering IFD100 in the app store?

Jason

What software version do you have in your IFD?

Perhaps IFD100 thinks it's trying to connect to the IFD Trainer. I just tried to connect the iPad pro in question to a different iPad running IFD Trainer AviOS 10.3 (at home) and get the same message i did in the cockpit and posted above "IFD Version Mismatch"

While I do have the IFD Trainer installed on the iPad Pro, the trainer is not running. The trainer isn't running on the mini either (not sure it's installed).

Odd - perhaps I can try uninstalling the trainer on my cockpit iPads and see if that helps.

Other thoughts?

Can you try connecting your iPad Pro IFD100 to your real IFD, with your iPad mini powered off?

Are you sure it isn't AviOS 10.2.2.0.A? AviOS 10.2.2.0 does not have the GPS patch that came out in February 2019 to update it to AviOS 10.2.2.0.A. I could see that being a mismatch issue with the IFD100.

There was a mandatory service bulletin released in February 2019 to upgrade all IFDs running 10.2.0.0, 10.2.1.0, or 10.2.2.0 to 10.2.2.0.A to address the GPS rollover. 

Thanks for the heads up...

I installed IFD100 on another iPad Air to validate. Here are results:

Panel IFD version 10.2.2.0

iPad Pro/iOS 15.0.2 IFD100 10.2 release 10.3 / Avidyne App version 10.2.9 VERSION MISMATCH

iPad Air/iOS 12.5.5 IFD100 10.2 release 10.3/ Avidyne App version 10.2.9 VERSION MISMATCH

iPad Mini/iOS 15.0.2  IFD100 release 10.2.9 / Avidyne App version 10.2.9 WORKS

Confirmed that on the mini that IFD100 is an earlier version even though the in-app version is same:

I am surprised you can even use the IFD without the GPS rollover update. Anyway, there are a bunch of features that make the 10.2.6.1 worth the time and trouble. BTW, you will need an A&P signoff for the update.

It looks to me like the Avidyne App version in settings for the Jeppesen Update Navigation Databases in the latest IFD100 AviOS 10.2 release did not get up sequenced to 10.3.0 to match the App Store  Version number. I believe that version number discrepancy is just "noise" and does not have any impact on your IFD100 AviOS connection problems. 

I'm running the IFD100 AviOS 10.2 App Store version 10.3.0 on a iPad mini 5th gen and a iPad Pro 9.7" (both iOS 15.1) paired with a panel IFD540 running AviOS 10.2.6.1 without issue. AviOS 10.2.6.1 was released well after April 2019 and has the GPS date rollover patch embedded in it. 

Just a hypothesis for what you're experiencing:

As Avidyne prepares for the release of AviOS 10.3.0.0, it will require a corresponding separate IFD100 AviOS 10.3 app release. I suspect this recent release of the IFD100 AviOS 10.2 app was enhanced to verify that it is working with current panel IFD AviOS 10.2 version (all AviOS 10.2 versions except 10.2.0.0, 10.2.1.0, and 10.2.2.0). I expect that IFD100 AviOS 10.3 will do the same check for panel IFD AviOS 10.3 versions. It appears we're setting up for the IFD100 AviOS 10.2 to not be compatible with IFD AviOS 10.3 and the IFD100 AviOS 10.3 to possibly not be backwards compatible with panel IFD AviOS 10.2.  

I suspect that since panel IFD AviOS 10.2.2.0 is not a current AviOS 10.2 version, the IFD100 AviOS 10.2 version check fails. When the IFD100 AviOS 10.2 version check fails, this may default to assuming the panel IFD must have been updated to a version of AviOS 10.3; hence the message and why it will not connect for you. The programmed IFD100 AviOS 10.2 version check may have been developed assuming there would not any panel IFD's still using any versions of AviOS 10.1.x.x, 10.2.0.0, 10.2.1.0, or 10.2.2.0; the AviOS versions that became obsolete after April 6, 2019.

I expect IFD100 App Store version 10.2.9 does not do the panel IFD AviOS check as it was developed over a year ago; long before the release of AviOS 10.3.0 was a near term possibility. That is why that version still connects for you.

.....or I could be way off.

I happen to have the aircraft in for Mx next week. Will coordinate the http://https://pilotsupport.avidyne.com/kb/article/659-ifd-5xx-4xx-software-update-10-2-6-1-update-instructional-video-for-loading/" rel="nofollow - 10.2.6.1 update with my A&P and report back. 

Sounds like this should do the trick, get me current, and most importantly address GPS rollover SB. 

Coordinating the update took longer than expected but happy to report updating the IFD440 to 10.2.6.1 in fact resolved all issues with connectivity from IFD100 10.2 release 10.3.

Thanks again for the help!