Release 10.2.1 Available

Steve,

Very nice!

Edited by brou0040 - 21 Feb 2018 at 6:40pm

Great news, thanks!

I have answers to several of the questions above.  Stand by for responses to the rest…

n7ifr wrote: 1.  Any word on v10.2.1 ability to allow IFD540 to receive higher speed baud rate input (115,100 baud) from GTX345 or Lynx9000 to display ADSB Wx on both IFD 540 and Aspen MFD?

The high speed capstone interface to the GTX-345 is supported in 10.2.1.  Sorry for omitting that one from the list.  However, related changes to the install manual are still pending.

brou0040 wrote: Do we need to contact customer support for A&P upgrades as before?

The dealers will be notified in the next few days, you can coordinate with your shop for the upgrade.  If you're an A&P and have done upgrades yourself in the past, then call customer support as you have done before.  TJ may weigh in on this one as well.

AUXAIR wrote: Any update on approved linkages to the G* G5?

While there is still no formal support for G5 in 10.2.1 (i.e. we have done no formal testing of that configuration), there have been several installations where an IFD is integrated with the G5. Current plan is to get it into the STC with release 10.3.  If you have further questions regarding the G5, I would suggest posting to the thread http://forums.avidyne.com/forum_posts.asp?TID=1267&title=garmin-g5-and-ifd-540 or calling tech support.

I will also ask along with Tom. Looks like maybe there is some movement again.

TAS-A software.?

n7ifr wrote: Steve, 1.  Any word on v10.2.1 ability to allow IFD540 to receive higher speed baud rate input (115,100 baud) from GTX345 or Lynx9000 to display ADSB Wx on both IFD 540 and Aspen MFD?  2.  What is latest update on TAS"A" software upgrade availability for IFD540? Thanks. Tom W.

n7ifr wrote: What is latest update on TAS"A" software upgrade availability for IFD540?

The latest estimate for TAS-A upgrade is TSO by mid-year 2018.

dmtidler wrote: The IFD100 update is now available in the App Store. Is this update still compatible with IFD’s running software version 10.2.0?

The 10.2.1 version of IFD100 is compatible with 10.2 IFD software, but there could be some situations where user waypoints don't sync correctly.  We don't think there's any advantage to updating your IFD100 until the IFD has the new software.

brou0040 wrote: Any idea on when the new sim will be posted?

The trainer app has been updated on the App Store.

 

Where is Orest?  He finally got his banana.....

I'm in Switzerland, skiing!

But I did take notice, and delighted to see it released, for sure!

I'm out spreading the word.

* Orest

Can you advise if the KFC225/G500 glideslope arming for LPV approaches has been fixed?

Awesome! Thanks

oskrypuch wrote: I'm in Switzerland, skiing! But I did take notice, and delighted to see it released, for sure! I'm out spreading the word. * Orest

I just finished installing 10.2.1.0 in one of my IFDs tonight and it went successful exactly like the instructions say. I only touched the IFD once to confirm I backed up my settings. In my case, only the Setup FMS settings were changed on the user part of the IFD. There are some new fields and pages in the maintenance section and some of the existing values were zeroed out and had to be manually restored from my photos. I don’t have any stored routes or user waypoints, so I can’t speak to that. Unfortunately I don’t have time to do the second one tonight and I can’t test fly it because of the weather.

The actual update took about 70 minutes going from 10.2.0.0. As I’ve done in the past I took digital photos of all the settings and backed up all the data on a USB stick.

As I’ve said with the 10.2.0.0 update, I could see a shop billing up to 3 hours for an upgrade once you include all the prep work, moving the airplane into the shop, running the update, completing the post install checkout, and supplying the proper logbook entry.  I know my view is unpopular and some on the form have heartburn over this, but if I owned a shop, I’d for sure charge in the 2.5 - 3.0hr range for the first IFD and 1.5 - 2.0hr range for the second one.

Looking forward to doing the second one tomorrow and it looks like weather will prevent a flight until next week.

Edited by Gring - 22 Feb 2018 at 9:04pm

Awesome!  Thanks a bunch to the whole team for the hard work on this release.  It looks like a few of my main complaints have been fixed.  I'm really hoping the "computed course" fix is the issue I saw when flying VOR DME approaches, and having the database legs not matching the charted radials.  This was the only potentially deadly bug I had run into, and I'm glad to see it hopefully fixed.

ddgates wrote: Where are the 10.2. Install instructions? Are they devoid of the red "$1200 bricking penalty" that freaked my shop with 10.2?

n7ifr wrote: Avi-Steve: So regarding the High Speed Input compatibility with the GTX345: Will the new v10.2.1 IFD540 high speed baud input display the GTX345 composite/Merged traffic plus ADSB Wx Output?   i.e. - GTX Merged Active TAS605 (input to GTX) + Dual Link GTX345 ADSB Traffic IN (980/1090) This would be an awesome solution, (also providing the 1090 OUT)... and I suspect also display compatible to Aspen (Garmin Unlock) MFD Display. Tom W.

Steve,

Wow TJ! That's a clarification worth its weight in gold. :-)

n7ifr wrote: AviTJ wrote: ...what this means is that you can interface a TAS6xx to a GTX-345, and display a composite version of that traffic information on the IFD (via 429).  But this ability has been there since 10.2, and has nothing to due with the increase in baud rate released in 10.2.1.  The increase in baud rate in 10.2.1 facilitates the ability to parallel that RS422 FIS-B Wx output from the GTX-345 to both the IFD and to the Aspen (same situation with the NGT-9000).  Of course, this all assumes 2 different data paths between the 345 and the IFD/Aspen.  ARINC-429 for traffic, and RS422 for FIS-B Wx. Thanks TJ - very good useful information.  So, if I have this right:   .  GTX-345 Wx can display its ADSB FIS-B Wx on both units (IFD540 + Aspen - separate pathways and likely "unlock") using the higher baud rate (v10.2.1) using RS422. .  Merged GTX traffic Output (TAS + Dual ADSB IN) can display on IFD & Aspen units using traditional ARNC 429 to both. Will IFD then display UAT Icons with Speed Vectors, etc on ADSB and TAS targets as traditional circles and diamonds? Thanks again. Tom W.

Tom, That's the rub, and that's where the limitation kicks in.  The 429 data stream is not going to give you the full ADS-B traffic symbology.  For what it's worth this limitation exists, even if interfacing a 345 to a G1000 system...

Edited by AviSteve - 23 Feb 2018 at 4:03pm

Catani wrote: [QUOTE=n7ifr]The Lynx also displays ADS-B and TAS traffic on my IFD, but without the full ADS-B traffic symbology.  The IFD cannot display ADS-B weather from the NGT9000.

Hi Steve,

Yeah, the 540 does look fine.  It looks like the 550, 510 and 410 guides all have the same issue as the 440.

Is the issue with the Skytrax that it was the Navworx box, which the FAA declared inadequate, and now Navworx is no more?   I wasn't tracking that issue.   I did think that use of an external certified GPS (like the IFD) addressed the FAA concerns, but perhaps there were additional issues with it.