System Event 11

[Stevec]

Hi all
Anybody any idea what causes a system event 11. I was attempting to update to the latest software 16.0.04 when it produced a Event 11 message and told me to contact Dynon with a diagnostic file which I have done. The problem now is the Screen will not boot up at all and stops on the Dynon screen at the start. I will wait to hear back from Dynon hopefully reasonably quickly but just wondered if anyone new what causes this problem so I can have my wallet prepared. Frustrating thing is I had only just installed the second screen after it was returned after repair.
Steve

 

[TouchTheSky]

Any news on that? When I read your post, I was almost upgrading to 16.0.4 ...

 

[Rhino]

Based on previous reports it appears it may be an access error. There was a bug in a previous version that gave these errors for "repetitive/intermittent USB disk connection". The version update after that (15.3.3) supposedly fixed it. It doesn't sound like the access error was the bug though. The bug just manifested in that error. Likely only Dynon can clear this up.

 

[Stevec]

i have had great contact from Don at Dynon and he thinks there may be an issue with my hard drive that may have caused data corruption. I have been given some links to software to have a go at reloading the software to see if that will provide a solution. Ultimately I suspect it will have to go back for a new drive but here’s hoping we can get away with it for a while. My setup has been a bit frustrating as it was installed in 2013 by the original builder but looking at the logbooks has only done about 50 hours until I bought it last year. I now have had problems with both screens so it looks like inactivity can cause issues for electronics as well as engines.

 

[Rhino]

I should probably have investigated this long ago considering I have a background in IT, but Dynon uses solid state hard drives, right?

 

[Stevec]

No idea that was what I was wondering as well. The approach I have been told to take is to reimage the drive. I would be interested to know if a fdisk , chkdisk or the Linux equivalent type utility is run on the drive before the new image is laid down on it. However I will follow the instructions I have been given to the letter but perhaps have my fingers crossed just as a backup.

 

[RVDan]

I recently had a system event 11 and after sending in the diagnostic files was told that it was likely the USB. thumb drive. The unit went blank just after takeoff, displayed the error for 30 seconds or so then rebooted to a normal display and continued working normally ever since. If I was IFR, it would have been a few nervous moments. It is a bit disturbing that a thumb drive error (if that is what it was) can cause loss of primary display of flight data, when the USB is only used of chart data. I could see the map going blank, but not the entire unit.

 

[Rhino]

Skyview system updates are done via USB, so it can involve more than just charts. Still a good point though. A bad USB drive really shouldn't be able to mess with your system like that.

 

[Tim Fitz]

Since upgrading to 16.0.4 I have had some issues. But today on a cross country I had a system 3, system 11 and although I just did a backup battery check it said I needed another one. Checking the date it passed was shown as yesterday. All of these came on during the same flight. My skyview is 12 years old so maybe it is now dying a slow death. Just some more data points for the thread.

 

[RVDan]

Skyview system updates are done via USB, so it can involve more than just charts. Still a good point though. A bad USB drive really shouldn't be able to mess with your system like that.

True, but system updates are only done when manually iniated, and not during flight. The USB isn’t required to be inserted during flight if you don’t use Seattle Avionics charts.

 

[Rhino]

I'd still be concerned if it did that on the ground, but point taken. Avare on my tablet is starting to sound better and better all the time.

 

[Stevec]

A bit more info on my system fix. The re-imageing worked well and everything seemed to be going well. I realised when I went for the first flight that I had not loaded the hi-res pacific database. I did 4 error free flights and decided to update the database. It failed each time I tried it with invalid file error and I saw another event 11. I decided to check the USB drive when I returned home and found it was corrupted. The file system was shot to the extent that it would not reformat, I could not load anything onto it as it said it was full and I could not delete all the files from it and regain the full amount of space. I used a PC tool to fix it and then copied a new version of the pacific database to it. Today it all loaded perfectly. I now suspect the root cause of my original failure may have been the corrupted USB as that was where I was loading the new system 16.0.4 from. I have now decided anytime I want to load anything new into the system I will start with a freshly formatted USB and copy only the files I need to it. Just hoping now that this was the problem and the hard drive is not the issue but only time will tell.