Search results

What I'd expect to happen is that SkyView's flight plan will instantly change. The autopilot might see that as a momentary disruption to the GPS flight plan, which may or may not cause it to fall down to TRK+ALT mode (if that happened, it would be annunciated both on-screen and via audio alerting)

Airguy is correct. It's not just the GPS that allows for the IFR operations; It's all the other certifications as well.

Yeah, I think that's a quirk in the data log output, if I remember correctly.

I think the zeroes mean that there isn't anything being seen. That file above is erroneous though (now deleted). If you are running the latest experimental software, the fuel flow policy is always differential between the two sensors. IE, it always subtracts one from the other.

Stevec is right - there isn't a way to manully add airports, and SkyView gets its airport and runway listings from the installed database. But, it looks like runways are in there. Could be a bug, or could be something non-obvious to me. I'll file a case with engineering.

Not positive on this, but I don't think SkyView sends anything back to the SL30. It uses the information that the SL30 puts out to do its own CDI math and display, based on SkyView's selected course.

A bit stumped here - EGTs are indeed Type K if they're ours, and there wouldn't be any major change in probe configuration (as far as EGTs go) between those two engines.

Even with things in the hangar, the SL30 will spew out data that should cause the RX counter to continuously increment. If there's no activity there, SkyView isn't seeing it at all.

Plates are always shown split-screen, either replacing a 50% map, or half of a 100% map.

No. If the mode lights are working (and not all permanently lit up, which indicates a problem), the buttons should work too. There isn't a setting to disable/enable them.

Sorry for the delayed repair. I think our support team is in touch and will have your D100 heading back your way Monday.

Our support team would be happy to work through this with you. There's probably a non-obvious setting that we need to flip. Get in touch with them via email or phone - contact info in our signature below...

There aren't currently plans to support frequency output.

The SkyView Network status page will tell you the devices that are seeing the network error. From there, you can often deduce which cable or component (s) you need to troubleshoot. Disconnecting from the hub can indeed help identify the problem.

You want 100399-000 for sure. I think that the EGTs and CHTs are sent through the CAN bus. Our 912 iS package doesn't include the EGT/CHT harness or the probes. That said, if you were monitoring the EGT/CHTSs via sensors, you want the 100399-001 too.

That'd be our best guess too

It sounds like you're looking at the diagnostic data package, which is primarily for Dynon technical support / engineering. You want to down load the user datalogs, not the diagnostic data.

So one thing that might be helpful is the AFMS (Approved Flight Manual Supplement) for the Dynon Certified side of things. We've taken a light touch historically on specific procedures, but there are some regulatory requirements on the certified side that drives some of the documentation there...

A couple of comments: If your capacitance probe has a voltage output (ie, a variable voltage within 0-5V), the advice above holds: you can ditch the converter and use a GP input. If it's actually a frequency output though - which some are - you'll need a converter. As for the voltage readings...

There are two sides to the installation to consider: First, there's the audio connectivity. As Lou says above, two radios really deserve an audio panel to best be able to hand the audio inputs and switching to your headsets. Next, there's the data and feature interactivity with SkyView. The...