zugbug007 / opentx

Automatically exported from code.google.com/p/opentx
0 stars 0 forks source link

weight and offset cannot go more than 500 units #180

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Which board (stock / gruvin9x / sky9x / Taranis) are you using?
Stock Taranis batch 1, gimbals replaced, 2p switch moved from rhs to lhs

What is your openTx FW version?
2834 / 2013-10-29

What is your openTx EEPROM version?
Latest 07/11/2013

What steps will reproduce the problem?
Read below

What is the expected output? What do you see instead?
For a source (either switch or pots etc) and assuming the range is -100 to 100 
I want to have a mix for a computed channel range (to change the value of a 
gvar from 100 to 80.
to do that I need to have weight -10 and offset -900
However weight and offset cannot go more than 500 units
can we increase both weight and offset value range to 999 units please?

Original issue reported on code.google.com by cklea...@gmail.com on 7 Nov 2013 at 11:23

GoogleCodeExporter commented 8 years ago
No. But you can use a curve to set your gvar to the desired range :)

Original comment by bernet.a...@gmail.com on 8 Nov 2013 at 8:25

GoogleCodeExporter commented 8 years ago

Original comment by bernet.a...@gmail.com on 10 Nov 2013 at 9:07

GoogleCodeExporter commented 8 years ago
To change from -100/100 S1 input to 100/80
1) Setup up a virtual channel with S1 as the input, going through a curve
CH14 (+100%)S1 Curve(Curve 1)
2) Setup up the curve as a 3 point one with the values 100,90,80
3) Tie the Gvar to the virtual channel in the Custom functions page

FSW1 ON Adjust GV1 CH14
This works, however I get a range on the gvar of 81 to 102 both in C9x and on 
the radio. I had to change the curve to 98,89,79 and then it works. Rounding 
errors perhaps?

a very big workaround and I still think it would have been simpler to increase 
the range.

Original comment by cklea...@gmail.com on 11 Nov 2013 at 12:53

GoogleCodeExporter commented 8 years ago
increasing range means wasting a huge amount of eeprom for a feature that is 
barely requested...

Original comment by romolo.m...@gmail.com on 11 Nov 2013 at 1:04

GoogleCodeExporter commented 8 years ago
Not sure if you do something similar, but for engineering tasks when I have to 
write fortan or matlab code, before I do any math I process my data to 
initialise my size of array/matrices. From what you said opentx at the moment 
has range for all sources from-500 to 500. All im saying is allow more range if 
you need it for programing but manage the range for your source to use 
resources efficiently. 

Original comment by cklea...@gmail.com on 17 Nov 2013 at 1:23