Dependence altitude gain and throw amplitude of ailerons, elevator, rudder CC3D

[kazmod1]

Hello, I hope that this site is still at live and I can count on your help.
I have remark that changes in gain attitude (perhaps rate, other as well) influence throw of control surfaces . In my case
I'm using CC3D . What I can do to avoid this.
When gain is important throw of ailerons (other ) are large, but when gain is small the throws are as well small.

I like very much program Librepilot and I still using CC3D controller. Hope that I wrote correctly my pull.

Regards, K.Wirpszo

[paul-jewell]

Hello, I hope that this site is still at live and I can count on your help. I have remark that changes in gain attitude (perhaps rate, other as well) influence throw of control surfaces . In my case I'm using CC3D . What I can do to avoid this. When gain is important throw of ailerons (other ) are large, but when gain is small the throws are as well small.

I like very much program Librepilot and I still using CC3D controller. Hope that I wrote correctly my pull.

Regards, K.Wirpszo

The main repo for development is on bitbucket, here: https://bitbucket.org/librepilot

I can't comment on your pull request as I haven't reviewed it, however I am sure your contribution will be welcomed! I recommend you head over and submit your PR there.

Best regards,
Paul

[theothercliff]

This looks like you are attempting to check in:
"[kazmod1] wants to merge 782 commits into [master] from [next]"
When I think about that... 782 commits. 😮 782 full sets of changes (multiple files for each one?) That doesn't sound correct to me.

I am far from a git guru 😄 and it has been a long time since I made a pull request (I read my notes when I need to do something like that), so given that...

That number 782 sounds like you are using 16.09 or something just a little later, and trying to put that on top of next. Or there is some other version / commit issue.

LibrePilot has only one branch and that is the tip of next (although I personally think it would be nice to see some backports to an updated 16.09 that is still compatible with the original 16.09, I do this for my own use). Generally, to check something in, you code and test it in your own pull of next (which currently is 16.09 + 796). When it is all working, you push it back to your own version of next which should be the current next plus your changes. You then do a pull request on that and after being voted to be OK (a non-trivial part, there are quite a few pull requests in this part of the process), someone with super privileges will merge it into the global next.

The description of this change sounds like it is fixing something that is working as it should? 😮 When you say "gain" I assume you mean PIDs. First of all, the Output page, min, neutral, max are adjusted for max throw without binding (also perhaps limited to some other limits like max recommended control deflection angles). That way, no matter what other configuration you change, it will never make the servos / surface move farther than that (but be aware that if it actually moves this far and hits the "stop" in flight that the PID is no longer working as it should and enters another form of wind-up / oscillation). Next, the definition of PIDs says that for a given error (like a bank angle that is not level but the sticks are centered), the higher the P term, the farther the ailerons (or whatever causes roll, that is differential motor thrust in multicopters) move. Of course the I term adds to that and winds it up slowly, farther and farther, till it hits I-Limit or Beta.

If you like, this could be discussed at forum.librepilot.org

[paul-jewell]

@kazmod1: to add to Cliff's comment, more information about contributing to development can be found here: https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/84672528/Git+Workflow

You are definitely welcome to join the development team!

[kazmod1]

<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} -->Hello  Paul, I will be happy to joint the devollepement team but you  must to know that right know I’m not able to program. If I can make other thing, yes I will be happy to help. Thank you for your help and this proposition, Kaz Wirpszo  Sent from Mail for Windows From: Paul JewellSent: Monday, May 23, 2022 3:04 AMTo: librepilot/LibrePilotCc: kazmod1; MentionSubject: Re: [librepilot/LibrePilot] Dependence altitude gain and throw amplitude of ailerons, elevator, rudder CC3D (PR ***@***.***: to add to Cliff's comment, more information about contributing to development can be found here: https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/84672528/Git+WorkflowYou are definitely welcome to join the development team!—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>