System Event 3

[Tucson9a]

I am starting a new thread. I have two 10” skyviews about 13 years old. The first one is a first generation of Classic, the second one is a Touch screen, a few year after I traded in one of the classic to the Touch.
Over the last couple of years, both screens have turned black and rebooted themselves within 60 seconds in flight, mostly during takeoffs. I downloaded the diagnostic files and sent to Dynon. I have not gotten a definitive answer. They did recommend changing new memory sticks and downloading new Seattle Avionics data, plugging the sticks directly into the back of the screens. I tried them but the events still happen. It’s no good if I takeoff in the IMC and the screens become dark. The autopilot doesn’t work while rebooting. It’s a safety hazard. I am hoping Dynon comes up some solutions.
I intend to install an independent D3, maybe wait a little longer for their newer version. However, those events have shaken my confidence on Dynon’s hardware and software, even though I have enjoyed Dynon for over a decade. A simple independent Garmin G5 ($1500) is a strong contender.

 

[skysailor]

I would recommend you pull at least one of the Skyviews out and send it back to let them look at it on the bench. They will get to the bottom of the issue there.

Let me suggest you consider the GRT Mini X (as opposed to the G5) as a backup for your Dynon. They work together quite well whereas the G5 will require additional Garmin devices to interface. That is the setup I have in both planes. The ADSB radar depiction is better on the Dynon but the traffic and textual weather interface on the GRT is vastly superior to the Dynon and can be fed industry standard GDL90 protocol. I send it from my Echo UAT. I even have my GRT control a remote transponder to save panel space. I can provide more detail if needed.

 

[swatson999]

Before doing anything else, I would recommend you *contact Dynon* either by email or phone.

 

[Tucson9a]

Thank you guys. I have called, emailed and sent the diagnostic files from both displays. I think it’s most likely a software issue. I suggested that there might be something they can do to prevent both displays going dark at the same time (I even disconnected the cable that links the two displays). That defeats the purpose of redundancy of having two displays.

 

[swatson999]

Did you read the manuals and the relevant sections re: System Events and how to access info on them via the menus? You stated it's a System Event 3. What did the display show you for info on that event?

 

[Rhino]

It doesn't really tell you anything useful. System Event 3 means there was an error that caused the system to reboot. In the past, this has sometimes been caused by USB devices, such as memory sticks or wifi modules, and often follows a database or software update.

 

[Tucson9a]

After each reboot, they did show System Event 3 on each screen. The memory sticks are new, the firmware, Seattle Avionics data are all up to date.
I flipped through the 580 page manual in a pdf file, I did not see the definition of System Event 3. However, it did say that it is not an emergency and the airplane is still airworthy. I downloaded the diagnostic files from both displays and sent them to Dynon again. It happened a few dozen times in the last couple of years. It doesn’t happen on each flight though. However, it seems happening more often lately. I am getting used to it already (desensitized the risks). That’s why I am going to install an independent EFIS, from one of the manufacturers.

 

[CanardMulti]

Re your choice of independent EFIS: If you are thinking in terms of what most call an SAI (standby attitude indicator) there are plenty of compact choices. Also, I suspect when you say 'EFIS' you are referring to an electronic screen with attitude and basic pitot static information that has its own back up battery. I'd advocate to choose one from a company other than Dynon, simply because that puts you into an entirely removed software ecosystem - call it a belt and suspenders mindset, with the belt manufactured by a different company than the suspenders. The chosen unit having the ability to display course guidance from your IFR navigator and/or your VHF NAV is a capability you'll have to decide whether or not is important for your needs.

As a bottom line, though, ANY airplane flown IFR using an integrated glass cockpit multi screen system ( Dynon, the big 'G', whatever) should have a totally independent way to keep the right side up and, preferably, tune comms of some sort in the event of the main system crashing. Your difficulties are a prime example of case in point. I'll be very interested to see how (if ??) Dynon actually succeeds in helping you pinpoint and resolve the underlying problem. Good luck!

Ken

 

[Tucson9a]

Garmin G5 is my primary consideration, Although a preview of the newer version of Dynon D3 is pretty impressive. Both of them fit in my limited real estate on my panel. I will pick one in the fall.

 

[Rhino]

I'm partial to the AV-30-E, which is considerably less expensive than the G5. The D3 is even half the cost of the AV-30 though, so evaluate what you really need for backup capability. If the D3 fits that criteria, it's the best bang for the buck. And it's totally isolated from your Skyview system, so a Skyview failure can't affect it.

EDIT: And a D3 installation couldn't be more simple.

 

[Malndi]

Interestingly the exact same thing happened to me yesterday. Rebooted itself after a normal shutdown and reported SYS EVENT 3, PITCH SERVO OFFLINE, ROLL SERVO OFFLINE. Then it shutdown again. I had installed v17.1 the previous day and though it had something to do with that.

 

[Stevec]

That’s interesting. I have just had a Sys Event 3 on my new HDX upgrade. I did assume it was something to do with the USB as I had installed the USB before I booted it up. The event occurred when I shut the screens down and the one with the USB in rebooted itself gave the system event 3 and ran on the backup battery.
I removed the USB drive and looked at its properties on the PC. It said there was a problem with the drive did I want to repair it. I did and ran the HDX with the repaired USB. It ran fine with no errors and booted up and shut down ok. Out of interest I looked at the USB drive on the PC again and the error was back. Not sure if this is what the HDX software does by altering the file system somehow so will just have to see what happens.

 

[airguy]

Didn't somebody already say that?

I think somebody did, but we don't really pay much attention to that guy.

 

[badia358]

Today I was doing my second flight on my RV-10 with three SV_HDX_1100 that I recently completed. I was testing stalls and right before the takeoff stall occurred, the three HDX Displays rebooted. I know had no instruments. When the Displays came back up, the PFD had a "SYS EVENT 3: SEE SETUP message. I continued my phase 1 testing for another hour plus and no additional issues. But this scared me and it is very concerning since I have three units to ensure that I have backup. I am not confident that I have any backup.

 

[Rhino]

Anything in the log?

 

[jakej]

Re your choice of independent EFIS: If you are thinking in terms of what most call an SAI (standby attitude indicator) there are plenty of compact choices. Also, I suspect when you say 'EFIS' you are referring to an electronic screen with attitude and basic pitot static information that has its own back up battery. I'd advocate to choose one from a company other than Dynon, simply because that puts you into an entirely removed software ecosystem - call it a belt and suspenders mindset, with the belt manufactured by a different company than the suspenders. The chosen unit having the ability to display course guidance from your IFR navigator and/or your VHF NAV is a capability you'll have to decide whether or not is important for your needs.

As a bottom line, though, ANY airplane flown IFR using an integrated glass cockpit multi screen system ( Dynon, the big 'G', whatever) should have a totally independent way to keep the right side up and, preferably, tune comms of some sort in the event of the main system crashing. Your difficulties are a prime example of case in point. I'll be very interested to see how (if ??) Dynon actually succeeds in helping you pinpoint and resolve the underlying problem. Good luck!

Ken

Ken, I totally agree 'we' keep talking about EFIS 'failures/reboots' issues & my method is to have an autopilot that can be driven by either the EFIS system OR an IFR Gps & have power available directly from the battery bus - just following something Bob Nuckolls wrote about some time ago. A more cost effective alternative is an independent attitude instrument. YMMV

 

[badia358]

Yesterday the reboots of the three HDX displays occurred 4 times. Each time during takeoff and full throttle. On Sunday when I encountered the first SYS EVENT 3 it was during a Takeoff stall. I have sent the diagnostic logs to Dynon, but no response yet. I also sent Dynon an email and no response. I plan to send Dynon the diagnostic logs from one of the SYS EVENT 3 issues from yesterday. Hopefully I will get something back since this issue is pretty serious.

 

[kurtfly]

I got the system event 3 on shutdown today. Anybody know what it means?
downloaded the diagnostic log and user logs.

Kurt

 

[Tom_RV10]

I got the System Event 3 while taxiing back for fuel after landing. I have 2 x HDX1100 and 1 x HDX800 in my RV-10. It was the pilot's HDX1100 that faulted. I am running SW v17.1.0.13527.

 

[Rhino]

I got the system event 3 on shutdown today. Anybody know what it means?

No. See post #6.