Skyview Manual ARINC improvement suggestion

madb1rd

Member
Joined
Dec 8, 2007
Messages
50
I'm upgrading my panel which had one of the early D10 EFIS (subsequently upgraded to a D10-A) and one of the first publicly sold D10EMS's. I will eliminate the EMS, keep the D10-A and add a D1000 Skyview Classic. I've spent quite a few nights getting lost in the manual (and falling asleep) while trying to understand the SV-ARINC429. As I look at it I get that the SV-ARINC429 gets GPS ARINC and VOR/ILS ARINC data from the GNS430, which I'm also keeping. Reading between the wiring diagram lines I get that it also communicates back to the 430, both GPS and VOR/ILS, although it's the same data going to both. Where I get lost it how to feed one, two, or all three sets of data to my Trio Propilot. My objective is a source select switch to allow the Propilot to steer from the 430 or the Skyview.

I realized this morning this is in part because I need a broad overview in the Skyview install manual detailing what each set of data provides, benefits, pros and cons. I can gleam what the two ARINC data sets from the 430 do for the Skyview (GPS and VOR/ILS) but I'm at a total loss as to what the Skyview is communicating back to the 430, and what that does for the 430??? and why it needs to go back to both the GPS ARINC and VOR/ILS ARINC RX inputs as detailed in the Skyview install manual?

I have a 3PDT switch and I think I know how to wire it using the ARINC and GPS TX's from the Skyview and I guess the GPS ARINC and GPS serial from the 430. Or I need a 3P3T switch to be able to select all three options. This latter question is not really a Dynon question but does anybody know what the difference is on the 430 between the GPS ARINC and the VOR/ILS ARINC?

Thx
 

jakej

Well-Known Member
Joined
Oct 10, 2007
Messages
2,167
Location
Adelaide, Australia
Just follow the Trio a/pilot manual - there is a picture of the switch wiring. Or PM me & I can give you more details.
 

CanardMulti

Active Member
Joined
Apr 1, 2021
Messages
122
An alternative path:

The integration of Skyview > SV-ARINC-429 > 430W is absolutely seamless. It is well understood and the setting selections on the various setup pages are well documented. In flight, the operation of both the VOR and GPS functions integrate well with the Skyview autopilot with clear depiction on screen of who is doing what.

Skyview already has an excellent autopilot built in. All it takes to take advantage of it is to install the Skyview servos. If you chose that path, you could then remove the Trio AP and it's servos and sell them. It would almost certainly cover the cost of the new SV servos and there's an outside chance you might even come out a few $ ahead.

Consider:

- You've already paid for the SV autopilot. Why carry around the weight of a second autopilot? The weights of the swapped servos will be pretty much a wash.

- If you use the Skyview AP, you also get a usable flight director.

- Skyview only has 5 serial inputs and at least one is needed for the required GPS (2020 or 250) input. The at most 4 remaining may not be enough to facilitate all functions via RS232. If your ADSB OUT solution is via the SV transponder + the SV-GPS-2020, there are only 3 inputs available. If you add the SV-ADSB-472 for your ADSB-IN solution (works GREAT), you're down to only 2 inputs. Add a backup SV GPS and there's only 1 input.

- What's your time worth? All of the above are so well documented that even an electronics neophyte like me managed to build his own harnesses that worked correctly on the first try. The serial route you are considering will take a lot of head work and undoubtedly some trial and error = time.

- Provided you do have enough serial ports to make it all work thru the serial back door + 3 and 4 pole switches + feedback to the Trio + who knows what else will crop up in testing, it will never be as fully functional and seamless as using the ARINC front door.

No matter what you choose, enjoy the build.

Ken
 
Last edited:

Rhino

Well-Known Member
Joined
Jul 20, 2009
Messages
1,579
Translation:
1. Using the Dynon autopilot instead of the Trio means no worries about serial ports and switches = Simpler and easier.
2. Selling the Trio could pay for much, if not all, of the Dynon autopilot servos cost (autopilot itself is already built in) = Inexpensive.
3. Added capability by using the Dynon autopilot as opposed to Trio (flight director) = More bang for buck.
At least, that's what I got from it.
 

CanardMulti

Active Member
Joined
Apr 1, 2021
Messages
122
Translation:
1. Using the Dynon autopilot instead of the Trio means no worries about serial ports and switches = Simpler and easier.
2. Selling the Trio could pay for much, if not all, of the Dynon autopilot servos cost (autopilot itself is already built in) = Inexpensive.
3. Added capability by using the Dynon autopilot as opposed to Trio (flight director) = More bang for buck.
At least, that's what I got from it.
Rhino got it spot on.

The only other thing I tried to show is a sore spot with a lot of folks who otherwise love their Skyview systems: The shortage of serial ports.

Lots of 3rd party devices / radios / fancy tech can only talk to Skyview thru its serial ports. If you do a full install of Dynon branded ADS-B in / out, transponder, and backup GPS, you really only get one lonely serial input.

Ken
 

madb1rd

Member
Joined
Dec 8, 2007
Messages
50
So, although I'm not surprised, neither of my questions got answered at this point. Given my normal limited use of autopilots there is no advantage of doing the dance of installing Dynon servos and trying to sell my Propilot, and there are at least two substantial disadvantages. The Propilot gives me independent choice of nav source, and it keeps working if either, or both the 430 and Skyview crap out. Why would I do all that work for no operational advantage and a substantial loss of redundancy?
 

Rhino

Well-Known Member
Joined
Jul 20, 2009
Messages
1,579
Possibilities?????




Have no idea if that'll help or not, but I figured it wouldn't hurt.....
 
Top