GVARS management with flight phase

[GoogleCodeExporter]

Please see screenshot attached.

The idea is to have, in only one screen, all the values that can have all 
GVARS. In benefits, that distinguishes GVARS form the flight phase menu.

Original issue reported on code.google.com by f.ague...@wanadoo.fr on 10 Nov 2012 at 5:28

Attachments:

• GVARS.png

[GoogleCodeExporter]

But on ARM it will be hard to fit 9 columns...

Original comment by bernet.a...@gmail.com on 10 Nov 2012 at 6:35

[GoogleCodeExporter]

Screenshot from Romolo

Original comment by bson...@gmail.com on 12 Nov 2012 at 2:51

Attachments:

• variables.png

[GoogleCodeExporter]

Random notes:
- I like the idea of a dedicated screen (Romolo)
- I like presentation with all VG as horizontal lines (Franck)

But we have to keep in mind that:
- VG names are 6 chars wide
- VG values can be "-1024"

So my conclusion is ...
- It will be ok on X9D (212px width) ;)
- We need to scroll horizontally on other boards

Original comment by bson...@gmail.com on 12 Nov 2012 at 2:56

• Changed state: Accepted

[GoogleCodeExporter]

I like the idea of a dedicated screen too... I hardly dared to dream of it ;)
But, one question : all software use +/-100% scale, so why +/-1024 for GVARS ?

A little additition, perhaps already planned : it would be perfect if the 
ongoing GVARS and FP are shown in bold.

Original comment by f.ague...@wanadoo.fr on 12 Nov 2012 at 8:34

[GoogleCodeExporter]

The mixer, it goes up to 500% today!

Original comment by bson...@gmail.com on 12 Nov 2012 at 8:36

[GoogleCodeExporter]

OK, this is since the issue #146... but I never understood what it was for, 
especially now with raw inputs of sticks (without D/R). I'm probably wrong, as 
I don't really know his need, but perhaps this feature could have solved the 
problem of Greg without expanded range of GVARS.
I also think that a so important range could be dangerous for in flight 
adjusting.

Original comment by f.ague...@wanadoo.fr on 12 Nov 2012 at 8:58

[GoogleCodeExporter]

For example, if you want one side of the stick to result in the entire servo 
throw, it's useful to be able to set 200% weight. 
There was also one guy who was doing some "math" and needed to set a 400% mix. 
Mixers are limited to 125% for EEPROM reasons, but GVARS were an easy solution 
to get around that when needed. 
It's not a problem for in-flight adjusting, as you need to explicitly set it up 
yourself to go that far. 

Original comment by bernet.a...@gmail.com on 12 Nov 2012 at 9:20

[GoogleCodeExporter]

If you use a potentiometer to adjust a GVAR in-flight, the physical accuracy 
(what you can really do with your fingers...) is 4 time less with +/-500 range 
(or 8 times (!) with +/-1024) than with the normal +/-125 range. This will much 
complicate the setting of some usual couplings that have small rate values, 
like motor, flaps or airbrakes to elevator compensation, snap-flap, wing camber 
or differential (as, for all, their normal rate is around 10-20%).

For your example, I'm sorry but I not sure I understand, please could you 
explain more ?

Original comment by f.ague...@wanadoo.fr on 13 Nov 2012 at 8:43

[GoogleCodeExporter]

No, because the pot range isn't +/-500.
A pot gives -100% to +100%. When you set a function switch with "Adjust GVx 
P1", then the value of P1 is simply copied into GV1. So this way, you still 
have the normal +/-100 range. 

If you want to in-flight adjust a GV between +/-500 you'll need to set it up 
yourself using 2 GVs and a free channel.
For example:
- GV1 = 500
- CH16: GV1% P1
- A function switch with Adjust GV2 CH16. 

Then you'll have GV2 in-flight adjustable between -500 and +500 with P1.

So - it allows for >125 values for those who need it, but doesn't change 
anything for the others. 

Original comment by bernet.a...@gmail.com on 13 Nov 2012 at 9:10

[GoogleCodeExporter]

EDIT: Not even actually. In-flight adjsutment doesn't work beyond +/-125%

The +/-500 range is useable just as a fixed value, like above to set a fixed 
weight > 125% for example.

Original comment by bernet.a...@gmail.com on 13 Nov 2012 at 9:16

[GoogleCodeExporter]

OK, I understand a little better now, thanks !
Just a last question : does it works the same with rotary encoders ?

Original comment by f.ague...@wanadoo.fr on 13 Nov 2012 at 9:18

[GoogleCodeExporter]

"actually", tu veux dire "actuellement" ? 

Original comment by bson...@gmail.com on 13 Nov 2012 at 9:20

[GoogleCodeExporter]

actually = en fait, c'est un faux-ami ;)

Original comment by bernet.a...@gmail.com on 13 Nov 2012 at 9:35

[GoogleCodeExporter]

For the moment I only enabled this feature when LCD_W >= 260

Original comment by bson...@gmail.com on 18 Jan 2013 at 9:56

• Changed state: Fixed

Attachments:

• snapshot_06.png

[GoogleCodeExporter]

Is there a way to turn off the pop-up window when the gvar value is updated. 
I'm using it to store a throttle and rudder value for a Throttle Hold - 
pan/tilt mix and the pop-up is just annoying 

Original comment by m...@jsmtech.com on 2 Nov 2013 at 5:37