Garmin 696 update 6.0 has a bad bug

[humptybump]

from Garmin:

Ver 6.0 of the 695/696 system software has a bug and that is the causing "NAV LOST" for the serial out data. Garmin is working on a fix and hopes to release revised software this week. DO NOT UPDATE FROM Ver 5 to Ver 6.0. You can't go back once you install a higher version.

Note this is a NEW issue created by the July 2012 firmware update provided by Garmin.

I found the above posted over on the Dynon forums.

Explains why my autopilot (affectionately called Yoda) was dropping out frequently on my flight two days ago.

Yoda lost track of the droid army after receiving bad intel from the high council.

[g3xpert]

Yes, an issue has been identified with the new software that was recently released to support the GDL39. A couple of clarifications.

1. The GPSMAP 69X and GDL39 work just fine with no problems. The GPSMAP 69X does not lose navigation.
2. The issue is only experienced by those that are using NMEA Out data streams to external devices (with and without the GDL39). The periodic NMEA Out transmissions can be interrupted at times causing the external devices using the data to indicate issues (such as Nav Lost).
3. We expect to have new software in a short time to correct the issue. We flew some new software with improved prioritization of serial data output over 260 nm this morning and didn't experience any issues, so we believe we are close to releasing improvements.
4. Those that prefer to downgrade to V5.00 may do so, but GDL39 support will be lost and user settings will be lost. User preferences will have to be manually restored. Contact us at the email address below if you need to downgrade for some reason before we have a new version with GDL39 support to fix the issue.

We apologize for any inconvenience this has caused.

Steve

[SmilingJack]

Garmin Steve!

Is this related to the G3X software v7.0?

I am preparing for a GDL39 install and I installed 7.0, now my AFS auto pilot cycles "GPS OK" then "NO GPS". On a 2.0 flight today it was consistent and did it every 5-10 min.

Since the AFS A/P is a secondary device feed by my G3X it seems like I have the same issue as the 696.

Thanks,

[g3xpert]

Hello John,

Yes, unfortunately same issue. We will be releasing new versions of at least GDU 37X (G3X) and GPSMAP 69X soon to restore the previous performance of the serial output.

If you can't wait and need to downgrade to G3X V6.40 and don't have a copy, let us know.

Steve

[SmilingJack]

Thanks for the quick response Steve!

Nope, I will tough it out with the tiny bug

I only fly VFR and on my 2 legs today of about 1.5 hrs I really didn't have any big issues.

It only indicated NO GPS for a half of second and I never lost navigation and the auto pilot seemed to "track" ok.

Have a good weekend.

[g3xpert]

We just released new software for the GPSMAP 69X and G3X (and standalone GDU 37X) that fixes the issue with intermittent loss of NMEA Out to external devices.

GPSMAP 695/696 V6.10

G3X V7.10

Again, we apologize for the inconvenience.

Thanks,
Steve

[humptybump]

Tanks! I just received my email about the new firmware. I've loaded it but I won't be able to test right away.

Thanks for the quick turn-around.

[Pmerems]

Could whatever solution that fixed the Nav lost data stream problem with the 696 fix the same issue in the 496 with the Dynon EFIS. According to Dynon this is a 496 bug?

One can only hope. Maybe Christmas will come early.

[Brantel]

Originally Posted by Pmerems

Could whatever solution that fixed the Nav lost data stream problem with the 696 fix the same issue in the 496 with the Dynon EFIS. According to Dynon this is a 496 bug?

One can only hope. Maybe Christmas will come early.

Paul,

The long term NAV Source Lost error has been around for years now.

It is not specific to the 496. It has been reported on the entire line of 296-396-496 series, the 696 and with the older Aera units. It has even been reported on other brands as well but not as much as with the Garmin units but that may be because the Garmin units are more popular. I have not seen the issue yet with my 796 but I typically fly with the 430W as the source and the ARINC 429 interface does not have the issue.

EDIT:
Regarding the long term NAV source lost issue with the Dynon AP:

Let me be clear. I do not think the issue is with the Garmin GPS's or the Garmin NMEA data stream. I personally think the issue is in Dynon's code.

Reasons I think this:

•No other user of Garmin's NMEA data stream have reported an issue.
•People with other brands of GPS's have reported the same issue.
•I have spend hours and hours logging NMEA data from my Garmin GPS's and have never found an error in the data stream

[Brantel]

Updated tail end of prior post...