Dynon Skyview and Trig TX56 integration
So I thought I’d give some feedback on the new Trig TX56A COM/NAV radio integration with the Dynon Skyview. I’ve seen a few posts within various forums asking the questions on compatibility and installation so below are my thoughts and minor issues that I’m trying to figure out. The Trig replaced my 1 year old, trusted second radio Garmin 200. The replacement only took us about 4 hrs to complete which included installing the Archer Antenna in the wing tip. Actually, probably the hardest part was running the RG400 cable through the wing and center section. The form and fit was almost identical to the Garmin 200 (size and weight), so swapping trays was relatively easy, no cutting panel like I would have had to do if I went with the Garmin 255. I was already using the Dynon Serial Port #3 for the Garmin 200, so the wiring was relatively easy on the Comm side but had to build a harness for the Nav side and connect to Port #3. Basically the form, fit and wiring is extremely easy as far as integrating into the Dynon Skyview. Lets talk about compatibility. The Trig understands the Garmin SL-30 “AND” Gamin 255 A/B protocols, so in Dynon skyview port (in my case) #3, I chose the Garmin 255 A/B protocol ($PGRMC and $PGRMV) which set the speed at 9600 bps and immediately the Trig started talking to the Dynon. Next is the CDI configuration that must be set up. Trig has a sub menu that you go into and push the “type” of CDI you would like. The choices are Converter, Resolver, Serial and Internal. When the Trig is talking to an external EFIS, the serial is the choice you are supposed to use, same function in the SL-30 when you chose CDI choice-“none”. So now I dial in the VOT testing frequency (we have one at the airfield), and the CDI comes up- GREAT- but if I stop turning the knob, the skyview CDI disappears. Ok, that doesn’t work correctly, so I double check all settings and even change protocol in Port #3 to SL-30 ($PMRRC and $PMRRV) but still no change to the skyview CDI needle. It will appear if I spin the knob but disappear if not actively turning the knob. So this is what I currently had to do for it to work appropriately. Like I said earlier, in the Trig sub section, you can choose Converter, Resolver, Serial or Internal. When I choose “INTERNAL”, the Dynon Skyview CDI works accordingly with a few caveats.
The skyview CDI needle WILL NOT come up if you dial in NAV frequency on the Trig, you get the ID (voice and automatic) BUT YOU HAVE TO HIT THE OBS button on the TRIG. This activates your Skyview CDI for the rest of the flight. You can change freqs, go from VOR to ILS. You can turn the CRS knob on the Dynon or Trig as both work. You can also monitor the standby Nav FREQ on the TRIG and it will get you the standby bearing. I wish that part showed up on the Dynon ‘bearing bugs’ since it is showing “NAV stby” as a Nav source but so far I cant get that to work. With all that said, it tracks VOR’s, ILS/GS really well in this configuration as well as autopilot. In this mode (INTERNAL), I believe the Skyview is just mimicking what the TRIG is displaying on its own screen, that is why you have to activate the OBS mode on the Trig. I’ll update more as I get information back from Dynon and Trig on this compatibility. Hope that helps those that are looking for the combination I have. I’ll post pictures later today. Last note- Like others in on this forum, I’m in IFR training so that is why I needed an additional “Nav” source. I only had the Garmin 355 and was just flying overlays for VOR/ILS’s, now I can track via NAV capability.
Flying Cessna 140
Dues Paid for 23
Last edited by Frogman208 : 09-21-2022 at 03:17 PM.