GUI

FDR wrote: A change request:
Could you make the model page to be the last (or we can say the -1. to the left), so it would be only one click away from the default (mixer) page.
I still think that the mixer page is the most used one, so it should be the first when we enter the model menu, but the second more important is the model page.
I would be like if the model page is the first, mixer is second, and then the rest, just we always start with the second page...

Done. I also pulled your other changes.

There are some strange new bugs.

In a source select box there are virtual channel up to Virt10, but on the mixer list there are 14, which behave weird: the 11. is a complex mixer, but if I want to set it back to None it hangs the program. Furthermore the None option is the first to left, not third after expo and simple.
The last 14. virtual has "Unknown" mixer type.
I know that they can be bad model data, but even then they shouldn't crash the program.

EDIT: ...that was in the emulator with the defaul model...

On the mixer setup page in the mixer type select box the are Cyclic1-3, but they do nothing. What are they good for?

FDR wrote: On the mixer setup page in the mixer type select box the are Cyclic1-3, but they do nothing. What are they good for?

They do something. They are basically predefined (non-editable) mixers, that use the swash type to mix the 1st 3 virtual channels. If you select a cyclic template, you will see the names of the virtual channels change accordingly.

FDR wrote: There are some strange new bugs.

In a source select box there are virtual channel up to Virt10, but on the mixer list there are 14, which behave weird: the 11. is a complex mixer, but if I want to set it back to None it hangs the program. Furthermore the None option is the first to left, not third after expo and simple.
The last 14. virtual has "Unknown" mixer type.
I know that they can be bad model data, but even then they shouldn't crash the program.

EDIT: ...that was in the emulator with the defaul model...

fixed

I cannot reproduce that virtual channel renaming...

BTW the binding button is visible when no protocol is set.
On the mixer list if I scroll down (no matter if one by one or with long press) and open and close a mixer, the scroll bar jumps up.

FDR wrote: I cannot reproduce that virtual channel renaming...

Select 'Cyclic1' for any of the 1st 8 channels. The 1st Virtual channel is now named 'CYC - AIL' on the mixer page. (It still shows u as 'Virt1' if you try to select it as a source manually though. I have to give that some thought)

Your other issues are fixed

OK, I've got them...
(EDIT: BTW loading the CCPM template were not enough...)

How can one know, which cyclic he have to assign to the aileron, elevator and pitch?
Shouldn't we use the same name for the cyclic channels everywhere to ease to choose from them: CYC_AIL, CYC_ELE, CYC_COL or CYC_PITCH?

FDR wrote: OK, I've got them...
(EDIT: BTW loading the CCPM template were not enough...)

How can one know, which cyclic he have to assign to the aileron, elevator and pitch?
Shouldn't we use the same name for the cyclic channels everywhere to ease to choose from them: CYC_AIL, CYC_ELE, CYC_COL or CYC_PITCH?

I didn't update the CCPM template yet.
Is there a 'standard' way to name the cyclic outputs?
The channels mix (for 120-degree swash)
cyc1 = collective - elevator
cyc2 = collective + elevator/2 + aileron
cyc3 = collective + elevator/2 - aileron

which of those is col, ail, ele?

Good question!

ok I did some testing with the devo firmware and found this:
cyc1 = ele
cyc2 = ail
cyc3 = pitch (channel 6)

I've updated the 6-channel template to have a reasonably realistic setting.

One note is that walkera seems to use a reversed ele (in front rather than in back?). such that the direction is opposite to the normal formula. so you need to set 'ele inversed' on the heli page. This isn't part of the 6ch template though.

I also increased the max default servo throw to 150%. this is the value that Walkera seems to use by default. I still need to go through all the protocols and make sure the >100% throws work for each one.

Yep, it looks much better now!
Now only the default model needs some tweaking...

...and they use the ch7 for the gyro. How does it work with 6ch transmitters, I wonder?

Should we support translating the template names?
It would make it easier for non-english speakers to use. The only downside is that we only have translations for officially supported templates.

Yes, we may support the default ones in the language files, the rest will be named by the users...

PhracturedBlue wrote: I also increased the max default servo throw to 150%. this is the value that Walkera seems to use by default.

No, they use 100% as default, and I think it is the right think to do.
It's only an option to increase it to 150%...

FDR wrote:

PhracturedBlue wrote: I also increased the max default servo throw to 150%. this is the value that Walkera seems to use by default.

No, they use 100% as default, and I think it is the right think to do.
It's only an option to increase it to 150%...

Not from what I see. Theyuse 100% as the range multiplier. They seem to set a hard-limit on throw at 150% (maybe this can also be adjusted upwards I dunno)

For instance, with all values at 100% and trim maex, the max value is > 100%.
Also, with 120-degree CCPM, and all values at 100% the max value is 150%. You can measure this on the servos or by looking at the monitor page.

I don't think Walkera has any concept of a real servo limit that is user controlabale

PhracturedBlue wrote: Not from what I see. Theyuse 100% as the range multiplier. They seem to set a hard-limit on throw at 150% (maybe this can also be adjusted upwards I dunno)

For instance, with all values at 100% and trim maex, the max value is > 100%.
Also, with 120-degree CCPM, and all values at 100% the max value is 150%. You can measure this on the servos or by looking at the monitor page.

Internally I don't know, but on the UI they have 100% default servo adjust, which can be extended to 150%.
May be they normalize after some stages, or may be the 100% here is not the same value as 100% there...

PhracturedBlue wrote: I don't think Walkera has any concept of a real servo limit that is user controlabale

No they have only scaling, but they have two values for the negative and positive halves.

Right. In the Devo firmware, 'Servo Adjust' is the same as my 'scale' value on the channel page in Deviation (except that they allow separate settings for positive and negative). Deviation defaults to 100% just like the Walkera firmware.

They also have a hard-limit at 150% which does not seem to be adjustable.
My 'max' and 'min' values allow adjusting the hard-limit to prevent servo/model damage. They are currently set at 150% just like the Walkera firmware.

Note that the 'limits' don't work when the Rx is doing its own mixing of course since the Tx has no knowledge of it

We need some more usable toggle images...
Here is my first try, but will try to find some better...

EDIT: bmp was not on the allowed list...
There should be an image of gears to warn they are out!

FDR wrote: We need some more usable toggle images...
Here is my first try, but will try to find some better...

Here where?
I don't see them on the forum or in your repo.