Search results

I don't believe there are current plans to change this. The ADS-B-based traffic/wx is essentially "passed through" in its native format, whereas various other formats would need to be individually converted and repackaged into something that apps can consume (such as the GDL format).

Yes, SkyView will support the new wx products, but it's not in the next release. 15.4 is definitely 2018.

The raw FIS-B data, including the expanded weather, should just pass through. Note that there are some peculiarities with SkyView-ForeFlight Traffic/Weather integration that won't be solved until our next (15.4) release. But then, it should work. Note that we haven't tested this ourselves to date.

Some of our guys use Avare here for various testing. Port 4000 is correct, and then traffic and weather should "just work". Flight plan transfer isn't something that is supported by Avare though. With the currently released version of software, (15.3.4), if there is an iOS device running...

The intercom isn't affected by any of the SkyView settings. I'm wondering if perhaps the SkyView audio output is going somewhere it shouldn't. But regardless, give our support team a call at 425-402-0433 for further help with this.

If you have oil pressure (or rpm), that will disable the power on alarms feature. I'm not sure what you mean by blinking though. Can you send a video of the sequence you're seeing to support at dynonavionics dot com?

There isn't, unfortunately. There isn't a software readout of the transponder serial number.

What Garrett and Ray said. We actually have a "WAAS" GPS that's STC'd as part of the SkyView Certified product line - it's the same SV-GPS-2020 that you install for 2020 ADS-B Out compliance. As others have said, the actual GPS source alone is only a small part of the equation here.

Basically what Ray said. We have a pretty substantial backlog of trade-ins that we interleave with new orders. We also had a pretty substantial period (many months) where we weren't shipping SV-ADSB-472 units because of a design issue. If you give Dan a call at the sales desk at 425-402-0433, he...

It can indicate a hardware issue with the display. Give our support team a call at 425-402-0433 or email at support at dynonavionics dot com for more help.

Ditto what Ray says. There isn't a slave mode. Each display requires serial ports, audio wires, and other inputs/outputs to be paralleled, and each diaplsy requires a SkyView Network connection to the other devices (because of the nature of the network, this really only means a single SkyView...

Still not technically fixed. 15.4 should have the real fix.

There aren't as of yet.

Yes, you can shorten the thermocouple wires.

Maybe, but not certainly. Do you change the type of fuel that you use (IE 100LL and/or mogas)? Different fuels have different capacitances, and that can affect readings.

So you have the fundamental equipment in place for a suitable IFR-capable panel. You have redundant displays and redundant sources of flight instrumentation (especially attitude). From here, you'll need a suitable IFR-capable navigator. These days, many people choose a GPS/NAV/COM such as the...

Come on now - you asked your question yesterday. We didn't address the question instantly because we didn't have an instant answer. There are lots of examples already where data isn't outputted, and not just by the 650, for proprietary reasons, the data just not being there, etc. So, we can...

They're both nominally oil temperature probes, so they are both designed for the range. I can't speak to which one might be more reactive to changes (since air will cool/heat the sensor a bit slower than fluid against the sensor will)

It should "just work", but on some installations, the voltage ranges can be tight. Do you know what the differences in voltage are across your data points (you can go back into the fuel calibration menu to see a table readout of the voltages stored for each gallon measurement.)

Did you do an end-to-end trim calibration on the aileron axis?