{"action":"closed","issue":{"url":"https://api.github.com/repos/ArduPilot/ardupilot_wiki/issues/569","repository_url":"https://api.github.com/repos/ArduPilot/ardupilot_wiki","labels_url":"https://api.github.com/repos/ArduPilot/ardupilot_wiki/issues/569/labels{/name}","comments_url":"https://api.github.com/repos/ArduPilot/ardupilot_wiki/issues/569/comments","events_url":"https://api.github.com/repos/ArduPilot/ardupilot_wiki/issues/569/events","html_url":"https://github.com/ArduPilot/ardupilot_wiki/issues/569","id":182000401,"number":569,"title":"AutoTune","user":{"login":"hpcre","id":3989885,"avatar_url":"https://avatars.githubusercontent.com/u/3989885?v=3","gravatar_id":"","url":"https://api.github.com/users/hpcre","html_url":"https://github.com/hpcre","followers_url":"https://api.github.com/users/hpcre/followers","following_url":"https://api.github.com/users/hpcre/following{/other_user}","gists_url":"https://api.github.com/users/hpcre/gists{/gist_id}","starred_url":"https://api.github.com/users/hpcre/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hpcre/subscriptions","organizations_url":"https://api.github.com/users/hpcre/orgs","repos_url":"https://api.github.com/users/hpcre/repos","events_url":"https://api.github.com/users/hpcre/events{/privacy}","received_events_url":"https://api.github.com/users/hpcre/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-10-10T12:16:25Z","updated_at":"2016-11-15T03:36:37Z","closed_at":"2016-11-15T03:36:37Z","body":"[AutoTune](http://ardupilot.org/copter/docs/autotune.html) - \n\nOn this page the following paragraphs are listed twice \n\n`AUTOTUNE_AXES allows control of which axis are to be tuned (useful if the vehicle’s battery life is not long enough to complete all 3-axis). “1” = tune roll, “2” = tune pitch, “4” = tune yaw. Add these numbers together to tune multiple axis in a single session (i.e. “7” = tune all axis)\n\nAUTOTUNE_AGGR : Should be in the range of 0.05 to 0.10. Controls the threshold for D-term bounce back and P-term overshoot. This affects the tuning noise immunity (a higher value is more tolerant to flex in the frame or other disturbances that could trick the tuning algorithm). High values also leads to a tune that rejects external disturbances better. Lower values result in a tune that is more responsive to pilot input.\n`\n"}}
{"actor":{"display_login":"davidbuzz"}}