The manual for DEVO 10, Section 9.5 (Trims and Virtual Inputs) says:
...If the ‘Input’ field is set as a channel or virtual-channel output, the value is applied directly to the channel output.
In this case, the selected ‘Trim +’ and ‘Trim -’ buttons can operate as a virtual stick to control an output channel.
I, like many others, use this method to control the V-Bar gyroscope.
In my case, the signal is transmitted via Сh5, control is performed by the Top-Right trim (TRIM_R).
To display the GYRO signal in V-bar units (0 ... 128 instead of -100 ... + 100) on DEVO screen, I use the virtual channel (virtchan7) with curve 1-to-1, scalar = 64, offset = 64.
[trim5]
src=Ch5
pos=TRIM_R+
neg=TRIM_R-
step=10
value=2,0,0
[channel5]
scalar=98
template=simple
[mixer]
src=AIL
dest=Ch5
scalar=0
curvetype=fixed
[virtchan7]
name=Gyro-D
template=simple
[mixer]
src=Ch5
dest=Virt7
scalar=64
offset=64
But the mixer, whose source is the channel with the trimmer, does not work correctly.
This mixer ignores the type of the curve and scalar.
You can specify:
Mixer of any type: Simple or Complex.
Any curve: 1-to-1, Fixed, Min / Max, 0 / Max, EXPO, Multi-point b, etc.).
Any scalar: (-100 ... + 100).
In either case, the mixer output will use the 1-to-1 curve, scalar = 100, and the specified offset.
In the case of the Fixed curve, Min / Max, 0 / Max, the specified scalar will be added to offset.
For myself, I solve this problem in two ways:
1) By using an intermediate channel (for example Trimmer -> Ch5 -> Ch7 -> Virtchan7):
[channel7]
template=simple
[mixer]
src=Ch5
dest=Ch7
scalar=0
curvetype=fixed //Note that the curve is Fixed, the curve can be any!
[virtchan7]
name=Gyro-D
template=simple
[mixer]
src=Ch7
dest=Virt7
scalar=64
offset=64
2) Complex mixer with two pages:
[virtchan7]
name=Gyro-D
template=complex
[mixer]
src=Ch5
dest=Virt7
scalar=-100 //Scalar can be any!
curvetype=expo //Note that the curve is EXPO, the curve can be any!
points=0,0
[mixer]
src=Virt7
dest=Virt7
scalar=64
offset=64
usetrim=0
Why is that? This behavior looks like an error.
The firmware is last night build, but this effect I have been watching for a long time, incl. in Deviation 5.0.0
The model file is attached.
