3.2.2 Update Problem

[mmarien]

I updated to 3.2.2 from 3.2.0 and had an error about ten minutes into the first flight after the update. Both the Engine page and the PDF developed red crosses. The MAP page wasn't affected. I checked the error and I believe it said "Static sensor error" or something similar. At the time I thought that that particular error shouldn't have affected the engine page.

My passenger was flying for the first time and had just a few minutes on the controls. I took the time to show him how to fly by the big screen out front and then checked the error while he wandered all over the sky. The pitch on a Glasair II is not for novices.

I used the 1-2-5 salute to reboot. It came back up but spent some time analyzing the network and then did a couple of updates. I was spending time coaching my newly deputized copilot on straight and level so I didn't see all the updates, but I think one was the ADAHRS. That matched the error but wasn't expected. When I did the update earlier, I started SV with the 1 key rather than the master switch and when I realized that the servos weren't on I turned on the master and the servos switch, but forgot the servo power comes from the avionic master so I believe the servos weren't updated. That was the first thing that came to mind when the problem occurred but then the error didn't reflect that and why should the ADAHRS be updated if it was only the servos that were missed. I believe the error occurred shortly after turning on the servos during flight.

All ended well. When the system did come back up I had to take over to fly straight and level enough for the ADAHRS to reset. That seemed to take a while, but then I wasn't IMC so it wasn't a big deal. I have no question but thought I should remind folks that it's probably important to check that the update was successful before you go flying. Checking the network page after an update will show devices and current firmware version.

 

[dynonsupport]

Yeah, what you've seen there doesn't quite make sense. Did the network go out right as you flipped on the AP breaker? If so, it may have been the out-of-date servos interfering with the network. If not, then that's a bit mysterious. If the ADAHRS was working, that implies that it had the same version as the display software, or else you'd be seeing the red X all the time, even on the ground.

 

[mmarien]

After I rethought it, I'm almost certain the red X appeared when I pushed the AP ALT hold button. So the out-of-date servos probably crashed the system although the MAP page stayed on.

The recovery was impressive. and automatic.

 

[dabear]

I've had that problem (not in flight) when one screen is updated and other screens/equipment is not updates. I've also had problems with all 3 screens, EMS, 2 ADHARS, GPS, AP servos when updating the system when EVERYTHING is on at the same time. I've had best results when
1. only one screen and all accessories are on:
2. do the update
3. confirm each of the sub units are updated (ADHARS, EMS, AP, etc)
4. Shut down 1st screen and turn on 2nd
5. Update 2nd screen
6. Shut down 2nd screen and turn on 3rd screen
7 update 3rd screen
8 restart/turn on full system and check everything is correct.

That is one of the reasons I still ask for the system to have a single quick check screen that confirms everything is up to date (firmware, AV/OB/map Databases, etc).

I can get the ADHARS to tumble with fast roll & pitch at the same time... but once going strait and level it takes just a couple of seconds to reset. that fast reset is nice.

 

[mmarien]

Thanks for the update and checklist Bear. I don't have the complications of multiple screens but will definitely be checking that the updates were all done. I think the network page is a good place to look, but it doesn't display the other screens if there are any.

 

[dabear]

The networking screen WILL show other screens if they are up and running and the same version of software.

However, what the networking screen doesn't show is the databases in each screen. So the OB/Nav databases could be different on the different screens in front and back seats.

 

[preid]

With the ethernet connection the databases are "linked" when one is updated. I confirmed that I had the latest on both screens but I also noticed that the database update was being done to the other display pretty much right after I updated it on the other screen.