New Crowdin updates (PX4#1945)

* New translations filter_tuning.md (German)

* New translations filter_tuning.md (Japanese)

* New translations filter_tuning.md (Korean)

* New translations filter_tuning.md (Russian)

* New translations filter_tuning.md (Turkish)

* New translations filter_tuning.md (Chinese Simplified)

* New translations vtol_quad_configuration.md (German)

* New translations vtol_quad_configuration.md (Japanese)

* New translations vtol_quad_configuration.md (Korean)

* New translations vtol_quad_configuration.md (Russian)

* New translations vtol_quad_configuration.md (Turkish)

* New translations vtol_quad_configuration.md (Chinese Simplified)

* New translations position_mc.md (German)

* New translations controller_diagrams.md (German)

* New translations controller_diagrams.md (Japanese)

* New translations position_mc.md (Japanese)

* New translations position_mc.md (Korean)

* New translations controller_diagrams.md (Korean)

* New translations controller_diagrams.md (Russian)

* New translations position_mc.md (Russian)

* New translations position_mc.md (Turkish)

* New translations controller_diagrams.md (Turkish)

* New translations position_mc.md (Chinese Simplified)

* New translations controller_diagrams.md (Chinese Simplified)

* New translations vtol_tiltrotor_eflite_convergence_pixfalcon.md (German)

* New translations vtol_tiltrotor_eflite_convergence_pixfalcon.md (Japanese)

* New translations vtol_tiltrotor_eflite_convergence_pixfalcon.md (Korean)

* New translations vtol_tiltrotor_eflite_convergence_pixfalcon.md (Russian)

* New translations vtol_tiltrotor_eflite_convergence_pixfalcon.md (Turkish)

* New translations vtol_tiltrotor_eflite_convergence_pixfalcon.md (Chinese Simplified)

* New translations thunderfly_tachometer.md (German)

* New translations thunderfly_tachometer.md (Japanese)

* New translations thunderfly_tachometer.md (Korean)

* New translations thunderfly_tachometer.md (Russian)

* New translations thunderfly_tachometer.md (Turkish)

* New translations thunderfly_tachometer.md (Chinese Simplified)

* New translations ark_flow.md (German)

* New translations ark_flow.md (Japanese)

* New translations ark_flow.md (Korean)

* New translations ark_flow.md (Russian)

* New translations ark_flow.md (Turkish)

* New translations ark_flow.md (Chinese Simplified)

* New translations ark_cannode.md (German)

* New translations ark_cannode.md (Japanese)

* New translations ark_cannode.md (Korean)

* New translations ark_cannode.md (Russian)

* New translations ark_cannode.md (Turkish)

* New translations ark_cannode.md (Chinese Simplified)

* New translations tuning_the_ecl_ekf.md (German)

* New translations tuning_the_ecl_ekf.md (Japanese)

* New translations tuning_the_ecl_ekf.md (Korean)

* New translations tuning_the_ecl_ekf.md (Russian)

* New translations tuning_the_ecl_ekf.md (Turkish)

* New translations tuning_the_ecl_ekf.md (Chinese Simplified)

* New translations compass.md (German)

* New translations compass.md (Japanese)

* New translations compass.md (Korean)

* New translations compass.md (Russian)

* New translations compass.md (Turkish)

* New translations compass.md (Chinese Simplified)

de/advanced_config/tuning_the_ecl_ekf.md

@@ -139,6 +139,10 @@ Tuning parameters:
 - [EKF2_PCOEF_YN](../advanced_config/parameter_reference.md#EKF2_PCOEF_YN)
 - [EKF2_PCOEF_Z](../advanced_config/parameter_reference.md#EKF2_PCOEF_Z)
 
+#### Barometer bias compensation
+
+A barometer at a constant altitude is subject to drift in its measurements due to changes in the ambient pressure environment or variations of the sensor temperature. To compensate for this measurement error, EKF2 estimates the bias using GNSS height (if available) a "non drifting" reference. No tuning is required.
+
 ### GPS
 
 #### Position and Velocity Measurements
@@ -209,6 +213,16 @@ Range finder distance to ground is used by a single state filter to estimate the
 
 If operating over a flat surface that can be used as a zero height datum, the range finder data can also be used directly by the EKF to estimate height by setting the [EKF2_HGT_MODE](../advanced_config/parameter_reference.md#EKF2_HGT_MODE) parameter to 2.
 
+#### Range Finder Blockage Detection
+
+When not used as the primary height source, blockage is detected using a kinematic consistency check between the vertical velocity estimate and the numerical derivative of the range finder data. If the range finder is statistically inconsistent with EKF2, the sensor is rejected for the rest of the flight unless the statistical test passes again for at least 1 second at a vertical speed of 0.5m/s or more.
+
+Note that the check is only active while the vehicle is hovering as it assumes a static ground height. In order to obtain a good detection, the range finder noise parameter needs to be tightly tuned using flight data. Then, the kinematic consistency gate parameter can be adjusted to obtain the desired fault detection sensitivity.
+
+Tuning parameters:
+- [EKF2_RNG_NOISE](../advanced_config/parameter_reference.md#EKF2_RNG_NOISE)
+- [EKF2_RNG_K_GATE](../advanced_config/parameter_reference.md#EKF2_RNG_K_GATE)
+
 ### Airspeed
 
 Equivalent Airspeed (EAS) data can be used to estimate wind velocity and reduce drift when GPS is lost by setting [EKF2_ARSP_THR](../advanced_config/parameter_reference.md#EKF2_ARSP_THR) to a positive value. Airspeed data will be used when it exceeds the threshold set by a positive value for [EKF2_ARSP_THR](../advanced_config/parameter_reference.md#EKF2_ARSP_THR) and the vehicle type is not rotary wing.

de/config/compass.md

@@ -4,6 +4,11 @@ The compass calibration process configures all connected internal and external [
 
 You will need to calibrate your compass on first use, and you may need to recalibrate it if the vehicles is ever exposed to a very strong magnetic field, or if it is used in an area with abnormal magnetic characteristics.
 
+Two types of compass calibration are available:
+
+1. [Complete](#complete-calibration): This calibration is required after installing the autopilot on an airframe for the first time or when the configuration of the vehicle has changed significantly. It compensates for hard and soft iron effects by estimating an offset and a scale factor for each axis.
+1. [Partial](#partial-quick-calibration) ("Quick Calibration"): This calibration can be performed as a routine when preparing the vehicle for a flight, after changing the payload, or simply when the compass rose seems inaccurate. This type of calibration only estimates the offsets to compensate for a hard iron effect.
+
 :::note
 If you are using an external magnetometer/compass (or a compass integrated into a GPS module) make sure it is [mounted](../assembly/mount_gps_compass.md) as far as possible from other electronics and in a *supported orientation*. Instructions for *connecting* your GPS+compass can be found in [Basic Assembly](../assembly/README.md) for your specific autopilot hardware. Once connected, *QGroundControl* will automatically detect the external magnetometer.
 :::
@@ -14,6 +19,8 @@ Indications of a poor compass calibration include multicopter circling during ho
 
 ## Performing the Calibration
 
+### Complete Calibration
+
 The calibration steps are:
 
 1. Choose a location away from large metal objects or magnetic fields. :::tip
@@ -38,6 +45,18 @@ You should already have set the [Autopilot Orientation](../config/flight_control
 
 Once you've calibrated the vehicle in all the positions *QGroundControl* will display *Calibration complete* (all orientation images will be displayed in green and the progress bar will fill completely). You can then proceed to the next sensor.
 
+### Partial "Quick" Calibration
+
+This calibration is similar to the well-known figure-8 compass calibration done on a smartphone:
+
+1. Hold the vehicle in front of you and randomly perform partial rotations on all its axes.
+1. Wait for the heading estimate to stabilize and verify that the compass rose is pointing to the correct direction (this can take a couple of seconds).
+
+Notes:
+
+- There is no start/stop for this type of calibration (the algorithm runs continuously when the vehicle is disarmed).
+- The calibration is immediately applied to the data (no reboot is required) but is saved to the calibration parameters after disarming the vehicle only (the calibration is lost if no arming/disarming sequence is performed between calibration and shutdown).
+- The amplitude and the speed of the partial rotations done in step 1 can affect the calibration quality. However, 2-3 oscillations of ~30 degrees in every direction is usually enough.
 
 ## Further Information
 

de/config_mc/filter_tuning.md

@@ -30,8 +30,8 @@ Below we look at the impact of the low pass filters.
 
 This is the filtering pipeline for the controllers in PX4:
 - On-chip DLPF for the gyro sensor. This is disabled on all chips where it can be disabled (if not, the cutoff frequency is set to the highest level of the chip).
-- A notch filter on the gyro sensor data that is used to filter out narrow band noise, for example harmonics at the rotor blade pass frequency. This filter can be configured using [IMU_GYRO_NF_BW](../advanced_config/parameter_reference.md#IMU_GYRO_NF_BW) and [IMU_GYRO_NF_FREQ](../advanced_config/parameter_reference.md#IMU_GYRO_NF_FREQ).
-- Low-pass filter on the gyro sensor data. It can be configured with the [IMU_GYRO_CUTOFF](../advanced_config/parameter_reference.md#IMU_GYRO_CUTOFF) parameter. :::note
+- A notch filter on the gyro sensor data that is used to filter out narrow band noise, for example harmonics at the rotor blade pass frequency. This filter can be configured using [IMU_GYRO_NF0_BW](../advanced_config/parameter_reference.md#IMU_GYRO_NF0_BW) and [IMU_GYRO_NF0_FRQ](../advanced_config/parameter_reference.md#IMU_GYRO_NF0_FRQ).
+- Low-pass filter on the gyro sensor data. It can be configured with the  [IMU_GYRO_CUTOFF](../advanced_config/parameter_reference.md#IMU_GYRO_CUTOFF) parameter. :::note
 Sampling and filtering is always performed at the full raw sensor rate (commonly 8kHz, depending on the IMU).
 :::
 - A separate low-pass filter on the D-term. The D-term is most susceptible to noise while slightly increased latency does not negatively affect performance. For this reason the D-term has a separately-configurable low-pass filter, [IMU_DGYRO_CUTOFF](../advanced_config/parameter_reference.md#IMU_DGYRO_CUTOFF).
@@ -82,9 +82,9 @@ The plot cannot be compared between different vehicles, as the y axis scale can
 On the same vehicle it is consistent and independent of the flight duration.
 :::
 
-If the flight plots shows significant low frequency spikes, like the one shown in the diagram below, you can remove it using a notch filter. In this case you might use the settings: [IMU_GYRO_NF_FREQ=32](../advanced_config/parameter_reference.md#IMU_GYRO_NF_FREQ) and [IMU_GYRO_NF_BW=5](../advanced_config/parameter_reference.md#IMU_GYRO_NF_BW) (note, this spike is narrower than usual). The low pass filters and the notch filter can be tuned independently (i.e. you don't need to set the notch filter before collecting the data for tuning the low pass filter).
+If the flight plots shows significant low frequency spikes, like the one shown in the diagram below, you can remove it using a notch filter. In this case you might use the settings: [IMU_GYRO_NF0_FRQ=32](../advanced_config/parameter_reference.md#IMU_GYRO_NF0_FRQ) and [IMU_GYRO_NF0_BW=5](../advanced_config/parameter_reference.md#IMU_GYRO_NF0_BW) (note, this spike is narrower than usual). The low pass filters and the notch filter can be tuned independently (i.e. you don't need to set the notch filter before collecting the data for tuning the low pass filter).
 
-![IMU_GYRO_NF_FREQ=32 IMU_GYRO_NF_BW=5](../../assets/config/mc/filter_tuning/actuator_controls_fft_gyro_notch_32.png)
+![IMU_GYRO_NF0_FRQ=32 IMU_GYRO_NF0_BW=5](../../assets/config/mc/filter_tuning/actuator_controls_fft_gyro_notch_32.png)
 
 ## Additional Tips
 

de/config_vtol/vtol_quad_configuration.md

@@ -75,15 +75,6 @@ Parameter: [VT_ARSP_TRANS](../advanced_config/parameter_reference.md#VT_ARSP_TRA
 This is the airspeed which, when reached, will trigger the transition out of multirotor mode into fixed wing mode. It is critical that you have properly calibrated your airspeed sensor. It is also important that you pick an airspeed that is comfortably above your airframes stall speed (check `FW_AIRSPD_MIN`) as this is currently not checked.
 
 
-#### Fixed Wing Permanent Stabilisation
-
-Parameter: [VT_FW_PERM_STAB](../advanced_config/parameter_reference.md#VT_FW_PERM_STAB)
-
-Activating permanent stabilisation will result in fixed wing flight being stabilised by the autopilot at all times. As soon as a transition to fixed wing occurs it will be stabilised.
-
-Note that if you have not yet tuned your fixed wing mode you should leave this off until you are sure it behaves well in this mode.
-
-
 <span id="transitioning_tips"></span>
 ### Transitioning Tips