Search results

Thanks I did call and speak with a tech Support today. Will get a diagnostic file uploaded ASAP.

My plane is an RV-12...built by Vans as an SLSA

Thanks for the info. I get that a loose connection could cause erratic readings but don’t quite understand why it returns to normal at reduced throttle.

In cruise today oil pressure suddenly began to fluctuate and then went to zero with red X shortly followed by fuel flow increasing to max. With both got audible caution warnings. Engine continued to run normally. On descent with power reduced indications returned to normal but as power...

:-* As I said in my post I flew for two hours with no USB stick installed other than the wifi adapter. Other than a screen blank/reboot 8 minutes into the flight everything has been fine. I mentioned "remnants" of the Seattle Avionics software because in the area of SkyView pertaining to what...

The other day shortly after take off my single SkyView screen went black and proceeded to reboot several times. I got a SYS 3 message to export a diagnostic file within 30 mins. Since I wouldn't land within 30 mins I did it in the air. I landed with screen normal but it said it required the...

Just tried multiple times to download FAA_av1706_ob1703_15.1.0.duc from the Dynon site. Just keeps taking me around to several pages and back to the beginning. Not seen this before. :(

Today on boot-up the EMS was missing from the SkyView screen. I was able to switch EMS on and it operated fine and then it disappeared on shutdown. After delving into the set up are of SkyView I found that I had to select EMS on a boot up which I did and which fixed the problem. My question is...

I have a Rotax 912ULS serial #6782132 and as per SB-912-066UL I have the new cylinder temp sensors which Rotax says should be labeled CLNT instead of CHT. I've updated my SkyView Touch with 15.0.4 which says you can now change CHT to CLNT. I located this in the installation manual and changed...

Update: Apparently the unit wasn't sent out to Wichita as I was told. After talking with a Dynon Tech Support again my avionics guy discovered that one if the connections had a broken pin that wasn't detected at first look. I flew the airplane and everything seems to back to normal. Yea!

Update: Unit was sent to southeast avionics dealer a few weeks ago and they can't figure out the problem. They wanted to send it to atria in Scotland but they're supposed to be sending it back to me. I contacted the Trig dealership for USA in Wichita and I'm trying to get some info from them...

Avionics shop at home field found a loose connection and did a certification check. I flew it today and it began having the same issues...aural caution, transponder failure warning, IDT, STBY, red X with increasing intensity. The avionics shop is in the process of contacting Dynon for...

I have a Vans RV-12 SLSA delivered in July 2014 with an SV-261-TXP and Touch 10" screen. Last few flights I began getting continuous intermittent caution aural alerts well as screen cautions mostly related to the transponder. Even though the transponder changed from ground to air and received...

What is happening as far as a stable version of SV 14? When is this likely to be available?

This is the statement from Dynon I found confusing.

If you're currently using V13.03 and a 250 GPS don't you need to upgrade to V14.0+ in order to modify the transponder and resume getting ADSB traffic?

Last couple of flights (SV 13.0) only get "ADSB No Radar" (which I assume is the FAA doing their mods with ADSB) and a few times have had the traffic alert on my own plane which eventually went away. Traffic is now sporadic sometimes and I mostly don't get it now. I'm waiting for Vans to post...

I conducted my first battery test which passed. It then took me about 5 hours of flying before the warning finally went away. I would get the 'caution low battery' with each start. If you push the 7/8 buttons on SkyView with engine running on ground/flight you can select backup battery status...

"We're preparing a version of v14 that will give us the ability to chase this issue down to root cause. When that's available, we'll reach out for people to try it. Additionally, we may be in touch with some of you individually to learn about the circumstances of when/how your system stopped...

Michael, thanks for finally clarifying the issue! :)