Avidyne recommends that you contact your dealer to perform the installation.  However, it is possible to get the software directly by visiting our https://pilotsupport.avidyne.com/kb/article/767-ifd-5xx-4xx-software-update-10-3-0-2-update-instructional-video-for-loading/" rel="nofollow - pilot support knowledge base . 

This is a huge release, so I've tried to categorize the changes.  The changes that have a * next to them were driven by customer input through either in-person suggestion, AvidyneLive, or the Avidyne Pilot's Club Facebook group.  Thanks for the help and keep the suggestions coming!

FMS

   - Add support for non-AR procedures containing RF legs *

   - Add visual approaches *

   - Add support for oceanic navigation mode

   - Add Enroute VNAV *

   - Add aural alert for waypoint passage *

   - Add ability to set OBS on IFDs without a radio

   - Add OBS selected course digital readout

   - Allow window constraints to be edited *

   - Fix virtual keyboard display when editing user waypoints

   - Allow uploading/downloading user waypoints from/to CSV file (via Mx Mode) *

Map

   - Fixed map popups

      - Formatting for long METARs

      - Changed ETE to be a live value instead of a snapshot

      - Placement error when map is in forward view

   - Datalink

      - Change datalink CAS message from "Not Rcvd" to "Overdue"

      - Support ADS-B Icing, Lightning, Cloud Tops, Turbulence *

   - Charts

      - Center aircraft diagrams on the aircraft *

      - Add option to enable/disable charts (via Mx Mode) *

   - Certified TAWS / HTAWS

   - Support for Hi-Res terrain (requires hardware upgrade)

   - Add power line map layer

   - Modify radar display to use the Setup page distance/speed units settings

Aux

   - New Setup Page

      - Support up to 10 user profiles *

      - Allow WiFi configuration completely from flight mode

   - Com Preset List

      - Assume decimal point when setting a frequency *

      - Fix bug that allowed entry of invalid 8.33KHz channels in frequency list

   - Calculators/Timers

      - Assume decimal point when entering air data calculator baro setting *

      - Add weight calculator

      - Allow entry of negative temperature values in calculators

      - Fix trip timer to stop counting upon landing *

   - Sys page

      - Display IFD serial number on SYS page

      - Display fuel flows for each engine in a twin engine aircraft *

   - Remove AUX button coloring when advisory has been acknowledged *

   - Fix ADS-B station reception rate calculation

   - Fix checklist TOC item not being unchecked when subordinate item is edited

General

   - Add ability for one IFD to tune the radio of the other IFD

   - Dismiss frequency list after a period of inactivity *

   - Remove WiFi Allow/Ignore dialog on power up *

Interfaces

   - Add datablock to display AGL altitude from a radar altimeter

   - Support remote mount Becker BXT65xx transponder

   - Fixed IFD network so it doesn't advertise internet access *

   - Allow IFD to display data from a portable ADS-B In device *

   - Allow IFD to be an ADS-B position source for GDL-88 *

   - Improved gnd/alt transition logic for AXP322 with squat switch

   - Fix bluetooth keyboard swap key so holding it down sets 121.5 *

Maintenance Mode

   - Add ownship icon for canard aircraft *

   - Add PIN notice saying you don't actually need one

   - Fix places where PIN protected changes don't persist

   - Fix wording in bluetooth pairing instructions

   - Add various settings to support new functions (RF Legs, VNAV, Weight Calculator, Disabling Charts)

How about that!

Calling my avionics shop.

* Orest

1. Purchase paperback or Kindle versions on Amazon.com

2. Click on the Knowledge base article and find the Guides under Attachments on the right side:

http://pilotsupport.avidyne.com/kb/article/767-ifd-5xx-4xx-software-update-10-3-0-2-update-instructional-video-for-loading/" rel="nofollow - https://pilotsupport.avidyne.com/kb/article/767-ifd-5xx-4xx-software-update-10-3-0-2-update-instructional-video-for-loading/

3. Reach out to your dealer, as they are already up on the Dealer Portal for download

Apparently you will get enroute VNav advice with 10.3 ONLY if you have a IFD550. This is not due to a technical limitation, but from what I understand it was a design decision -- in my view a misstep and an opportunity missed. Hopefully that decision is rethought, and reversed.

But, even with a 550, I do not believe VNav data that can be used by the GFC500 is produced, yet.

* Orest

We attempted to get other PFD manufacturers to play, but were unable to make that happen.  Vantage will show it...

AviSteve wrote: ... An IFD550 shows a vertical deviation indicator, so we were able to show it there.  Other IFDs don't have that indicator.

Just take your cue from a standard airline ND (MFD), which is equivalent to an IFD's display, just paint a VPath indicator along the right side. Numeric indications are added, when you are out of "center" limits. Done.

There is no reason it has to be tied to the IFD egocentric SVS page. You will see a VPath indicator on both PFD & ND in most cockpits. And remember, the vast bulk of your base is non-550! But, I'm patient, will wait a little longer.

That said, congrats on getting 10.3 done. Something to celebrate.

* Orest

The service bulletin is available with the software download.  I included the link to the pilot support article in the original post, https://pilotsupport.avidyne.com/kb/article/767-ifd-5xx-4xx-software-update-10-3-0-2-update-instructional-video-for-loading/" rel="nofollow - but here it is again .  The link to the software download is at the bottom of that article.

Top Seven favorite features ...

   - Add aural alert for waypoint passage *

AuxInterfacesNot specifically mentioned in the list, but the improved flight strip logic, allowing duplicate waypoints (wtih gaps), handling of holds at IAF and similar is a BIGGIE for me, and looking forward to having that.

* Orest

Yes

Say 'YES' and I am ready to purchase your Radar Unlock feature.

Has anyone loaded this successfully from a Mac running Big Sur?

One unit fully successful, passed all checksums and showing approved version etc. per the SB. No abnormalities noted.

Second unit, similar result, all checksums good, approved version on after installation check but the error below showed up on the maintenance page. I sent a query to tech support- Result, CF corrupt, needs a reformat. Trying to figure out now if we can do this in the hangar with tools from Avidyne or unit needs to go to a dealer. 

Run the Goldmaster file and let it do its thing. If that fails, then I would do the CF reformat. I've only seen this twice and one was fixed with Goldmaster, the other with a reformat. Neither had to come back and they both are now working perfectly.

Thanks Mike- that fixed it. All good.

Ken 

I’ll give it a conditional yes.  We did fix one minor thing related to RDS81.  Maybe that fixes your situation.  I’ll hook you up with Dale in sales and we’ll see if we can work out a trial run.

It was covered on the Webinar last night. A more robust card (video maybe?) is needed to handle the higher resolution images generated from the 3 arc second terrain map.

Best,

Ken

IIRC it requires an upgrade to the internal memory due to the larger terrain maps.

Thanks,

Ken

Edit- had time to troubleshoot a little more. The inability to enter a direct to only seems to affect the use of the cross sync keyboard on the other box. If I hit direct to on either box and then scroll a waypoint with the lower right knob I can get direct to anything. The cross sync keyboard just ignores an entry, nothing happens when you hit enter. 🤔

2. Is the lack of maintaining the  previous com frequency over startups a bug with 10.3 or only an isolated thing certain users are seeing?

Congrats to Avidyne for getting this done and the great support!

Video here of the issue with Direct to failing to take the input via cross-sync. I guess she wanted to go camping no matter what.

And yes, I had a visual approach loaded for a grass strip! Love that feature.

 

https://www.smugmug.com/gallery/n-kLs2Md/i-d4pKG4b" rel="nofollow - https://www.smugmug.com/gallery/n-kLs2Md/i-d4pKG4b

Mine didn’t, so I went through all the Config settings and relevant Setup (enable and disable) settings of both units to ensure they were the same. Some were not and after I equalised those the Cross-Sync worked fine.

Hope this works for you.

Settings, versions, databases are all the same on both boxes. Most cross-sync functions work fine. Flight plan, radio frequencies, etc. It's literally just this one thing, accepting direct-to via cross-sync, that doesn't work. And it's the one thing I use on every flight.

You can see in the vid when I use the scroll wheel to enter direct to KHWD on the top unit, it shows up on both boxes immediately.

I uploaded photos of all the config pages here. 

http://www.smugmug.com/gallery/n-kLs2Md" rel="nofollow - https://www.smugmug.com/gallery/n-kLs2Md

Thanks,

Ken

Do you have keyboard convenience mode "On" in both boxes?

There is no such file from Jeppesen.  Can you post a picture of the exact message you are seeing?

My other issues have been getting my Ipads and Level BOM to talk to each other, and I seem to be almost there.

On the config page I set the Capstone to Enabled

Then to AUX page Setup, Wifi = On

Networks = BOM-XXXX

Devices = allow IP address to Always

Under User Devises = Connect

and then I see two IP address after turning on the ipads.

One of these iIP addresses apparently belong my Gen 9 Ipad that has Foreflight, the other address is my Gen7 Mini which has the IDFSoftware on it, which immediately locked on to the IDF, ie, Nav and Com Freqs, Data Blocks etc.

So far so good until I get a message on the IDF440 that stat cannot connect to traffic module.

What does that mean?

Also, can you change the names from the IP addresses to say Foreflight (ipad 1) and IDF100 (Ipad2)

I am getting close. But obviously still need some help here.

Claude

Claude

allenc3 wrote: On the config page I set the Capstone to Enabled Then to AUX page Setup, Wifi = On

So far, so good...

allenc3 wrote: Networks = BOM-XXXX

I'm assuming that's what you see on the Setup page under the Networks category.

allenc3 wrote: Devices = allow IP address to Always Under User Devises = Connect and then I see two IP address after turning on the ipads.

allenc3 wrote: ...I get a message on the IDF440 that stat cannot connect to traffic module. What does that mean?

What is the exact message on the IFD440?

allenc3 wrote: Also, can you change the names from the IP addresses to say Foreflight (ipad 1) and IDF100 (Ipad2)

The IFD just shows IP addresses.

Hi Steve,

Yes. To be clear all of the convenience keyboard elements work except for the direct-to selection. If you’ve seen the video, the boxes won’t accept a direct to entry via convenience key unless the waypoint is in the active flight plan already. The “activate direct to” starts to pop in from the right when you hit enter but never comes fully onto the screen. I’ll try another video to demonstrate.

Yep, I reviewed the video and tried it on my computer at home last night but was unable to reproduce it.  I'll take a look on real hardware today.

Much appreciated Steve. I took another couple of videos here to try to make it clearer.

Best,

Ken

http://www.smugmug.com/gallery/n-kLs2Md/i-xxJD5Xj/A" rel="nofollow - https://photos.smugmug.com/Airplanes/Avidyne-update-/i-3fdQzVL/0/152d2a4f/1920/IMG_4622-1920.mp4

http://www.smugmug.com/gallery/n-kLs2Md/i-CGxHmJR/A" rel="nofollow - https://photos.smugmug.com/photos/i-CGxHmJR/0/6cac91e8/1920/i-CGxHmJR-1920.mp4

I was able to reproduce this and indeed it is incorrect behavior.  Cross sync is fine.  it's the keyboard convenience mode that has the issue.  We'll look deeper into it.

Until we have a fix released, here are two workarounds:

1) Disable keyboard convenience mode and continue to use the virtual keyboard to enter the identifier

2) Use the knobs to enter the -D-> identifier

Sorry for the inconvenience.

That’s great Steve, it feels better to know I’m not going nuts!

Best,

Ken 

1. VNAV does require a baro altitude input.

2. This has been discussed at length already, but I guess the answer is "both" :)

Do I have a setting wrong that I'm unaware of? 

See http://www.avidynelive.com/10-3-upgrade-issues_topic2395.html" rel="nofollow - this thread...

A known bug. It defaults to the Freqs for KMLB TWR & DEP. Probably why it wasn't noticed.

* Orest

You'll need to enable the "Remote IFD Tuning" option on the Setup Page (under the Radio category).  At that point, the com radios from the other IFD can be accessed by pressing the left knob (just like Nav radios are accessed).  Once displayed, turning the knobs will adjust the frequency for the radio on the other IFD.  See page 1-32 in the 500 series Pilot Guide for full explanation.

Thanks.  Another feature request:  I'd like to select the frequency on the airport information tab->frequencies page, select the frequency and have the option to send it to standby on either IFD1 or IFD2.  

We have an IFD540, we upgraded to 10.3 last week. We use SkyDemon. And we have one user who uses the IFD100 app to plan at home and transfer to the 540. One of our members used the plane over the weekend. He could not get SkyDemon to connect to the 540. I told him that he needed to turn on the Wi-Fi in the setup menu. He could not get it to work.

Is there a problem with the connectivity with SkyDemon?

Is there any instructions or video how to connect the iPad to the 540?

Having checked the IFD documentation page, all of the documents are for the previous version.

I will be flying the plane tomorrow so I hope to be able to setup the IFD to work with SkyDemon and the IFD100 app.

Thanks in advance.

Yes there is.  On its own, SkyDemon will not connect to the IFD.  Therefore, SkyDemon will not get information from the IFD (e.g. GPS position) nor will it be able to send data to the IFD (e.g. flight plans).  I've been in contact with Tim Dawson of SkyDemon and he is aware of the problem and the solution.

In the interim, fortunately, there is a workaround.  The problem is that SkyDemon isn't announcing its presence to the IFD.  Therefore, the IFD isn't aware that there's a device connected with an app that wants to share data and doesn't have an opportunity to ask the user to accept or reject the connection to that device.  But if you start the IFD100 app on the same device on which SkyDemon is loaded, then the IFD will recognize the device and you can accept the connection.  Once that's done, start SkyDemon and it will communicate normally.  You can stop the IFD100 if you like.  It's a temporary solution, but at least you'll be able to use SkyDemon until a fix is published.

Of course, that workaround only works on an iPad since IFD100 is only on that platform.  If you're running on Android, the same technique could work, but it would require another Android app that has the capability to connect with an IFD.

Claude

What file?  What problem?

No you can't disable the obstacles database.  Good idea about a nav/obstacle bundle.  I'll suggest that to Jeppesen and see if we can work something out.

I don't have a schedule for 10.3 fixes (e.g. the frequency issue).  it will be the same process as we use for all of our software releases.  How big it is will depend on when it happens, but it will be *way* less impact than the upgrade from 10.2.x.x to 10.3.0.2.

I really hope the frequency bug isn't put on the list for the next release such that it will take another year or so.  This is something that got broken in this latest release, and in my opinion should be FIXED as soon as possible (i.e. - 10.3.0.3, or whatever).  No, it's not the end of the world, but it is a deviation from the way it has operated since day 1.  I've inadvertently transmitted on 118.2 a couple of times already.  I find this to be a major frustration.  Don't get me wrong -- I'm not trying to be a whiner or complainer.  I was an early adopter (2014) and I love my IFD, but this seems to be a clear defect in the latest update.

There is a difference between waiting patiently for new features, and waiting for a deficiency to be corrected.

+1

I really hope Avidyne considers an update just to fix this issue.  Having to reset the last frequency at every startup sounds like a huge PITA.  I am holding off on updating to 10.3 for now because of this issue.  I hope this fix comes quickly.

David

Yet another "first world" problem! ;-)

Sure, it is a nuisance, probably a little embarrassing, but it will be fixed. And honestly, if you are affected it is pretty easy to just grab and nominate the previous freqs from the FREQ  | RECENT list.

* Orest

When I depart my home airport, at a minimum I'll be tuning ATIS, clearance, ground, tower, and departure. Even if the IFD retained its last 2 frequencies, that would only give me tower and ground, so I'd be knobbin' anyway (or using COM2).

I'm very surprised we haven't seen a fix for the frequency issue by now.  Now that they know exactly how the problem manifests, they should be able to track it down rather quickly and find out what was changed to cause this new and unwanted behavior.  I really hate being reminded that my IFD-540 is screwed up every time I power it up.

Rationalize it all you want, call it a "first world problem", but that just seems like a fanboy response to me.  I'm certainly an Avidyne fanboy myself, but I don't see any need to cut them slack.  They are a top tier avionics manufacturer, and they need to be held to a high standard - anything less isn't fair to them or us.

1. Something happened with the code that created an undesired, and unintended result.

2. This result was not caught in all of the extensive testing that was done.

This of course begs the question, "what else got messed up that wasn't caught during testing?"

Well, fan boy or otherwise, coming from a programming background, I know there is no such thing as software with no bugs. It is just a matter of how soon you find them.

This is a really awkward one, I entirely agree. Kind of in your face, but at least relatively harmless.

* Orest

MacCool wrote: .... the COM frequencies do not persist across power cycles

You are a little late to the party!! ;-)

* Orest

I might be able to live with the broken frequency issue for a few months - though REALLY irritating. The loss of hard wired data from my stratux to the IFD would be a non-starter. That is an awesome feature for me... Maybe the WiFi will eliminate this need, but I'm not sold yet.

Do we have a comprehensive bug list vs. feature list yet?

I've been a software developer, architect, and product manager for 40+ years. I have shipped large commercial applications, and some of them have had embarrassing bugs in them despite our very best efforts in testing and certification. It happens. It happens whether or not you have the FAA up in your grille. It happens no matter what your CMMI maturity level is. It happened yesterday, it's happening right now, and it'll still be happening decades from now. In the grand scheme of things, this is a minor blip.

I am sure there were and are some red faces at Avidyne about this. Probably some people got yelled at. They are not as public and transparent about their bugs as some other companies, so I doubt we'll ever see a proper PIR. But they're more so than Aspen or Garmin or S-TEC (ask someone from Garmin about GFC500 servo infant mortality and see what they say!)

This too shall pass. Meanwhile, the other improvements in 10.3 are worthwhile and I am not concerned about its fitness for purpose as a primary navigation method.

I have a ticket open on this now; in my case it's hardwired to an EchoUAT used as an ADS-B receiver.   Has been working well with 10.2 for some time; stops working with 10.3 after about 15 minutes or so.   Power-cycling the IFD gets it working again, for a short while.  

Thus far Avidyne has been great to work with trouble shooting this.  

Jim

No.

Any difficulties getting this to work? What is the portable device being used?

Using Stratus 3i. -- My setup also required that Foreflight be able to access the traffic/wx.  (that is what made it unstable in my opinion)

It did sort of work, but was not stable. -- looking forward to a day when Foreflight plays nice with open-adsb.  (not holding my breath)

There are two gotchas I ran into; you must have the Stratus device booted up prior to powering on the IFD, as it will try to connect immediately to the last network it used, and if it doesn’t find it, it will revert to normal broadcast mode. 

The second is that you must allow access from both the Stratus device and a client iPad in order for things to work between all three units. It’s possible that if you let the IFD boot up into broadcast mode and then later connect it to a Stratus device in client mode, you may have to re-allow each previously permitted device, but you should see the request to connect on the IFD.