Input of virtual channels not visible in mixers?

Hello,

my name is Thomas, I am from germany. Recently I got involved with DeviationTX, and I think I have understood most things.

One thing irritates me - example from my config:
This is an extract of a NanoQX config that simulates an off-on-off sequence to switch between blue and red flight mode.

When I enter channel view mode in transmitter, everything works. But when I enter mixers of channel 6, the input channel seems to stay in the middle, although it actually works like programmed. The channel movement is not displayed in the mixer curve. When using stick or analog AUX input as source, you can see the channel position move as you move stick or AUX. Why does this not work for virtual channels?

curious greetings from Germany

ThomasC

It's taking the current mixer input and processing that value via the current mixer curve.

The screen is being refreshed but for some virtual channels the displayed value remains zero.

I'll look into it further.

Off topic, but I set up my NanoQX to toggle flight modes on the flight mode switch, and it didn't stay in sync. That meant I'd be pulling the switch the wrong way to change flight modes, which also didn't work. Maybe your version will work better, but I went a different way with this.

The trim switch buttons features were designed specifically to deal with situations like this. In fact, the NanoQX flight mode was the reason they were requested in the first place.

I've got mine set up so that the ENT button causes the blue/red flight mode to change. I've set up a second trim on the same button that tracks the parity of the number changes, and displays a toggle icon on the screen indicating which mode it thinks the NanoQX is in. I did that mostly to see if I could, but haven't really used that icon while flying.

If you'd like to see how that's done, I'd be glad to either share my config or walk you through setting it up.

@mwm: to simply toggle the desired mode by tapping a key was my first thought. In fact "mode sync" can be problematic directly after turning on the transmitter (this is also true for the MX-20 I normally use to fly the Nano QX), the sequencer seems to require initializing first by toggling Fmode0/Fmode1/Fmode0 once after switching on. And you have to take care to plug in flight battery only when Fmode0 is active.

My idea behind this was the fact that in blue mode I need 100%/125% D/R (at least), and in red mode I need 60%/80%, so my Dualrate follows flight mode AND I am still able to change Dualrate between indoor and outdoor settings.

Unfortunately, I currently have no access to the Devo10 I used to learn Deviation programming - it is not mine, I still have the old Devo7 for any Devo RX.

Have fun

ThomasC

I would love to see how you track the state of the toggle. I have been combing the site to see how to display a toggle that would tell me what Deviation thinks is the state of the video camera. In the 2X2 model ini the typical setup is to use the left vertical trim as a momentary switch to snap a photo (trimLV+) or to trigger the video on and off (trimLV-). I can capture the change and invert the switch value, but I can't get the change to stay because of the "momentary" state of the trim switch.

I would appreciate a look at your work.

Haven't saved it yet because it was just an experiment, but it's straightforward. I think I'll do it for my v383 video, though. If you have any problems, ask and I'll upload that model file for you to look at after I'm done.

Anyway, you set up a another virtual channel for use as a trim switch. Then you set up another trim with trimLV- as the button. Make the step toggle, not momentary. You then set up a toggle icon using that virtual channel as the switch. My Devo6s always powers on in the same state, so just make the power on state show your "video off" icon, and the other one show your "recording" icon.

Thanks! That sounds like a good approach... I'll work on that and see how far I get!

That worked great. I had no idea I could use the same physical trim switch for more than one purpose! One more really amazing feature I've learned this week. Thanks so much for your guidance.