Earlier I have set up an R18 as master and Rsat as clone (with Rsat connected to the Sat1/18 port on R18), with the DC16 in Standard-mode and this works fine. This equipment is currently installed in a Futura jet. The telemetry from the R18 is handled as it should be and displayed on the radio. If I disconnect the Rsat I have set up a morse-code alarm for PPM signal loss (tied to a voice alarm) and this also works when testing.
Yesterday I was testing the feature with two receivers (R18EX + RsatEX) in dual-path mode on the DC16. The goal was to have the increased redundancy from two transmitter modules. But I think I found an unexpected side-effect/issue that disrupt the telemetry presentation.
I set both receivers in Master mode with jetibox, then I went into dual-path mode and first bound the R18 to the DC16. Then I shut down the R18, powered the Rsat separately and bound it as the second RX. After reconnecting everything, both receivers was active and communicating with the DC-16. BUT the telemetry I had earlier set up and used on the display was now flashing on/off at a high frequency, the only data that could be seen at all was the antenna A1 A2, but it was alternating between "9"-"9" and "-" - "-".
Thinking about it afterwards, it makes a wierd kind of sense that the telemetry is alternating between both receivers since they are both transmitting back. The problem is that only the R18 has any sensors connected to it (MgpsEX, MaxBec2DEX, and MUI30EX), and there is no option in the DC16 for selecting/locking which receiver should supply what, in the way of telemetry. But perhaps there is something I did wrong, I don´t know.
One way of handling telemetry from multiple receivers would be to process them as separate sources, that would also give the possibility to attach more than four external sensors. But perhaps there is a limit to what the DC16 can handle.
Has anyone else tested this? everyones input is welcome!