10.3 Upgrade Issues

I'm assuming your NGT-9000 is properly wired into your IFD and you are getting traffic and WX on the IFD, if this was not the case before upgrading then you need to see your avionics shop, if it was working prior to the upgrade and you are no longer seeing weather and traffic on the IFD then one of the settings for a serial port got changed and will need to be corrected, this may also involve a trip the the avionics shop if you do not know what the settings are supposed to be.

If you are getting WX and traffic on your IFD but not on your tablet when connected to the IFD make sure you have ADS-B over WiFi turned on, previously this was called ADS-B forwarding.  Go to the Aux page and then Setup.  expand the Connectivity menue and scroll down to ADS-B over WiFi, make sure this is set to "ON".

On a related note, the IFD and the NGT-9000's WiFi both use the same channel by default, channel 1, depending upon your system serial number the IFD maybe using a different channel, I would VERY HIGHLY RECOMMEND that you make sure the IFD and the NGT-9000 are using different WiFi Channels.  The WiFi frequency that both units are using is in the 2.4Ghz range which means that although there are 11 channels assigned to the range, only 3 frequencies are usable (You can Google the technical reasons), channels 1, 6, & 11.  If you choose any other frequency you can have overlap which is a bad thing.  You can set the frequency on the NGT-9000 using L3/Harris' "MPC" program which is available directly from them, of you can adjust the SSID name of the IFD's network.  Avidyne cleverly allows the end user to change the channel number by specifying the channel as part of the SSID, for example you set the IFD's SSID to be "MyPlane6" the IFD will use channel 6, if you specify "MyPlane11" the IFD will use channel 11.  Not sure what happens if you specify something like "N12345" since channel "45" is not valid, I'm guessing it'll use channel 5.

Tested it yesterday, it's definitely a 10.3 problem. Did a practice RNAV under 10.2, no integrity issues or LPV downgrades. (As a bonus my frequencies were retained after shutdown!)

How was the fallback process to 10.2.6? is it as straightforward as the upgrade or they had to take you through CF format route?

I don't expect that all known issues will be fixed with a single dot release.

Perhaps it's just somewhere that I haven't yet found, but in general it would be useful if Avidyne would post the various dot releases and the issues fixed with them. That way we could track the dot releases that have been issued and the associated items that have been fixed. I think I've read somewhere here that the current software release is 10.3.0.3..... what is in that?

The current 540 PG is Rev 08 (web page says Rev 07 but file is 08), and the manual says Rev 08 corresponds to 10.3.0.2 which implies that was the first 10.3 version actually released.

Waited another 1.5 hours then. restarted.  It must have finished the load okay, because it booted with  10.3 okay, but the screen at times would blank on and off randomly in "Maintenance Mode".   Long story short, had to have my dealer perform a CF format.  Dealer also had to reset the paid options like WiFi in my case.  So, support told me the same thing about it needing a CF Format...that didn't fix it! The screen has never blank on and off in flight in the 5 or 6 hours flown with 10.3 thank goodness, but I've convinced myself it's just waiting to do that when I'm IFR on approach.  

Even after the CF format, anytime its in the download logs or database upload it will sometimes do the screen blank on and off thing.  This Sunday while installing the latest chart data, the little airplane was almost done traveling across the bottom of the screen.   Then, the screen went dark and stayed that way just like it did during the 10.3 upgrade.  I waited several mins and restarted.  At the Update screen: "System update halted. Error detected "copying Charts Files".  Tried the update again,  same message after several seconds.  "01-2023 charts updat... ERROR"    Now on the MAP-Chart page, "Chart File Not Found".  Been working with Jeppesen support, but it's looking like I'm going the need my Avidyne Dealer's help again.  

10.3.0.2 is not keeping me awake yet, but wish this all over soon...

I had considered downgrading back to 10.2 but after looking through the bug list I didn't find anything that told me that I must downgrade.  Yeah some of the bugs are simply annoying but really don't prevent the use of the device.

The only bug I've heard of so far that causes the IFD to crash is selecting/highlighting an approach with RF legs and this bug can be worked around by simply enabling RF legs in maintenance mode even if your plane is incapable of flying RF legs.

One thing I really have to figure out is the lighting, I have never had it setup properly and usually manually adjust it during the flight.   When the original GNS430 was installed the shop didn't setup the lighting properly on the lighting buss, somehow they ran 12v all the time for the dimming circuit and added resistance to ground even though my airplane controls all of the lighting by varying the output voltage.  I have since disconnected both lines for the lighting control (they are wrapped neatly behind the panel should I decided to use them again).  Now that it gets dark early I can spend some time trying to set the dimming using the photocell correctly, then again it is often too cold that I don't want to spend time out at the airplane.

@AviSteve - any updates on fixes for 10.3?  Any ETA?   This RNAV bug seems one of the more serious issues with 10.3... My preference would be for Avidyne to not "boil the ocean" with a huge 10.3-fix++ release but rather focus just on these 10.3 issues... nothing else for this release... is that the plan or is there a different one in progress?

Thanks!! 

Doug

N208LG

AviSteve wrote: We're working on it.  I would expect some news in the very near future.

Waiting on the FAA again, or can Avidyne release this one with just a notification to the FAA?

When 10.3 was released it was the day that hell froze over as GAMI got their STC approved for their 100UL at the same time.  Wonder what other announcement the FAA is holding up?

I'm also having problems with 10.3.

Frequency thing like everyone else.

Foreflight can't send flight plans to the unit.   It tries to send but after a minute or so it reports back with a timeout error or something like that.

I can't view traffic in foreflight because the traffic option doesn't appear in the layer drop down even when the WiFi is working.

WiFi cuts out.   On a 45 minute flight yesterday, WiFi dropped out for a minute and then came back up.

No WiFi at all.  On my return flight yesterday WiFi according to Avidyne was on but according to my iPad and iPhone it wasn't broadcasting. 

I was hoping these problems are simply set up problems but after reading through this thread it seems like 10.3 has a lot problems.  I hope there's a fix soon.

I know there are some issues with WiFi on the 10.3 release of software, based upon what I've see I don't think it is with the WiFi signal itself but with the protocols running on the WiFi.  I saw it initially when connecting a Stratux to the IFD over WiFi and was able to document the problem, plus I found some potentially related issues which manifest them as FF getting errors when trying to push flight plans.

Hopefully Avidyne has a solution in their next release

The "new" issue is that WingX Pro (my plane partner's app of choice) is no longer receiving traffic (or any GDL90 data) over WiFi.  Capstone is Enabled.  ADSB-In/Out is through a GTX-345 wired to the IFD.

My two devices (iPhone and iPad) running ForeFlight work fine and show traffic and GPS location from the IFD, but even though they DO connect to the IFD local network (verified using a network sniffer) they do NOT show up under AUX->SYS->Network->Devices until ForeFlight is actually running.  Why is this?  It seems that the IFD is waiting for ForeFlight to connect to the port (4000?) and Ack something before it is recognized as a "device" on the network.

I can only suppose that WingX Pro does not do this Ack or is looking on a different port?

Did 10.3 change what port(s) it uses for sharing the GDL90 output?

What is the IFD looking for from the device before that device will show up under Devices?

Thanks

Neil

Thanks for the magic handshake.  I figured there had to be something like that but I assume that means all the apps that don't know it are now broken.  Lovely.  Thanks Avi.  Fortunately, now that you've given me the keys to the kingdom I can write my own app (I'm a registered developer) that sends the Ack code.

I believe that once you've acknowledged (the green button popup on the IFD) you can use the ALWAYS setting for that device and it won't bug you the next time.  I did this for my devices and they work fine after a power cycle.  You might try that.

Cheers

Neil

I need to try it in flight to be sure but, once the IFD accepts my iPad (green connect button appeared once I opened FF) and I set the device in SYS-NETWORK-DEVICES to ALWAYS it seemed to reconnect across IFD power cycles with no need to re-acknowledge the device.

In maintenance mode I also enabled Captsone.  I do not know if this enables GDL90 output from IFD, or tells the IFD to accept input from other devices.

I did try sending a flight plan from the IFD to ForeFlight and it worked but did not try not the other direction.

Neil

Oh, that would be a nuisance. I am used to setting and using the active standby to either #2 or #3.

* Orest

Thanks,

Vas