Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trainer settings per model and not system wide #4916

Open
1 task done
Papa-Echo opened this issue Apr 23, 2024 · 4 comments
Open
1 task done

Trainer settings per model and not system wide #4916

Papa-Echo opened this issue Apr 23, 2024 · 4 comments
Labels
enhancement ✨ New feature or request

Comments

@Papa-Echo
Copy link

Is there an existing issue for this feature request?

  • I have searched the existing issues

Is your feature request related to a problem?

I am the instructor in our club and I have several students for quadcopter (FPV) flying and for FPV planes. The problem is that OpenTx and Edge-TX only have one setting for Instructor/Student in the SYS menues.

Describe the solution you'd like

I want to ask for a model specific Instructor/Student page.
The reason is that I teach several students on the same day. One student is a beginner and I limit his % to 50. Then I have a more advanced student who can fly with 100%. The next student comes with his own plane or quadcopter and has a different order of channels. Or the calibration needs to be changed.
Every time I need to change this SYS page.
It would be much better if I could set up a model for each student and set specific values for the Instructor/Student mode.

Describe alternatives you've considered

This model trainer page could be added to the first model page if Instructor is selected.

Additional context

No response

@Papa-Echo Papa-Echo added the enhancement ✨ New feature or request label Apr 23, 2024
@pfeerick pfeerick changed the title Trainer settings per modell and not system wide Trainer settings per model and not system wide Apr 23, 2024
@pfeerick
Copy link
Member

Sounds like another candidate for the global/model level settings paradigm being introduced.

@sande005
Copy link

I noted in a past that having a few system trainer configs, that could be assigned to any model would be beneficial - ie "Bobs Radio, "Sue's Radio" that then could be selected (perhaps even by a switch) for a particular model. OP carries this a step further and makes it all model specific. So a complete model for Sue and another for Bob. Can be limiting if the Instructor has several different models he will be using as a Master with the same students. (I solved the rate problem by putting "low" on a dial, and then I can adjust the actual weight in the air to what suits that student).
The second example begs whether the students own plane/radio will be the master, or if the Instructor will setup and bind a new model so he can be the master. If the first case, then the setup for the slave TX has to be done in the student radio - which this proposal doesn't solve. OR beyond the work of duplicating/binding a new model in the Instructor radio, then either the OP's proposal or my variant will assist.
Mine, of course, seems to follow the design parameters of keeping Sources distinct from use of those sources. Kind of like when Inputs was separated from the Mixer way, way back in the early days.

@raphaelcoeffic
Copy link
Member

@sande005 the profile idea would be nice, indeed. In general, the trainer config is a bit weird right now. Parts of the settings are radio settings, some others are under model settings, and there are 5 different places to configure simple things. I'd really prefer some one-stop shop, rather than this complex setup.

@sande005
Copy link

@raphaelcoeffic - I agree with you, a one-stop config is generally preferable. All of you are doing amazing work. It will be interesting to see what solutions you can come up with for this classic one-to-many and many-to-one problem! Whatever you do, rip up and throw away the current code in Companion for Trainers - it is very messed up (but was long,long ago in OpenTX also)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ✨ New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants