|
549 | 549 | "auto_changed_by": "", |
550 | 550 | "old_filenames": ["15_pid_adjustment.param"] |
551 | 551 | }, |
552 | | - "19_notch_filter_results.param": { |
553 | | - "why": "The notch filter(s) configuration depends on real-flight data.", |
554 | | - "why_now": "real-flight data is only available after the first flight", |
555 | | - "blog_text": "Configure the notch filter(s) based on the data collected from the first flight", |
556 | | - "blog_url": "https://ardupilot.github.io/MethodicConfigurator/TUNING_GUIDE_ArduCopter#81-notch-filter-calibration", |
557 | | - "wiki_text": "Managing Gyro Noise with the Dynamic Harmonic Notch Filters", |
558 | | - "wiki_url": "https://ardupilot.org/copter/docs/common-imu-notch-filtering.html", |
559 | | - "external_tool_text": "Ardupilot Filter Review tool", |
560 | | - "external_tool_url": "https://firmware.ardupilot.org/Tools/WebTools/FilterReview/", |
561 | | - "mandatory_text": "100% mandatory (0% optional)", |
562 | | - "auto_changed_by": "", |
563 | | - "autoimport_nondefault_regexp": ["FFT_.*", "INS_GYRO_FILTER"], |
564 | | - "old_filenames": ["18_notch_filter_results.param"] |
565 | | - }, |
566 | 552 | "20_throttle_controller.param": { |
567 | 553 | "why": "The throttle controller is crucial for maintaining altitude and controlling the vehicle's vertical movement.", |
568 | 554 | "why_now": "After the first flight because it depends on the MOT_THST_HOVER parameter, before the second flight so that it can safely use the altitude controller", |
|
581 | 567 | }, |
582 | 568 | "old_filenames": ["19_throttle_controller.param"] |
583 | 569 | }, |
| 570 | + "19_notch_filter_results.param": { |
| 571 | + "why": "The notch filter(s) configuration depends on real-flight data.", |
| 572 | + "why_now": "real-flight data is only available after the first flight", |
| 573 | + "blog_text": "Configure the notch filter(s) based on the data collected from the first flight", |
| 574 | + "blog_url": "https://ardupilot.github.io/MethodicConfigurator/TUNING_GUIDE_ArduCopter#81-notch-filter-calibration", |
| 575 | + "wiki_text": "Managing Gyro Noise with the Dynamic Harmonic Notch Filters", |
| 576 | + "wiki_url": "https://ardupilot.org/copter/docs/common-imu-notch-filtering.html", |
| 577 | + "external_tool_text": "Ardupilot Filter Review tool", |
| 578 | + "external_tool_url": "https://firmware.ardupilot.org/Tools/WebTools/FilterReview/", |
| 579 | + "mandatory_text": "100% mandatory (0% optional)", |
| 580 | + "auto_changed_by": "", |
| 581 | + "autoimport_nondefault_regexp": ["FFT_.*", "INS_GYRO_FILTER"], |
| 582 | + "old_filenames": ["18_notch_filter_results.param"] |
| 583 | + }, |
584 | 584 | "21_ekf_config.param": { |
585 | 585 | "why": "Sometimes the weights of the barometer vs. GNSS altitude need to be adjusted.", |
586 | 586 | "why_now": "Before the second flight so that the EKF can be used to estimate the vehicle's position", |
|
613 | 613 | }, |
614 | 614 | "old_filenames": [] |
615 | 615 | }, |
| 616 | + "27_pid_notch_filter_results.param": { |
| 617 | + "why": "The PID notch filter(s) configuration depends on real-flight data collected with the logging enabled in the previous step", |
| 618 | + "why_now": "Real-flight data with PID notch filter batch logging is only available after the dedicated logging flight", |
| 619 | + "blog_text": "Configure the PID notch filter(s) based on the data collected from the logging flight", |
| 620 | + "blog_url": "https://ardupilot.github.io/MethodicConfigurator/TUNING_GUIDE_ArduCopter#81-notch-filter-calibration", |
| 621 | + "wiki_text": "Managing Gyro Noise with the Dynamic Harmonic Notch Filters", |
| 622 | + "wiki_url": "https://ardupilot.org/copter/docs/common-imu-notch-filtering.html", |
| 623 | + "external_tool_text": "Ardupilot Filter Review tool", |
| 624 | + "external_tool_url": "https://firmware.ardupilot.org/Tools/WebTools/FilterReview/", |
| 625 | + "mandatory_text": "100% mandatory (0% optional)", |
| 626 | + "auto_changed_by": "", |
| 627 | + "autoimport_nondefault_regexp": ["FILT.+", "ATC_RAT_.+_N[ET]F", "PSC_ACCZ_N[ET]F"], |
| 628 | + "old_filenames": [] |
| 629 | + }, |
616 | 630 | "22_quick_tune_setup.param": { |
617 | 631 | "why": "The VTOL-quicktune lua script can safely estimate good PID starting values for the vehicle.", |
618 | 632 | "why_now": "Before the second flight so that the vehicle can be safely tuned.", |
|
968 | 982 | }, |
969 | 983 | "old_filenames": [] |
970 | 984 | }, |
| 985 | + "46_pid_d_ff.param": { |
| 986 | + "why": "The D feed-forward term improves aggressive rate tracking and gives the drone a 'locked-in' feel with minimal control latency", |
| 987 | + "why_now": "After all autotune axes are complete and PID values are finalized, since D_FF is calculated from the final tuned PID response", |
| 988 | + "blog_text": "Calculate angle rate derivative feed-forward gains (ATC_RAT_*_D_FF and PSC_ACCZ_D_FF) to improve aggressive maneuver tracking", |
| 989 | + "blog_url": "https://ardupilot.github.io/MethodicConfigurator/TUNING_GUIDE_ArduCopter#97-angle-rate-derivative-feed-forward-calculation", |
| 990 | + "wiki_text": "", |
| 991 | + "wiki_url": "", |
| 992 | + "external_tool_text": "ArduPilot PID Review Tool", |
| 993 | + "external_tool_url": "https://firmware.ardupilot.org/Tools/WebTools/PIDReview/", |
| 994 | + "mandatory_text": "0% mandatory (100% optional)", |
| 995 | + "auto_changed_by": "", |
| 996 | + "autoimport_nondefault_regexp": ["ATC_RAT_.+_D_FF", "PSC_ACCZ_D_FF"], |
| 997 | + "old_filenames": [] |
| 998 | + }, |
971 | 999 | "40_windspeed_estimation.param": { |
972 | 1000 | "why": "For accurate navigation and stabilization at high speeds and/or in windy conditions", |
973 | 1001 | "why_now": "Because it can only be done after PID tuning is complete", |
|
1016 | 1044 | }, |
1017 | 1045 | "old_filenames": [] |
1018 | 1046 | }, |
| 1047 | + "50_system_id_input_roll.param": { |
| 1048 | + "why": "System identification is required to create a mathematical model of the vehicle", |
| 1049 | + "why_now": "Because the vehicle should be fully tuned (no more PID changes) before a model gets created (that depends on said PID values)", |
| 1050 | + "blog_text": "Configure parameters for the roll axis input system identification to create a mathematical model of the vehicle", |
| 1051 | + "blog_url": "https://ardupilot.github.io/MethodicConfigurator/TUNING_GUIDE_ArduCopter#11-system-identification-for-analytical-pid-optimization-optional", |
| 1052 | + "wiki_text": "Matlab and Simulink IAV scripts for system identification", |
| 1053 | + "wiki_url": "https://ardupilot.org/copter/docs/systemid-model-development.html#identification-of-a-multicopter", |
| 1054 | + "external_tool_text": "ArduCopter Simulink Model", |
| 1055 | + "external_tool_url": "https://github.com/ArduPilot/ardupilot/blob/master/Tools/simulink/arducopter/README.md", |
| 1056 | + "mandatory_text": "20% mandatory (80% optional)", |
| 1057 | + "auto_changed_by": "", |
| 1058 | + "forced_parameters": { |
| 1059 | + "SID_AXIS": { "New Value": 1, "Change Reason": "Inject chip on the input roll signal" } |
| 1060 | + }, |
| 1061 | + "old_filenames": [] |
| 1062 | + }, |
| 1063 | + "51_system_id_input_pitch.param": { |
| 1064 | + "why": "System identification is required to create a mathematical model of the vehicle", |
| 1065 | + "why_now": "Because the vehicle should be fully tuned (no more PID changes) before a model gets created (that depends on said PID values)", |
| 1066 | + "blog_text": "Configure parameters for the pitch axis input system identification to create a mathematical model of the vehicle", |
| 1067 | + "blog_url": "https://ardupilot.github.io/MethodicConfigurator/TUNING_GUIDE_ArduCopter#1112-pitch-rate-mathematical-model", |
| 1068 | + "wiki_text": "Matlab and Simulink IAV scripts for system identification", |
| 1069 | + "wiki_url": "https://ardupilot.org/copter/docs/systemid-model-development.html#identification-of-a-multicopter", |
| 1070 | + "external_tool_text": "ArduCopter Simulink Model", |
| 1071 | + "external_tool_url": "https://github.com/ArduPilot/ardupilot/blob/master/Tools/simulink/arducopter/README.md", |
| 1072 | + "mandatory_text": "20% mandatory (80% optional)", |
| 1073 | + "auto_changed_by": "", |
| 1074 | + "forced_parameters": { |
| 1075 | + "SID_AXIS": { "New Value": 2, "Change Reason": "Inject chip on the input pitch signal" } |
| 1076 | + }, |
| 1077 | + "old_filenames": [] |
| 1078 | + }, |
| 1079 | + "52_system_id_input_yaw.param": { |
| 1080 | + "why": "System identification is required to create a mathematical model of the vehicle", |
| 1081 | + "why_now": "Because the vehicle should be fully tuned (no more PID changes) before a model gets created (that depends on said PID values)", |
| 1082 | + "blog_text": "Configure parameters for the yaw axis input system identification to create a mathematical model of the vehicle", |
| 1083 | + "blog_url": "https://ardupilot.github.io/MethodicConfigurator/TUNING_GUIDE_ArduCopter#1113-yaw-rate-mathematical-model", |
| 1084 | + "wiki_text": "Matlab and Simulink IAV scripts for system identification", |
| 1085 | + "wiki_url": "https://ardupilot.org/copter/docs/systemid-model-development.html#identification-of-a-multicopter", |
| 1086 | + "external_tool_text": "ArduCopter Simulink Model", |
| 1087 | + "external_tool_url": "https://github.com/ArduPilot/ardupilot/blob/master/Tools/simulink/arducopter/README.md", |
| 1088 | + "mandatory_text": "20% mandatory (80% optional)", |
| 1089 | + "auto_changed_by": "", |
| 1090 | + "forced_parameters": { |
| 1091 | + "SID_AXIS": { "New Value": 3, "Change Reason": "Inject chip on the input yaw signal" } |
| 1092 | + }, |
| 1093 | + "old_filenames": [] |
| 1094 | + }, |
1019 | 1095 | "42_system_id_roll.param": { |
1020 | 1096 | "why": "System identification is required to create a mathematical model of the vehicle", |
1021 | 1097 | "why_now": "Because the vehicle should be fully tuned (no more PID changes) before a model gets created (that depends on said PID values)", |
|
0 commit comments