Release 10.2.1 Available

Hi, 

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.

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.

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

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?

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

Thanks for this. :)

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

"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.

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

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

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

Catani wrote: [QUOTE=arkvet] 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.

George P wrote: "The FAA allows pilots to update nav databases now".  Pilots have been able to update nav databases ever since downloadable updates became available.

Correct.  I should have said "The FAA allows pilots to update nav databases now, without having to make a logbook entry."

George P wrote: There is no reason that updating software should be any more difficult than updating nav databases.

Can't agree with that.  Doing the last IFD update on my own took over an hour, after spending a couple of hours in advance making sure how to do it correctly without bricking the box.

AviSteve wrote: Ibraham wrote: Steve, For the 10.2.1 release features, under Weather, found the following statement "Removed "Traffic" aural for ADS-B traffic" Does that mean that there are no longer aural warning for conflicting traffic with the Skytrax 100?  My previous response was imprecise, so I took extra time to research back to the beginning of this issue.  It's not that the Skytrax100 (MLB100) doesn't fully meet the TSOs that it claims to meet.  Instead, it's that the 10.2 version of the IFD was generating an aural alert that is associated with a portion of the TSO not claimed by the IFD.  Once we realized that, on 12 June 2017 we issued Service Bulletin (SB) 601-00182-041 to disable that aural alert. From the service bulletin: The Avidyne IFD4XX/5XX, when used in conjunction with SkyTrax100, will cause "Traffic" aural to play. The volume setting for this aural provides insufficient range to mute the aural. Moreover, the playing of this aural is not required by the TSO's met by the IFD series products.   The change in 10.2.1 is just a formalization of the service bulletin. If you have updated to 10.2.1.0, it is no longer necessary to apply SB 601-00182-041.

Steve,

Ibraham wrote: Steve, I understand that a dealer may be required to install a service bulletin, but not publishing the SB or alerting the aircraft owners about new SB is bad practice and deprives owners from critical and important information. Cirrus aircraft publishes all their Service bulletins on their website and alert registered owner of any new ones, so does TCM for the Continental engines. AD's are published on the FAA website. Avionics dealers never contact the owner after they do an install, and the owners may never go back to the same installer.  It may be beneficial to add a section on the Avidyne website for the service bulletins and other critical information, and contact the registered owners of the specific avionics with that information. Ibraham

My Avionics shop just did 10.2.1 install on Wed.  They put the IFD on the bench, started the process and walked away to do something else.  Came back when necessary to check on progress and keep it going, but then walked away again.  The time they actually spent in front of the box was trivial.  They also updated my Nav Data.  All at NO CHARGE!

Question for those with 10.2.1. Does the release change the behavior of the keyboard popping up when selecting the standby 1 frequency?

The sound of metal would be more "annoying" if you have a mid-air collision, that would definitely ruin your day!

"In high traffic suburban areas, seeing traffic at slightly lower altitude is almost impossible, that is why you need ADS-B traffic warnings.  It is not a convenience, it is an essential safety aide, otherwise the FAA would not have mandated the ADS-B."

I didn’t mean I requested the SB be made. That was done, I assume, due to all the complaints. Once there was this SB, I requested it be installed.   I yellow CAS message and yellow intruder on the display, catches my attention every time.

AviSteve wrote: My previous response was imprecise, so I took extra time to research back to the beginning of this issue.  It's not that the Skytrax100 (MLB100) doesn't fully meet the TSOs that it claims to meet.  Instead, it's that the 10.2 version of the IFD was generating an aural alert that is associated with a portion of the TSO not claimed by the IFD.  Once we realized that, on 12 June 2017 we issued Service Bulletin (SB) 601-00182-041 to disable that aural alert.

Steve,

That explanation made sense to me until I gave it more thought.  If the IFD is the problem, why are the aural alerts only removed for the Skytrax100, and not for other ADS-B receivers?

By the way, if you say it's because the other boxes produce their own aural signals, I will point out that the SkyTrax100 box has a connector pin designated "audio out" and that pin is wired up to the audio panel in my airplane.  Maybe Avidyne can enable that feature in the SkyTrax software.

Next question: Does the logic for the traffic alert (either audio or CAS) come from the IFD or does it come from the Skytrax?

David

I contacted my A/P to have him obtain the update.  After about a week of me waiting he sent me a text saying he didn't think he was going to be able to do it.  He called tech support 3 different times and was told he had to speak with the head tech for central N America.  He left 3 messages and never received a return call.  The tech he was able to talk to said he had to contact that specific person to obtain the update.   

I guess my 550 functions fine without the update.  Moving on. 

oskrypuch wrote: arkvet wrote: ... I guess my 550 functions fine without the update.  Moving on.  The banana is still beckoning ... * Orest

I'd love to have the banana but I'm not going to make my A/P go crazy trying to get a return call over a banana.

My other option is to take a day off work to fly over and sit and wait at my avionics shop for them to do the update.  The $ they'd charge isn't the frustration.  It's the wasted time which is a precious and limited commodity.  My mobile A/P is the preferred method.