Search results

Here are two possibilities/things to look at: In NAV mode, the AP won't sequence until it hits the new waypoint and will always overshoot, unless the anticipate turns feature is on. Another is that changes in TRK mode can look funny if you're watching the HEADING (not the track) and it's...

Literally, every setting is in the settings file. Probably the best way to proceed will be to get in touch with our support team so that they can help you through the details.

They're on our radar (see what I did there?). We probably won't have support on day 1, but lightning especially is one of the top weather wish list items from what we've seen.

If Jake's excellent troubleshooting tips don't help, we'll need to see it here. Give our support team a call at 425-402-0433 or email at support at dynonavionics dot com if that's the case.

We generally don't make battery parts available or publish specs because we don't consider the batteries servicable. But if you give our support team a call, they may be able to help depending on the situation.

I don't have an obvious answer. I suppose it could've happened somewhere in-between the interval, but 4hz is a pretty good rate to catch everything. Is there anything at all in the fuller data log at the same time that looks amiss?

So you really shouldn't connect a non-HDX to an HDX to try to accomplish a settings transfer - there are some behaviors that are undefined. Our official stance is that they're not cross-compatible. What I'd probably do is export your settings file and import it into your HDX. You might chop out...

Apologies for not responding. This isn't a SkyView capability at the moment, but we're always reading these forums for requested features. We generally don't make comments on implementation or timeframes unless we're really sure that it's going to happen.

Yep, that'll do it. You're going to want to do a zero pressure / airspeed calibration to get rid of the residual low airspeed indication. Full instructions are in the installation manual.

We're working on updating our twin engine support to support both engines on one screen. That work is ongoing. The ultimate display / page layout of twin engine aircraft is not yet finalized.

It's not a generally supported operation, but no version of system software will let you change your transponder software if it's not being seen at all. You should probably get in touch with our support team for further help teasing out what might be going on here. Did the transponder stop...

Ah. I misunderstood part of your post, and thought you had fitted the Kavlico as your replacement. If you've confirmed that the wiring is going back to the pins you have identified, and that you've added the appropriate resistor as indicated, your wiring should be correct based on your diagram...

Our hunch is that it's a real fluctuation, especially if other channels aren't exhibiting any issues. But first, definitely get it wired correctly... what Jake said: no 200 ohm resistor with the newer style (Kavlico) sensor. And pin 18, not 15, for power to the sensor. It needs 5V, not 12V. See...

Our shunt is rated for 60A, so you'll want one rated higher than that. Our sensor definition file for a shunt specifies 1mV/A, but you can edit the file to customize for other ratios. We don't have a specific third party shunt recommendation.

Great to hear. Thanks for the update and feedback!

I think we're going to need to see your ADAHRS here. Give our support team a call at 425-402-0433 or support at dynonavionics dot com for further help with this.

So the ideal way to keep the clock from resetting is to install a backup battery. If you do that, you definitely don't want to connect the keep alive wire, as it will recharge the backup battery as it slowly self-discharges over time. This wasn't an ideal design, and SkyView - in contrast - only...

For what it's worth, I can't think of a musical type sound that changes pitch that SkyView makes, so I don't think it's coming from SkyView.

There is not at this time.

So it turns out that the radio actually doesn't output anything when it's on an 8.33 channel, which is a limitation of the legacy protocol that it streams. We're reaching out to Trig to see if there is a workaround or any way that we can improve this experience.