Charlie,
The D10A without an H34 only has a single serial port. It is used for software updates and anything else that you are going to connect to the D10A directly, like a PC, GPS, NAV receiver or anything else. You have to provide some way to switch between these uses, (like a rotary switch on the panel) if that single input is going to be used for different things.
From the D10A Installation Manual;
Page 3-5 "The SL30 can be used as a VOR, localizer, or ILS (localizer + glideslope) source for the HSI."
Page 3-6 "Connect the GPS or SL30 transmit line into pin 22 on the DB25 connector. This is the same Serial Rx line that is used for firmware updates. You will need a way to disconnect this when you plug your EFIS into a PC for firmware updates and checklists."
The Apollo/UPS-AT/Garmin SL30 NAV/COM can be connected directly via serial. The manual doesn't call out the VAL NAV2000. According to VAL's website description, the NAV2000 mimics the SL30 serial communication protocols. It looks like the MGL N16 with one of their control heads can output SL30 serial too. It's less clear if the Garmin GNC 255 will work. Garmin claims "Legacy" SL30 compatibility but their manual only talks about input compatibility (like frequency control, etc.).
Except for the SL30 which Dynon has tested, I'd take all the other manufacturer claims with a grain of salt. If you land on a solution, contact the manufacturer's tech support and ask them specifically what part of the SL30 serial protocol they implemented and if they have users that have interfaced them successfully with the D10A.
Apollo/UPS-AT/Garmin, from what I've been told, never published a protocol spec for the SL30 serial interface and never cooperated with any other manufacturers (including Dynon) to implement the protocol. Apollo was apparently the first to come out with a serial interface that got rid of a dozen or more analog wires to do the same job. It's definitely a winner, so others reverse engineered the protocol and adopted it.
- Bill