Search results

Does this help? https://forum.flydynon.com/attachments/colours_decoded-txt.3353/

Audio alerts come from the audio outputs from the SkyView display. We don't send traffic to the 175 at all. BTW: on a more important note, the wiring diagram you posted is wrong and will not work. Here is a correct diagram.

If you replaced a 15 PSI with the new 15 PSI, the old sensor file should still work fine. The new sensor file only has the correct part number for the new sensor, the rest of it is the same. Can you verify the sensor part number on the label on the side of the sensor for me and give me a call...

That is the Aviation data base warning. Here is a screenshot with the SA charts as well. I will check with engineering to see where they stand with the early expiration issue.

Thanks, we fixed the service bulletin.....E4A is correct.

....also, when you get this on message on the screen, you need to go to the setup menu's, go to transponder setup, scroll down to see what the actual error is.

Mike, E-mail me at support@dynonavionics.com and I will send you a file that will quickly get it out of that state. This is an elusive bug we have been chasing for a while and seems linked to using the swap with a menu open. It is on engineering's list. Meanwhile, avoid using swap if you can.

The new 150 PSI sensor is extremely accurate down to pressures around 6 pounds, hence the need for the 15 PSI sensor. During testing we actually discovered the new sensors to be more accurate than the sensors they are replacing.

The new sensors share the same connector, wiring, etc. We do have a new sensor file which includes new sensor characterizations for the new sensors, but they are identical to the characterizations for the old sensors and were only done to include the new part number of the new sensors. So...

Tom, Yes, with the pull up set to NONE you can read voltage. The calibration I was talking about is the trim position calibration, not auto trim.

Tom, You really shouldn't need all of this. There are thousands flying around with Ray Allen servo's using our position sensor file. The problem is, you can't use both HDX and the Ray Allen indicators(without doing as you describe). I actually looked at doing this when I built mine and...

First, your aviation database is out of date. This is the one that gets updated every 28 days. Here is the link for that update. https://www.dynonavionics.com/us-aviation-obstacle-data.php Second as you already know the Seattle Avionics data is out of date and needs updating. As to the System...

Sorry for the slow reply, it's taking some time to get things sorted out working remotely due to the Corona Virus. If the shear screw is truly OK, I suspect we will need to see the servo here to see what's up and get it repaired. I have replied to your support e-mail request for RMA information.

It does look like we have an error in the documentation and I will need to look into which is correct. I believe the table 111 is in error. That said we need to replace this one, we have these things flying in all sorts of temps and this is the first I have seen one shutting down due to cold...

Actually, the com radio control panel is actually powered by the radio and will only light up when power is applied to the radio.

Here are the 175 settings. Note: you only need the RS232 Port 2 set to ADSB + if you are using the Garmin as the position source for your ADSB-out

Did a little research and this is the correct answer. The PLeads won't work as a tach signal for SkyView. You will need to get the "Tach Board" from SureFly. We should have no problem using the 0 - 5 volt square wave from the board on our low voltage RPM inputs on Pins 34 & 35

That means the ranges are defined by rotax and can't be user adjusted. Furthermore those are dynamic ranges where they change based on oil temperature.

I suspect this is a light sport that the manufacturer has restricted entry into the setup menus and the unit won't go into setup without a file from them being on the thumb drive. They do this because they don't allow changes to the configuration. If you contact the manufacturer, they should...

I have been working this problem trying to find the root cause and here is what I know right now. It appears Sandisk 32 GB drives that are USB 3.1 cause SkyView to not boot. I did have a customer who sent me his and I am testing to see if there is any quick fix, but it appears engineering will...