Release 10.2.1 Available

Edited by Gring - 26 Feb 2018 at 6:55pm

Where in Part 43 does it say that pilots can update nav databases?

Catani wrote: arkvet wrote: I understand the desire to improve quality control by requiring a "mechanic" or "A/P" to do the update. However, I find it somewhat frustrating that many of us owners are equally if not more capable of performing this update process with meticulous care. I don't think this gripe is on Avidyne.  As I understand it, the FAA regs prohibit pilots who are not mechanics from making modifications to certified equipment.  You can do it under the supervision of someone who is authorized to make modifications and is willing to sign your work off as his own, but with or without your help they are probably going to charge you. The FAA allows pilots to update nav databases now.  Maybe one day they will let us update the software.  I think the rules should allow us to trash our certified boxes if we want to take that chance, and flag them inop if that's what happens.  Forcing us to hire somebody to do it just puts the blame for messing up the box on somebody else (although it probably would make it cheaper to get it fixed since it wouldn't be our own  fault).  As you said, your mechanic is no better at this than you are, and probably not as meticulous as you would be.  I doubt an avionics shop doing a first-time 10.2.1 update would be any more meticulous than you would be either.  But at least its legal for them to brick the box. Having said that, it's not Avidyne's violation or fault if you choose to do it yourself and screw it up.  In the past Avidyne has sent software updates straight to pilots who are willing to waive warranty claims if they brick the box, maybe because Avidyne knows the FAA will go after the pilot for the violation, not Avidyne.  Maybe Avidyne is willing to do that for 10.2.1 also.

That makes sense, and I'm sorry if I came across as pointing a finger at Avidyne for the hassle.  I honestly didn't know who was behind the reasoning and decided to vent a little.

So other than telling my A/P "contact Avidyne..."  can I give him a specific phone # or e-mail to eliminate any extra hassle of him having to look for the info?  Also, how is the update supplied to my mechanic?  Email?

Thanks

"The FAA allows pilots to update nav databases now".  Pilots have been able to update nav databases ever since downloadable updates became available.  There is no reason that updating software should be any more difficult than updating nav databases.  There are a whole host of things pilots are permitted to do, that if done wrong, will lead to a whole bunch of trouble.

I have a couple of initial impressions regarding sw 10.2.1 on my IFD540 with MLB100/Skytrax100 installed using the common RS232 connection for both TIS and FIS:

Generally, sw 10.2.1 is running as advertised; the "Set Course to XXX" I mentioned earlier in this thread is working as advertised in the IFD540 PG. I finally had conditions set today to experiment with the "banana"...once again, this works as advertised even on my airplane that does not have any baro correction input to the IFD. The "banana" also displays on the updated IFD100.

I created a user waypoint on the IFD100 yesterday and noticed it did not transfer to the IFD540, even when I tried using it in a route modification initiated from the IFD100. On the other hand, my user waypoint was not wiped from my IFD100 either. I still need to test whether the stored routes sync between the IFD100 and the IFD540 as they did previously with sw 10.2.0.

As advertised, the ADSB “Traffic” callout is gone but the CAS cautions remain.

Both yesterday and today, I had an advisory CAS message and blue AUX light shortly after departure. Yesterday, the CAS was indicating that AIRMETs had not been received and stayed that way for the entire 1.5 hours operating the airplane. When I checked the Datalink Status, it indicated that SIGMETs were being received. Today, the CAS message was for both AIRMETs and SIGMETs not being received. Once again, this displayed shortly after departure and remained for nearly 2 hours until shutdown.

All other functions of the FIS and TIS worked well (ADSB traffic, METARs, TAFs, radar, etc.) The weather in my local area didn't have any SIGMETs or AIRMETs today. This leads me to several questions: Are FIS broadcast AIRMETs and SIGMETs only for the local region (similar to regional radar)? Improved decoding of AIRMETs and SIGMETs is listed as one of the sw10.2.1 changes; did Avidyne also change the way it handles non-reception of FIS-B SIGMETs and AIRMETs as I have flown on some very nice regional days and have never seen either of these CAS messages before; I have also recently seen AIRMETs and SIGMETs graphically displayed on my IFD540 and IFD100 prior to the sw10.2.1 upgrade. Did the FAA make any recent changes to how SIGMETs and AIRMETs are broadcast over FIS-B?

The link with FlyQ efb broke with this update; GPS latitude and longitude are about the only info coming through. GPS track, altitude, flight plan transfers, and ADSB (FIS & TIS) seem to be broken.

One other observation regarding the latest version of the IFD100; I noticed while they are listed as a "bright green" items, FLTA and Terrain Awareness (TA) is Off and cannot be turned On in the User Options on my IFD100 running on an iPad mini with iOS 9.3.5. Both of these options can be toggled On/Off on my IFD100 running on an iPad Pro 9.7 with iOS 11.2.6.






Edited by dmtidler - 26 Feb 2018 at 11:19pm

Thanks for this. :)

Hi TJ,

I am in the final stages of my engineering company (RGV in UK) installing my IFD’s, should be finished in next day or two.

They have emailed Avidyne about the update, though believe they might need to order it? I’d really like to get this update done before we pick the aircraft up later this week. Can you help get them access?

Many Thanks
Terry

chflyer wrote: BTW, can 10.2.1.0 be installed by owner with A&P or must the avionics shop do it? Can the owner get access to the update instructions via myavidyne or must we go through our avionics dealer?

ddgates wrote: Where can I get the software in instructions for my mechanic to install?

jimmyz80 wrote: The excessive traffic aural alerts in 10.2 were flat out dangerous in my opinion.  I could never focus on radio calls in the pattern with "caution, traffic!" blasting in my ear

Does anybody know if we will still get the CAS alert?  Or does the 10.2.1 software treat ALL traffic as non-threat traffic with the MLB100?

On my flight yesterday, I experienced several traffic alerts that were a nuisance AND one that was real.  Getting that one real alert (from a target climbing from below me) was in my opinion entirely worth tolerating the nuisance alerts.

In a perfect world, we would only get alerts from truly alarming scenarios, but if the choice is all or none, I'll take all.

I was glad I had 10.2.0 yesterday.  And like I said, that's disappointing.  I like everything else about 10.2.1 better.

I know that in NavWorx's last push at fixing everything, they were working on a newer software version "5.0" and I wonder if Avidyne might have a copy of that software they can push through certification.  (I do not know if traffic alerts were a factor in that software change.)  With NavWorx gone, I would assume that Avidyne is exploring their options for ADS-B In equipment.  Obvious options might be: re-branding a different piece of equipment like FreeFlight or uAvionics, designing Avidyne's own product, or improving the interface capabilities for third-party equipment like the GTX345 or Lynx 9000.

But this is a real blow to those of us to equipped as "all Avidyne" unless there is a fix coming for it.

AzAv8r wrote: 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.

Hi, 

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.

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

Hi Steve,

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.

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

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.

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

Steve,

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.

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?

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.

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

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