Skyview Classic internal memory keeps dumping lost all configuration Multiple times

[bretdavenport]

I have had a Skyview classic for several years now and other than a few minor bugs such as the fuel totalizer not saving my fuel add unless I start the engine (which seems to be fixed on last several software drops) and a few times were I land get gas and my Skyview acts as though it didn't fly such as the fuel totalizer goes back to where it was at the beginning of the flight and so does the tach and Hobbs time. These have only happened a few (say three times) and I catch it pretty quick as I keep detailed logs of each flight tach and Hobbs time separately.

So today was a new one. I flew in the morning for about 30 min. Landed and about 4 hours later after doing a little bit of maintenance to the engine area I test ran the engine all checked out good. I cowled up the airplane to go fly and flipped the master switch and got a Red X ADAHRS fail, the map was up (usually don't have it up) and the 20% engine screen was nothing I had configured (I usually don't have the 20% screen up).

As I dug through the menus the network components were all good but I realized the unit seemed to have hard reset and I lost my entire configuration, compass cal, tail number, tach time, Hobbs time. It was like the unit just flat out lost all memory.

I went home to grab my saved configuration files thinking I could resurrect the configuration to find out they don't do a thing to help set the system back to the way it was. So I spent about 2.5 hour going through each menu and setting everything back up to the way it was to include Autopilot recalibration basically setting up the system from scratch. I flipped the master switch to go home for the night and I thought maybe I would grab the configuration file so I turned the unit back on and bam lost all my configuration again. 2.5 hours down the drain again. What the F&$K is going on. I had a perfectly good unit 2.5 hours ago?!?!?

Is there an internal memory battery that took a crap? anyone experience this before?

 

[jakej]

Did you bother to contact Dynon Support ? That’s always a good course of action.

 

[bretdavenport]

Did you bother to contact Dynon Support ? That’s always a good course of action.

Of course I considered it but it occurred yesterday (saturday) I thought maybe someone one here might have experienced it before and might be able to provide insight. I fully expect that this point the unit needs to go back to Dynon but won't be able to get them on the phone till Monday morning.

 

[Rhino]

Skyview uses non-volatile flash memory, so this shouldn't be a battery issue. I would contact Dynon.

 

[bretdavenport]

Update: I spent most of the morning for a second time in 24 hours painstakingly building back up my configuration piece by piece. Saving the configuration every few minutes and cycling power to the Display each time so to earn by trust that it would save it. I was able to rebuild it nearly completely and able to get a flight off this afternoon. I'm still disturbed that this could happen and will ask Dynon about it tomorrow. I think there may be something glitchy about my non-volatile flash memory as I have had several instances where the Unit seems not to have memory of a previous flight and acts as though nothing happened. So may my non-volatile flash memory is volatile? Sorry couldn't help it.

 

[djones]

About the only way it will do this is if the solid state hard drive is failing. If it gets corrupted, the system loads factory defaults.
It will need to come back for repair. support@dynonavionics.com

 

[bretdavenport]

Thank you, I spoke with Customer support on Monday they said the same, Out of the plane and over to Dynon it goes.