-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Auxiliary Function Switches #1848
Comments
This is a MP display issue which is on the to-do list to fix before Copter-3.7 goes out. I have to ask though why is Copter-3.7 being loaded onto the vehicle? The latest stable is 3.6.9 and we highly recommend sticking with this version instead of the development version which hasn't undergone any beta testing yet. As a side note, issues should really be raised first in the support forums so I'll close this issue. Thanks in any case for using AP! |
Hello Randy,Thank you for replying to my issue. I am new to this and didn't realize that I was supposed to use the support forum. In future, I will use the support forum.You people are doing a wonderful job with this project. I have been able to build a working quad from scratch. I will persist with the autotune and I know that I will eventually get it to save. I will reload version 3.6.9 and use it. Thank you for taking the time to help me.Best regards,Tony NewtonSent from my Galaxy Tab® A
-------- Original message --------From: Randy Mackay <notifications@github.com> Date: 2019-07-18 9:27 PM (GMT-04:00) To: ArduPilot/ardupilot_wiki <ardupilot_wiki@noreply.github.com> Cc: Tonynewton <Tnewton99@gmail.com>, Author <author@noreply.github.com> Subject: Re: [ArduPilot/ardupilot_wiki] Auxiliary Function Switches (#1848) This is a MP display issue which is on the to-do list to fix before Copter-3.7 goes out. I have to ask though why is Copter-3.7 being loaded onto the vehicle? The latest stable is 3.6.9 and we highly recommend sticking with this version instead of the development version which hasn't undergone any beta testing yet.
As a side note, issues should really be raised first in the support forums so I'll close this issue. Thanks in any case for using AP!
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "#1848?email_source=notifications\u0026email_token=AJC7FPB3DBFEA6J5DQGICELQAEC7PA5CNFSM4IE6BZ22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2KGVOA#issuecomment-513043128",
"url": "#1848?email_source=notifications\u0026email_token=AJC7FPB3DBFEA6J5DQGICELQAEC7PA5CNFSM4IE6BZ22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2KGVOA#issuecomment-513043128",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
Auxiliary Function Switches - Describe the issue/suggestion and improve the title. Please keep a link to the original article if relevant.
I am trying to get autotune working. I am unable to access the switches from the Extended Tuning tab but the RC7Opt and RC8Opt buttons are grey and don't respond to the mouse pointer.
In the Full Parameter List tab, I was able to set the AUTOTUNE_AXES TO 1 (for roll tuning only). I set AUTOTUNE_AGGR to 0.1 and AUTOTUNE_MIN_D to 0.001
The copter did the roll tuning and beeped when it was done. I left switch 7 high, landed and disarmed. The new PIDs were not saved. Does this have anything to do with the grey fields in the Extended Tuning Tab. How does one activate the RC7Opt and RC8Opt buttins?
The text was updated successfully, but these errors were encountered: