er9x development

[MikeB]

RETA for mode1
RTEA for mode2

I have that done, ready for release. There is a wider issue with some people wishing to change modes at the field while helping to train people using a buddy box setup.

At change of the central point always it is necessary to recalculate values of limits for the size of a subtrimmer.

Have a look at the "AUTO LIMITS" option recently added (bottom of model setup menu). This allows you to set an amount (0-10%) of the sub-trim that is automatically added (internally, not on the screen) to the limits.
So with AUTO LIMITS set to 5.0%, if you set the sub-trim to 4% and the limits are -80% and +80%, these limits will be used as -80% and +80% from the sub-trim position, giving you an actual output of -76%, 4.0%, +84%.

Mike.

[msl272]

automatically added (internally, not on the screen)
Mike.

The such shouldn't be categorically. The program has to be simple. All indications have to be obvious to people.
I put:
autolimits=10
subtrim=10, min =-100 max = + 100.
In the output channel I received values:
from-90 to +110.
Value +110 this direct violation of the top limit (max = + 100). It is possible to see it only on the screen with percent. Violation of limits not seen for the user can be dangerous.

The simple decision it automatically to change min and max at change of a subtrimmer. On the screen possible violations of limits will be visible. It is possible to see and correct dangerous values.

[MikeB]

If you don't like the auto limits then leave the auto limits value at 0 (the default) then the sub-trim has no effect on the limits.
One of the problems with the limits is they are also the "End Point Adjust" values.
A number of users have complained that when they have a sub-trim value then they get less movement on one side and more on the other.

Mike.

[jhsa]

That is true.. I use the limits a little different.
I set the limits for the absolute maximum throw the servos can go without stalling, and then adjust the throws on the rate menu.. As far as my personal taste goes, I would like to be able to adjust the weight independently for both sides, the same as for the expo, using the stick to tell which side to adjust..
This was already discussed before and it was declined For me it makes more sense than using the limits or the rates menus for it.. Limits are as the name says, "limits" that shouldn't be crossed ever, or something could get damaged.. Ok, Auto-limit being an exception in some cases

João

[MikeB]

The dual rate can be set differently for each side, like expo, so this would adjust the stick input rather than the mix weight, but may be suitable when a stick is only used on a single mix.

Mike.

[MikeB]

I think I have code that will put a box round the limits if they are being modified by the auto limits settings (auto limit not zero AND sub-trim not zero).
This at least highights that they are modified.

Mike.

[msl272]

In a manual it is written:
"The limits act both as gains and as absolute limits. The servo will not go beyond the limits you
set here."
Autolimits have to conform to this requirement.

[MikeB]

I need to update the manual then!

Mike.

[jhsa]

[MikeB]

r801 released.
Add telemetry checking, trying to prevent odd jumps in values
Display changed limits when AutoLimits is enabled.
Fix flight Mode labels
Protect PPM sync pulse length from becoming too short.

Mike.

[msl272]

Thanks. Everything works as it is necessary.

Now it is safe to expose a subtrimmer in 10.
It is possible even to increase range till 15-20.

[msl272]

In the "eepe" program it will be convenient to unite screens "trimmers" and "modes" in one. It becomes simpler to adjust a trimmer.

[msl272]

Wishes according to the "eepe" program can be written here?

[MikeB]

Probably best to add a topic here: http://openrcforums.com/forum/viewforum.php?f=17.

I haven't had time to look at combining MODES and TRIMMERS yet.

Mike.

[MikeB]

With language variants coming soon, we will end up with too many different hex files to build.
I propose to reduce the built hex files to:

er9x.hex - with language variants (no templates)
er9x-frsky - with language variants
er9x-128 - with language variants and an option to choose if the THR and AIL switches have been moved

The following in English only:
er9x-ardupilot
er9x-jeti
er9x-nmea

I never quite understood why NO HELI was useful really, from the users view it only dropped a menu screen.

Mike.

[jhsa]

Compile server? maybe much less work?

João

[Kilrah]

I never quite understood why NO HELI was useful really, from the users view it only dropped a menu screen.

It came because of people complaining of having to step over that page they had no use for...

Sent via mobile

[jhsa]

I don't see the problem of having it there if it doesn't save any flash or memory.. Just don't use it if you don't need it..

João

[ReSt]

A FrSky version 801 with Heli is 63058 Bytes flash and without Heli (and without Heli templates) it is 61912 bytes flash

Reinhard

[jhsa]

I guess Mike is not going to put more features on the NO HELI version to make use of that flash.. So, what's the point anyway? Only one more version that has to be compiled.. More work for him as no one else is helping..
I start to believe that er9x really needs a compile server like opentx.. then people can choose what they want or not until the flash is full..

João

[MikeB]

The FrSky version (which doesn't have templates) is 61398. This is using V4.8 of the compiler. Take off the HELI and it is 60908.

Mike.

[msl272]

The RETA and RTEA modes for GVAR are similarly mixed.
In a mode mode2 I put:
GVAR1 = Etrm thus a variable changes from a trimmer of THR.

[MikeB]

What revision of er9x are you using?
I've just tried this, and it seems to be working correctly. On the GVAR menu (in mode 2), I selected Etrm as the source for GVAR1, and it correctly changed when I use the vertical trim of the right stick. If I change to mode 1, then GVAR1 changes with the vertical trim of the left stick.

Mike.

[msl272]

Control I made in EEPE of 801 versions.

[MikeB]

The simulator in eepe will be fixed in the next revision.

Mike.

[MikeB]

I'm working towards a new release, changes planned are:
M128 version - only one build, new option to set FRSKY MOD DONE - swaps the moved switches in software.
M128 version - select switch in menus by moving required switch
Voice for over 1000, use 3 significant figures not 2
Language builds + language headers - code is in place, if you want YOUR language, I need some translations, English and German done.
Vario sink tones optional
Fix move mix to empty channel 1
Set default switches by setting switches and pressing MENU - saves flash
Flash savings, various small savings

I have installed a M128 modified board in one of my transmitters, it's working without the FrSky mod, THR and AIL switches are correct, I now need to do the FrSky mod, and test the software selection for the switches works. This is delaying the completion of the testing of the release.

I should be able to consider further additions to the M128 version now I have a unit on which to test them.

Mike.

[jhsa]

Thank you very much Mike.. Top as always

João

[MikeB]

Release now committed, eepe, eepskye and ersky9x also committed.

Mike.

[MikeB]

I'm looking to add the option to use a pot as a volume control. I think this would be useful. I usually turn the volume down when using the Tx at home, then need it turned up when I go to fly.
My feeling is this is a radio option rather than a model option. I could easily do this either way.
Also, if a pot is allocated to volume control, then you can't really use the pot for pot scroll, can you?

Any comments/observations/suggestions?

Mike.

[jhsa]

That is a nice feature.. Thanks Mike.. What about making it available only if you are on a main screen.. you don't use pot scroll there..

The problem on making it a radio option is that you can't use that pot for anything else like controlling a servo, right?
Or maybe a combination? some key, popup (adjust volume), popup away after a second or so if no/after values were changed.. It also doesn't have to be with a pot..


Radios with encoder, we could use it when on main screen to adjust the volume.. the problem is if the encoder is used for moving a servo for example..same as with the pot

João