Very glad to have access to this data in flight-- thanks to the engineering team for getting this out the door!

50 minutes from start to finish of upgrade from 10.2.0.0.A. A&P assisted owner install. Used GPU. 1 hr of prep/backup, 20 minute config check and WiFi setup. Will fly soon.

Really like the dynamic WiFi config swap!

I took my time going over all the flight mode and maintenance mode pages and took pictures of everything. In the end, all settings were retained. Even the GPS antenna height that I had had to restore previously survived this time. The Jeppesen databases also survived. I had expected I would have to reload them. 

The only item that didn’t survive was the custom setting of various data locks. They were easy to restore using the pictures I took. The default setting weren’t all that bad, but I do like a few things different.

I m very happy that Avidyne allows owners to do these updates with their A&P mechanics. I am looking forward to ForeFlight integration with my Avidyne ADS-B traffic and weather. 

Rolfe

:)

+ config error

 I am still not getting traffic or weather in ForeFlight.   When I look under devices in FF, it says it is connected to the IFD for GPS, Flight Plan Send / Receive.   

I have seen a couple of issues with the IFD100 and FF one of which existed before but I thought it was to be fixed in this release.  The ETA at destination on the datablock of the IFD 100 is off by 4 hours which is the Zulu variation in my area.  This was a known issue but apparently it was not addressed yet.

The other thing I noticed is that the altitude of other aircraft appear correctly on the IFD 100 but are way off when the altitude comes over to FF.  See these 2 images taken at the same time.   The IFD 100 shows N142BF to be 100 feet above me but on FF it is shown as being 3310 feet above me.  There is also a large discrepancy for N953AZ.  I'm not sure if this is particular to my installation as I had a problem with my Icarus altitude in the previous release.

I don’t think their documentation has caught up with the updated capability from 10.2.3.1.  Their tech support said that Foreflight cannot get ADSB data from the IFD.   I sent them a screen shot of Pauls post showing it is working for some.  I have not heard back.

Here is the original reply from ForeFlight. 

“ ForeFlight can get GPS data and send/receive flight plans from your Avidyne avionics, but not use the ADS-B. See the article below relating to the connection with ForeFlight.

That article on the ForeFlight support site is left over from 2017. It's way out of date.

Here's the latest article on their site, dated April 10, 2019:  https://www.foreflight.com/support/support-center/category/about-foreflight-mobile/218282278" rel="nofollow - https://www.foreflight.com/support/support-center/category/about-foreflight-mobile/218282278

Mike

I’m trying to figure out why the data is no longer displaying on the IFD. It worked correctly before the rollover date issue.

It is tough to troubleshoot because I need to be in the air to get traffic. 

I just had my IFD upgrade done today. I connected the IFD up to ForeFlight on my iPad and everything looked good, except that I had the same altitude problem on the traffic that you did, and ForeFlight did not show a good GPS position.

Here's the weird thing: On ForeFlight I went to the ...More -> Devices -> ADS-B page. (There are two IFD related pages: An IFD page and an ADS-B page.) At the bottom of the ADS-B page there's a "Use as GPS" slider. I turned the slider OFF and the GPS started working! ForeFlight showed that it was getting accurate GPS from the IFD, and the altitudes of the traffic targets on ForeFlight were the same as those on the IFD. So everything is working now.

I can't explain the "Use as GPS" slider. But when it's off, the IFD GPS is on. Go figure.

I'm afraid to say it, but ForeFlight seems to be working very well with the IFD. It's showing traffic, radar, METARs and TAFs. Don't know about TFRs yet. There haven't been any around here. No lightning, either. Probably just as well.

Mike

See the attached screen shot.

Mike

No, the Stratus was off for the whole flight. I hope I can keep it that way.

Mike

I don't know if my GPS info is coming from the iPad GPS, from the IFD, or from extraterrestrials following me in their invisible spaceship. I just know that things seem to be working. I'm happy.

We installed the IFD540 and the MLB100 in our C182 four years ago. Now I finally have what I'd hoped for then: Full weather and traffic on the IFD and on ForeFlight with no Stratus clamped on the window. It took a little longer than expected but I'm not complaining.

Mike

Go into maintenance mode on the IFD and check to make sure your RS232 Channel Input is still set to "Capstone HS Trfc+Wx."  It could be the update changed it.  Don't know which of the 4 channels available your Lynx is wired to, so hopefully you can get that info.  Note that the correct input has "HS" in it - there is another Capstone setting that does not.

I noticed the same 3300' altitude for all traffic on FF on iPad.  This is corrected by going to FF "devices".  This will show two sources: Avidyne & ADSB (probably your MLB/Skytrax100).  Tap the "ADSB" and turn off the GPS - there is no internal GPS, but FF interprets some weird fixed altitude (3300').

Once this is OFF, all is good on target altitudes.

Tom W.

Thank you Avidyne!

. Zoom on IFD#2 nice, as a bit further away.

. Boeing Banana nice and large.

. Datablocks on all screens, including SVS

. FF displays UAT-icon traffic now from IFD WiFi (978-In stream from Skytrax100).

. FF flight plans bi-directional to/from IFD's - unlike FlyQ, not there yet.

Can't decide on optimum Traffic display.  I really love the "UAT" icons with speed vectors (978-In) but to show this on both IFD's, trade off is to give up 1090 ADS-R (for best VeriTAS) in favor of all 978-IN

.  set Transponder to 978 = On, 1090 = OFF 

.  set both IFD's to SkyTrax100 Traffic + Wx.

.  dual Aspens display 1090-In (TAS + ADSB)

Tom W.

I got the confit error in the IFD100 after updating both my IFD540 and the app. I have the app on two separate iPads, and both had the error. The IFD100 also failed to show my fuel information. The fuel screen had dashes for all the numbers.

I was able to fix the problem by completely uninstalling the IFD100 app from both iPads and downloading it again, and reinstalling the Jeppesen databases. After I did that, I got a ,essage on the IFD100 that said something like “Config Updated”. The Alert on the Aux screen said to restart the IFD100. After I did that, everything seemed to work as expected.

I also had some issues on FF that were fixed by going to Devices in the FF and turning off the GPS under the ADS-B device. FF then used the IFD GPS for position information.  I have an Avidyne MLB100 ADS-B receiver. 

Everything seems to be working as expected now. 

I still get a Traffic Degraded message on the traffic thumbnail of the IFD540, but I believe that is an issue addressed by a service bulletin on the MLB100 that requires a different setting. It is covered under warranty. I need to go to my avionics shop to get it taken care of, because I don’t have the tools to access the MLB100. Traffic and weather display fine on the IFD540 and FF. I didn’t check the IFD100 and I haven’t seen any actual problems caused by the alert. Traffic seems to be about the same as I receive with my Stratux box, when I switch Foreflight over to it.