You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
common, copter: document removal of TradHeli flybar/ext-gyro ACRO passthrough (32430)
ArduPilot PR #32430 removed the H_FLYBAR_MODE, H_GYR_GAIN, and
H_GYR_GAIN_ACRO parameters along with mechanical flybar and external
tail gyro passthrough support in ACRO mode for single-rotor TradHeli.
H_TAIL_TYPE=1 (Servo with External Gyro) now fails arming checks.
Updates the parameter list, tailrotor setup, manual tuning, and
transmitter tuning pages to match.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: copter/source/docs/traditional-helicopter-manual-tuning.rst
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,12 +122,11 @@ Note that there is a little overshoot and neutral ringing indicating that the FF
122
122
Tuning a Flybar Equipped Head
123
123
=============================
124
124
125
-
The setup of a helicopter with flybar equipped head does not require the
126
-
``H_FLYBAR_MODE`` set to flybar mode. This parameter only affects
127
-
the ACRO flight mode. Unless there is a reason passthrough provided by the flybar
128
-
setting in ACRO mode is needed, then it is recommended that ``H_FLYBAR_MODE`` is
129
-
left at its default of no flybar. If you choose to use the flybar mode then the FF gain
130
-
is set as described below. Otherwise the FF is tuned just like an flybarless head.
125
+
The setup of a helicopter with a flybar equipped head requires no special
126
+
configuration; ArduPilot's attitude controller runs the same way as for a
127
+
flybarless head, and the FF gain is set as described below.
128
+
129
+
.. note:: Prior to Copter-4.8, the ``H_FLYBAR_MODE`` parameter allowed ACRO flight mode to passthrough pilot roll/pitch input directly to the swashplate, mimicking a mechanical flybar. This passthrough option has been removed; ACRO mode now always uses the attitude controller's "Virtual Flybar" feature (see :ref:`acro-mode`) regardless of whether the head is flybar equipped.
131
130
132
131
.. Note:: For flybar heads, the flybar is a mechanical version of the rate PID loop. So flybar is tuned using only FF in pitch and roll. The rate D and P gains are left set to zero for flybar. I-gain, IMAX, and ILMI are tuned just like FBL.
Copy file name to clipboardExpand all lines: copter/source/docs/traditional-helicopter-tailrotor-setup.rst
+1-10Lines changed: 1 addition & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,6 @@ Traditional Helicopter – Tailrotor Setup
7
7
There are several ways for controlling the tailrotor to maintain yaw stabilization and provide yaw control, and each have a unique setup. The :ref:`H_TAIL_TYPE <H_TAIL_TYPE>` parameter is used to specify method for controlling the tailrotor. A list of available tail types is given below:
8
8
9
9
- Servo Only: ArduPilot will supply the tail rotor stabilization like a tail rotor gyro and control the pitch of the tail rotor blades.
10
-
- Servo with External Gyro: ArduPilot will output yaw demands without direct yaw attitude stabilization which is provided via an external gyro.
11
10
- Direct Drive Variable Pitch (DDVP): Instead of the tail rotor being driven from the main rotor via mechanical coupling as in the above cases, an electric motor is used with motor controlled(ramp up/down, operating point) by ArduPilot. Main yaw control is via tail blade pitch servo, as above.
12
11
- Direct Drive Fixed Pitch Clockwise (DDFP CW): Tail rotor is driven by a motor whose ESC is controlled by ArduPilot to maintain yaw stability and yaw direction. Used with clockwise rotating main rotors, when viewed from above.
13
12
- Direct Drive Fixed Pitch Counter-Clockwise (DDFP CCW): Tail rotor driven by a motor whose ESC is controlled by ArudPilot to maintain yaw stability and yaw direction. Used with counter-clockwise rotating main rotors, when viewed from above.
@@ -23,14 +22,7 @@ The Servo Only tail type uses a servo connected to an autopilot output whose ``S
23
22
24
23
Be sure to check the direction of operation of the Tail Servo. Move the rudder stick and notice the change in tail rotor pitch. Be sure that its increase or decrease of pitch is such that the change in thrust will result in the desired direction of movement. If not, reverse the servo direction with the ``SERVOx_REVERSED`` parameter.
25
24
26
-
Servo with External Gyro :ref:`H_TAIL_TYPE <H_TAIL_TYPE>` = 1
Instead of ArduPilot controlling both the desired yaw rate and stability, this option relies on an external gyro for stabilization. A servo is still used to input yaw rate demands to the tail and its setup as above, for the Servo Only case.
30
-
31
-
The external gyro gain can be set by the ``H_GYR_GAIN`` parameter using the autopilot's "Motor7" output function,``SERVOx_FUNCTION``.
32
-
33
-
In ACRO mode, this gain can be changed to the value of the ``H_GYR_GAIN_ACRO`` parameter, if non-zero.
25
+
.. note:: Prior to Copter-4.8, :ref:`H_TAIL_TYPE <H_TAIL_TYPE>` = 1 selected "Servo with External Gyro", which bypassed ArduPilot's yaw attitude/rate controller and passed pilot yaw demand straight to an external gyro for stabilization (using the ``H_GYR_GAIN`` and ``H_GYR_GAIN_ACRO`` parameters). This passthrough capability has been removed. Selecting :ref:`H_TAIL_TYPE <H_TAIL_TYPE>` = 1 will now fail arming checks. An external gyro can still be used mechanically, but only in its rate (non heading-hold/non-AVCS) mode, feeding a tail servo controlled normally via :ref:`H_TAIL_TYPE <H_TAIL_TYPE>` = 0 (Servo Only), with ArduPilot's own attitude/rate controller commanding the servo as usual.
34
26
35
27
Direct Drive Variable Pitch :ref:`H_TAIL_TYPE <H_TAIL_TYPE>` = 2
0 commit comments