Yesterday both of the SV700's in my RV7 went blank while inflight. They both immediately started rebooting, and as I started setting things up again, they both shut down a 2nd time and immediately rebooted again. They both stayed on until I landed 14 min later. I have 320 hrs on the airplane and this has never happened. As a coincidence my Seattle Avionics subscription expired yesterday. Any suggestions?
SV700 went blank inflight
- Thread starter oldpharte
- Start date
Mine has done this several times in flight since upgrading to the latest software. I have been working with support and even sent my one 10 in display back to them. From the notes, I believe they think this is a issue with the the latest software version. Knowing the usual great support from Dynon I am sure that they are working around the clock to fix this. However, knowing the criticality of having your system fail in flight, especially for those flying IFR, it would be nice if they came out with a notice on this to all users. Dynon has always done the right thing in the past, I am sure they are all over this.
Definitely something is up with the latest. I used to never see my screens reboot after making a database upgrade, yet it has done it everytime since I upgraded to 13.0. I once had my 700 reboot in flight, but hasnt happened since.
As far as criticality, a screen should never reboot in flight and a patch should be released to resolve whatever the issue is, along with a few other fixes (terr alert). If I had both my screens fail at the same time I would consider that a red X and no further flight until resolved. I have 3 levels of redundancy but that is for emergencies should 1 screen fail, I have a backup with battery, but if there is an issue that 2nd screen shuts down while landing that could be a problem and safety issue for most folks. I do have a D1 however, so I could land safely, but not something I would want to count on knowing on the ground that I had a display issue.
As you stated, my confidence in Dynon is very high that they are evaluating the issue and will respond with status when they get it. Always the honest feedback and they will do what is needed, when they believe it is required.
As far as criticality, a screen should never reboot in flight and a patch should be released to resolve whatever the issue is, along with a few other fixes (terr alert). If I had both my screens fail at the same time I would consider that a red X and no further flight until resolved. I have 3 levels of redundancy but that is for emergencies should 1 screen fail, I have a backup with battery, but if there is an issue that 2nd screen shuts down while landing that could be a problem and safety issue for most folks. I do have a D1 however, so I could land safely, but not something I would want to count on knowing on the ground that I had a display issue.
As you stated, my confidence in Dynon is very high that they are evaluating the issue and will respond with status when they get it. Always the honest feedback and they will do what is needed, when they believe it is required.
dlloyd
Member
First flight after upgrading to 13.0 one of my screens rebooted in flight. Traded emails and sent a diagnostic to Dynon. They were looking at it but did not share any info. Yesterday while loading the latest database (same stick with the SA charts) one screen rebooted a couple times. Hadn't seen that in the past 5 years. I agree, something is up.
Savannah_flyer
I love flying!
- Joined
- Apr 11, 2014
- Messages
- 37
Had three reboots in my 1000 non touch and a system event 5 in my 1000 touch. All after the last update to 13.0.3. Something's wrong...I don't know what but there is definitely something. Hope they find it.
- Joined
- Mar 23, 2005
- Messages
- 13,226
System Event 5 is a DIAGNOSTIC CAPABILITY that was added in v13.0.3... so your SkyView is now detecting an issue that was already present, but as of v13.0.3 is now being reported. Please fill out the form at http://dynon.aero/event5 to initiate a Return Material Authorization (RMA) for your SV-D1000T.
Unfortunately, the "reboots" are rare, and we don't have a lot of DATA to diagnose such reports. If you'd like to work with Dynon Avionics to do more investigation on your system, please contact our Technical Support Group (phone 425-402-0433, email support at dynonavionics dot com) to receive instructions on sending a Dynon Diagnostic File that is downloaded within an hour of system operation from when you experienced the "reboots".
Unfortunately, the "reboots" are rare, and we don't have a lot of DATA to diagnose such reports. If you'd like to work with Dynon Avionics to do more investigation on your system, please contact our Technical Support Group (phone 425-402-0433, email support at dynonavionics dot com) to receive instructions on sending a Dynon Diagnostic File that is downloaded within an hour of system operation from when you experienced the "reboots".