Search results

It isn't movable.

Try loading the contents of the attached zip (you need to extract the .efs file within, and load that). It should clear the log when you load it via the support program. It will only work on the D180, and only with 5.6.1.

You'll see red X's when the electrical value that is being seen on the wire is out of range for the sensor. This often means that there isn't anything connected to that wire, or that you don't have the pin selected that's hooked up to the wire that's going to the sensor you're trying to read...

So the EMS is its own self-contained device, and it sounds like fundamentally, the EMS is not working. Everything flows from there. Nothing you do from the EFIS will fix that. Get in touch with our support team at 425-402-0433 or support at dynonavionics dot com for more help with this issue.

So the whole -250 vs -2020 thing is nuanced. A couple of years ago, because of the way the SIL=0 (-250 at the time) ADS-B Out reports interact with other traffic, FAA decided to consider SIL=0 aircraft the same as completely unequipped. So -250 equipped aircraft stopped receiving aggregated...

The last number is generally a build number or other internal marker. If we don't specify a specific version, it's is essentially meaningless to you. Ignore any numbers "after" the number that we publish on the website (IE, you're up to date if our latest version is 5.6.1).

1. Only half(ish) of them. You can generally split a device's transmit pins into multiple receivers. So you should might be able to split the transmits from 10 and 29 on the Garmin's connector to both us and the G5. The in pins are not going to work. A receive pin can only listen to exactly one...

The intercom doesn't have any software in it, unlike most of our products. So absent a redesign, we aren't able to change this.

You'll see that message on the EFIS when the EMS is not transmitting information. So if the EMS itself wasn't working, that EFIS message would be expected. If the EMS wasn't working at all, that's the thing to troubleshoot. Is the EMS screen entirely blank? (in other words, not powering up at all?)

There isn't a way to adjust that.

OK, so getting technical here. The SV-GPS-2020 is both a GPS receiver and antenna. All of the electronics are in the puck. You can power it up and get a position out of it without anything else. It ultimately outputs a serial data stream. In contrast, most other IFR navigators split only the...

Unfortunately not. 50 PSI is the highest supported pressure sensor on the EMS-D10. See https://www.dynonavionics.com/includes/guides/EMS-D10_EMS-D120_FlightDEK-D180_Sensor_Types_Table_thru_v5.6.pdf

krw5927 - The logs here may still have value. Get in touch with our support staff so they can advise.

When the engine type is set to Rotax 912, there are a couple of behaviors on the EMS page that you benefit from. Once is a variable redline that increases as the engine warms up. The other is a requirement that Rotax would like to see the oil temp get to near boiling every flight so cook off...

That's our understanding.

So for those of you that are on 15.3.4 and are still seeing momentary dropouts, we'd like to see a log. Instructions and the upload page for submitting those are here: http://www.dynonavionics.com/data-datalogs-upload.php. Reference this thread in the message box.

Unfortunately, the EAA STC for the EFIS-D10A only covers the EFIS-D10A itself. Some of the accessories, like autopilot, connectivity to other devices via the HS34, etc are not permitted under that STC. Our Dynon Certified STC for Dynon SkyView, which includes and EFIS-D10A as a backup, does...

Our understanding that the rebate applied only to the installation of both the ADS-B Out emmiter (transponder in our case) and the position source (SV-GPS-2020). This is actually an improvement since last time. Now our SV-GPS-2020 is listed as acceptable, whereas last go-round it only applied to...

That's most likely a problem with the OAT probe. Give our support team a call at 425-402-0433 or an email at support at dynonavionics dot com for more help with this issue.

Also, there are return to service instructions in the installation manual that speak to what to do in this situation. See the "Returning SkyView Components to Service after Repair" section in the appendices.