I updated to version 4.0.7. My hope was that it would solve the problem of intermittent traffic data transfer failure to the GNS430W.
I just finished the config for a 600B in my Navion. It displays on my 430W and MX-20. On my lunch flight today the MX-20 was solid but the 430W traffic would periodically drop out. I got upgraded to version 4.0.7 when I first connected the UAT console. If this is a Navworx problem then I'll wait to beat up on the avionics guy that did the wiring. I wonder how many others with an ADS600B connected to a GNS430W are experiencing this problem.
Regarding those who upgraded to 4.0.7 and the unit failed - it failed because we implemented a compliant gps and the necessary hardware was not on the boards. We required these older units to be returned and your units were upgraded to the compliant gps.
Bill Moffitt
Bill, a little more info if you please............
Can you define "older units"? Serial number range maybe?
If using an external certified GPS source ----- GTN 6560 for example, is it necessary to do the upgrade, or is this something needed for only the units using a stand along GPS??
Thanks in advance.
Mike,
Units prior to serial number 2014110001. It is still necessary regardless of using an external source.
Also, we now have the ability to interface with the "proprietary" serial GPS data from the Garmin GNS430W, GNS530W, GTN60, GTN750, and GNS480. This support will be included in release 4.0.9.
I updated to version 4.0.7. My hope was that it would solve the problem of intermittent traffic data transfer failure to the GNS430W.
It did not solve that problem, and I also appear to have lost data to my ipad running WingXpro. Previously that had been operating flawlessly.
Message in to Bill at Navworx ... stay tuned.
Don