Going into servo menu sets servos to very low values.

[GoogleCodeExporter]

Which board (stock / gruvin9x / sky9x / Taranis) are you using?
Taranis

What is your openTx FW version?
2897

What is your openTx EEPROM version?
216

What steps will reproduce the problem?
1. Create new model
2. Go into "Servos" menu.
3. All servo throws are set from 2.4 to -2.4.  Changing them only allows a 
max/min of 12.9/-12.9, not the full 100+.

What is the expected output? What do you see instead?
Shouldn't change servo values at all from defaults when going into servo menu - 
DANGEROUS!
Servo max/min should at least allow +/-100

Please provide any additional information below.
Seems to have been a problem in builds newer than the current release.

Original issue reported on code.google.com by zebb...@gmail.com on 18 Dec 2013 at 3:57

[GoogleCodeExporter]

2897 is work in progress, not a release. Do NOT use anything after r2856 for 
anything but testing unless you know what you're doing, EEPROM format has 
changed and will still change before next release, and conversion is not fully 
implemented yet so things WILL get broken. 

However I don't recall seeing such an issue with my test builds. Can you list 
your compile options here? Maybe the problem only happens with a particular 
combination. Post your binary too. 

By the way the svn repo is deprecated, further work is being done on github:
https://github.com/opentx/opentx

Original comment by bernet.a...@gmail.com on 18 Dec 2013 at 1:06

[GoogleCodeExporter]

Thanks Bernet,

Was running the latest revs for DSM2 capabilities on Taranis.  Tried the github 
master, and it works just fine!  Lacks some of the new features/interface, and 
is also the older 215 EEPROM version which is compatible with the current 
release of Companion9x.  Perfect!  I think my issue is resolved.

For your interest, I was (and am) building with options PCB=TARANIS and 
DSM2=PPM.  I have a Jenkins autobuild system running daily, which I've now got 
building the SVN and github versions.  The one I had issues with was at least 
r2898.  You can check my builds at http://secops.wwworks-inc.com/opentx.  The 
dated versions are the github versions, as Jenkins doesn't seem to have an easy 
way to extract the build number - nor do github build numbers help anyway.

Original comment by zebb...@gmail.com on 21 Dec 2013 at 2:54

[GoogleCodeExporter]

Hi,

A normal make command for Taranis would be:
make PCB=TARANIS HELI=YES GVARS=YES AUTOSWITCH=YES PPM_LIMITS_SYMETRICAL=YES 
PPM_CENTER_ADJUSTABLE=YES DBLKEYS=YES AUTOSOURCE=YES

I would imagine the issue only appears when compiling with no GVARs. There have 
been changes there so it's totally possible something got broken but that case 
was not tested yet. Would be good if you could open an issue on github for it. 

Original comment by bernet.a...@gmail.com on 21 Dec 2013 at 8:51

[GoogleCodeExporter]

Thanks again,

Adding the additional build options fixes this issue.  I assumed that 
PCB=TARANIS would include some Taranis default build options.  I should have 
checked the Makefile to be sure...

However, I don't see the reversed "I" icon beside sticks in the Sticks menu.  
Was this pulled from the new source, or is it disabled when adding one of the 
build options you recommended?

Original comment by zebb...@gmail.com on 22 Dec 2013 at 3:07

[GoogleCodeExporter]

The I is for the new virtual inputs. This isn't fully tested as of yet and 
companion9x support is inexistant, which is why it's not in the master (= 
release) branch. You'll find it in next (experimental/for testing).
C9X support needs to be done first, then the whole set of changes needs a lot 
of testing, then only will it be released. 

Original comment by bernet.a...@gmail.com on 22 Dec 2013 at 11:19

[GoogleCodeExporter]

Original comment by bernet.a...@gmail.com on 28 Dec 2013 at 9:11

• Changed state: Fixed