Regardless of who physically loads the software, the upgrade must be signed off by authorized personnel with an appropriate repair station authorization or repairman certificate.  There are plenty of users who do the upgrade under the supervision of someone with said authorization who will then sign off upon completion.

If you use an NGT9000R, though, I would definitely install 10.2.6.1

What does this mean in layman's terms?

TIA!

Some low level chip configurations were changed that allowed the manufacturing process to be more efficient.  It's not something you'll ever notice or care about.

Yes, the problem was fixed.  VSR is inhibited, though, on ILS, LPV, and some LNAV/VNAV approaches.  it's also inhibited on final regardless of the kind of approach.

• 600-00299-000 IFD5XX IFD4XX Installation Manual - Rev 22 or greater

If it comes back to Avidyne, it will get latest software.  If the work is being done at the shop, just have them work with tech support to keep the software version you're on.

The ADS-B fixes improve performance, but based on other reports in the forum, it's still not perfect.

Give tech support a call, or have your installer call.  They can get it to you.

A reply from tech support acknowledged the issue and offered a resolution that provided the same results.

Misery loves company, so thought maybe someone had same issue with resolution. 

One thing that came to mind just recently is that I never did enter a PIN. Maybe that is expected?

I have an occasional dropout of the waypoint identifier on the Avidyne Entegra PFD in my Cirrus.  Tech support has never been able to explain this.

Is "declination waypoint" a waypoint name transmitted over ARIC to other screens on board?

I'm not sure what any of that would have to do with the PFD not showing a waypoint identifier.

I was wondering if this has something to do with my malfunction where I periodically loose the name of the waypoint on my PFD, while it is displayed on my MFD, but not the bearing and not the distance.  It is a weird hard to explain malfunction, unless there is more to a waypoint ID than just letters and I am starting to wonder if a waypoint is more than just letters and coordinates for this type of sophisticated equipment. 

LOL, that'll teach me to copy/paste without proofreading.  Give me a second to wipe the egg off of my face :)

There was one fix that had two parts and somehow those got translated into two separate bullets in the list (that weren't even next to each other). The fixes both involved the GAMA Graphics output.  

First, off route waypoints (i.e. nearest airports and navaids) were sent with no mag var.  The fix was to send the mag var associated with the waypoint.  For airports, that's local mag var.  For VORs, it's the published declination.

Second, when the IFD was in OBS mode, the IFD always sent local mag var.  Now, when the active leg terminates at a VOR, the IFD will send the published VOR declination.

The fixes would only affect systems that receive the GAMA Graphics output and use the mag var in OBS mode.  Not all systems use that mag var.

These fixes wouldn't have any effect on the active waypoint identifier.  The active waypoint identifier, time and distance to go are all output on separate labels.

I'll start a new thread with the release notes once 10.3 is released.

bobcain wrote: AviSteve wrote: Red checksum isn't affected by PIN. Thanks, Steve.  At least that's one thing it's not. :)