Standard Mixer Take-2

Just to jump in
a) something looks buggy there. The virt12 thing is something that FDR already reported. I agree it is unnecessary but haven't yet decided if I wnat to remove it as it does serve to allow me to restore a curve later.. But I expected to see '! GEAR0' on the pitch page and on the throttle page. If it looked that way (and the virt12 switch was gone) this wouldn't be too far from how you'd configure it yourself (the main difference being that the std mixer always uses the CYC mappings, and most FBL folks just directly configure their channels.

b) advanced is just what it sounds like: 'advanced'. being able to go from simple to advanced makes it possible to debug what the standard mixer is doing. If we get it to the point where it actually does things in an intuitive way, it could be a good learning tool, but it is not that at the moment. I would say we should not encourage people to move an existing model from simple to advanced until it works in an expected manner (and that is partially what this thread is about), but I see no reason to emove the behavior.

coaster wrote: the Power indicator bar in the main display is
alway on min regardless on the selected tx power.

It works for me in the emu_devo8 and emu_devo10...
Where do you see such behaviour?

FDR wrote: Reboot of DEVO 8 with the latest 5b6a882 version:
Open the throttle or pitch curves of the standard ui and click right on the mode spinbox.
The tx hangs for two seconds and reboots...

So, does anybody else have such tx reboot?

I was able to look at the elf and errors.txt and identify where the problem is. I haven't root caused it yet (nor have I tried to reproduce as yet)

"Try not. Do or do not... There is no try."

Master Yoda

It's not too hard to reproduce: it reboots every time I click right...

It doesn't reboot now with the 3926ed5.
It's strange, because I don't see too much modifications there to fix that...

Or....I could justfix the logic to be intuitive enough that ismple->advanced works as expected. I'm working on it.

I understand the THR config now, and it is fine. It uses a safety switch for thold which is why there is no 4th mixer.

I believe the 4th mixer on the pitch channel is a bug and should be '!GEAR0'

I am working to remove the use of Virt10 so that you don't have unused mixers

I do not yet understand how the GEAR channel is configured

That only leaves the question of whether FBL should use the Cyclic config or direct. Once we're at that point, it may not be hard to have the std mixer do the right thing there too.

Basically, if I can get the standard GUI to set things up the way you would do it in Advanced mode, everyone is happy, and I think that is a reasonable proposition.

No, for both used one switch 'Throttle hold', but 'Pitch curve' has choice to use it (On) or not use it (Off).

Ok, I just committed an update that should make the throttle-hold implementation much more intuitive when examining in the Advanced mixer. I realized I should also do this for the AIL/ELE/RUD D/R settings so that is next.

I've only tested in the emulator so far. I wouldn't be surprised if there are new bugs there so be wary.
Also, I broke backwards compatibility with suvsuv's models. If you load an existing 'Standard' model, you'll get 'invalid ini' on the pitch/throttle page.

Alright, I think I'm done for now. Moving from the standard-mixer to the advanced mixer appears to give a set of mixers that closely resemble the '6ch heli' mixer. From a usability perspective, the main issue seems to be that it uses the Cyclic instead of directly controlling channels A,E,P. I could probably fix that, but I'm not convinced it is worth the effort. I'll think on that some more. I'd like to see some testing on this to see if I broke anything I'm not aware of.

If you want the conversion to be more easily understandable, you could use the "Expo&DR" template for the AIL, ELE, RUDD and Gyro at least...

Don't know if it would raise compatibility issues though.

done. it is trivial to do.

on the topic of showing the throttle as 0 - 100 vs -100 to 100, does it make sense to do on the advanced mixer too?
Issues I foresee:
Do you do this to both the input and output (i.e. for 'INP=THR and CH3)?
If so, the graphs all need to be redrawn to not have a cross-hair when inp = THR
If not, the graps won't be redrawn which may cause some confusion.
Pitch should be -100 to 100 but it uses THR as the input

If we only do this on the standard mixer it is easier. The 'Throttle' graph can be drawn without cross-hairs, and the main page will show the value as 0-100. The down-side is that it means I need to special-case the code in a way I really don't like.

Devo 8 -> Std GUI -> Pitch curve = Invalid model.ini!

Timers have not 'Reset sw:' anymore?