Hi Guys,

Interesting discussion. As a long-time Futaba user, I can confirm that there is no way to use telemetry values to activate any actions in the TX. Perhaps others can comment on any other brands that can or can't do this.

As has already been pointed out, Jeti systems can do that, you can create a "virtual channel" (they call them telemetry controls) driven by a telemetry value that can be included in TX functions such as mixers, switches, etc and could in principle do what you are wanting to do. I don't know if the new Powerbox radio can do that, if anyone knows that would be an interesting data point to have.

Though I have never had any issues with link reliability with Futaba, I was frustrated with their total lack of innovation, and have switched about half of my planes to Jeti. One of the main reasons was what you could do with their telemetry, and this is a good example of the sort of problem that drove my switching. And LA Jetguy already has been flying the swing-wing function!

Having spent the summer with the Jeti radio, and looking at a lot of logs of telemetry data from actual flights at many different fields, I would offer one small caution. There are "gaps" in the telemetry data that comes down to the TX during the flight. You can see them clearly in the log files. Maybe 1-3 second gaps 5-6 times during a flight where there is no telemetry data on some telemetry values. Maybe due to antenna orientation, but no way to be sure what the actual cause might be. Jeti I think knows this happens (they seem to be very good engineers), and has included some functionality in the TX that mitigates the impact for these gaps. For example, (see page 112 in the DX manual) you can set up filtering, and account for occasionally missing data in the telemetry by only responding to triggers after so many seconds etc. For example I implemented a TX-based pneumatic gear failsafe using telemetry control from the air pressure sensor and used the feature so that the gear would only go down after low air pressure was reported for more than 5 seconds. So a 1-3 second gap in air pressure data would not drop the gear. The tradeoff is a 5-second delay in responding to a leak. No free lunch :-)

So while it is quite rational to worry about coupling critical flight controls to telemetry, your case might fit into the "doable" category. The delay you can set (e.g. only sweep the wing forward if the airspeed is less than 80 mph for 5-10 seconds .. only sweep the wing back if the airspeed is greater than 100 mph for 5-10 seconds) would give you some hysteresis. Then the wing would not be sweeping back and forth willy-nilly. I suspect that would work and would be relatively safe. For further safety you could have a 3-pos switch .. one end is wing forward, other end is wing back .. middle is "automatic" based on airspeed. So no matter what happens you can failsafe to a known configuration. At least that's what I'd do... and David did a similar thing in his setup.

You would want to stare at a bunch of telemetry log data and make up your own mind of course... you're the only one who can decide for your plane what level of function and "coolness" is worth what level of risk.

Dave