Tutorial for the First Flight of a Multi-rotor Aircraft -Ⅱ
Pre-Arm Safety Check Procedure
The APM: Copter firmware includes a comprehensive “Pre-Arm” safety check mechanism. It scans your aircraft for a wide range of potential issues—such as uncalibrated components or damaged sensors—before allowing it to be armed. While robust, this system is not infallible; you can disable these checks via the `Arming_check` parameter in the full parameter list.
Note: As flight controller firmware is continuously updated, some error messages may change or differ from those described here; there may also be errors not covered in this text. This is normal. You can try searching for the specific error using a search engine.
Using the GCS (Ground Control Station) to View Pre-Arm Error Messages
When the status light flashes yellow, the system cannot be armed; attempting to arm it will also trigger two long beeps from the buzzer. In this situation, you must connect to the Ground Control Station (GCS) to identify the specific issue preventing the system from being armed or flown. Common causes include uncalibrated sensors, the triggering of a failsafe, or incorrect low-voltage settings. Each type of error message is analyzed in detail below:
Before proceeding, please ensure that you have set up and connected your ground station, calibrated the flight controller, and learned the basics of operating the remote controller.
If you haven’t done so yet, please refer to the previous sections 🙂
Using Pre-Arm messages to diagnose arming failures:
- Ensure the flight controller is connected to the RC receiver, and that all propellers and the flight battery have been removed.
- Connect the flight controller to a Ground Control Station (GCS)—such as Mission Planner on a PC or CUAV Hfight on Android—via USB or a telemetry link (e.g., WP-LINK, 3DR, XBEE, or XTND).
- Turn on your RC transmitter and attempt to arm the system (the arming command requires the throttle stick to be at its lowest position—Channel 3—and the yaw stick to be pushed fully to the right—Channel 4).
- At this point, a red “Pre-Arm” error message should appear in the GCS interface. If no message appears, it typically indicates that the arming channels are not configured correctly, preventing the flight controller from detecting your arming command. You can also monitor the status bar within the “Flight Data” tab of the GCS while attempting to arm.
Prompt message for failed unlock:
Common error messages on the remote control:
No RC receiver
Please verify that the signal input to the receiver is functioning correctly.
Troubleshooting steps:
1: If you are using a PPM encoder module, check whether the blue status LED on the encoder is still flashing (this indicates whether the PPM encoder is operational).
2: If you are using an SBUS or PPM receiver, ensure that the receiver settings are configured correctly.
3: In rare cases, the flight controller hardware or its firmware may be faulty, requiring the unit to be returned to the manufacturer for inspection and repair.
RC not calibrated
The remote controller has either not been calibrated, or its values fall outside the range recorded by the flight controller—typically due to changes in the controller’s settings or the use of a different remote controller. Please perform a recalibration to resolve this.
For the RC3 (throttle) channel, the ideal range for the minimum (MIN) and maximum (MAX) values is 1100–1900.
For all other channels, the minimum value should not exceed 1300, and the maximum value should not be less than 1700; the ideal range for these is also 1100–1900.
Common error messages for electronic compasses:
Compass not healthy
An “unhealthy” status for an electronic compass may indicate that no data is being received or that the hardware is damaged.
Additionally, if the ambient temperature drops below 0°C, the compass sensor may fail to output any values.
Troubleshooting steps:
- Power-cycle the device.
- If the temperature is too low, take measures to keep the unit warm, then power-cycle it.
- Check the compass values (MX1, MY1, MZ1; MX2, MY2, MZ2) in the Ground Control Station (GCS) to ensure they are correct.
Compass not calibrated
If the compass is not calibrated, or if it has been removed and re-added, a “compass not calibrated” notification will appear.
Solution:
- Once the compass is installed, perform the calibration process again.
Compass offsets too high
If the offset value of the main compass (i.e., sqrt(x^2+y^2+z^2)) exceeds 500, this alert will be triggered. This is typically caused by the presence of magnetic objects (such as motors, screws, or batteries) near the flight controller or GPS, or by strong external magnetic field interference.
Solutions:
- Remove any sources of interference and power-cycle the system.
- Relocate the flight controller or GPS to a different position and perform a recalibration.
- Try operating the device in a different environment.
Check mag field
This error may occur if you are indoors, have moved to a different environment, or are near sources of magnetic interference.
Solution:
If you have changed your environment, simply perform a recalibration.
If you are indoors or near a source of interference, move away from that source.
Inconsistent compass readings:
The internal and external compasses show a discrepancy in their headings (>45 degrees). This is typically caused by an incorrect orientation setting for the external compass (`compass_orient`).
Solution:
Perform a recalibration. Select the PX4 calibration procedure; there is no need to specify an orientation.
Common GPS malfunctions:
GPS Glitch / Need 3D Fix
If GPS positioning fails, or if no GPS is present—while using flight modes that require GPS (such as “Loiter” or “Poshold”) or while a geofence is enabled—the system will trigger these two error messages.
Solutions:
- If no GPS is installed, or if you are flying indoors, please switch to a flight mode that does not require GPS.
- Wait for the GPS to achieve a “3D Fix.”
- “NO GPS” (GPS hardware not detected): Check the connecting cables.
- “NO FIX” (No 3D lock): Move the aircraft and the GPS unit to an outdoor location with an unobstructed view of the sky.
Bad Velocity:
If the compass is not calibrated, or if it has been removed and re-added, a “compass not calibrated” notification will appear.
Solution:
- Once the compass is installed, perform the calibration process again.
High GPS HDOP: (HDOP value does not meet the standard—it is not sufficiently low; a lower number indicates higher precision.)
An excessively high HDOP (Horizontal Dilution of Precision) value in satellite positioning is generally caused by an insufficient number of satellites.
Solution:
- Place the device outdoors in an unobstructed area. Wait a few minutes for it to lock onto more satellites.
The HDOP value can be viewed in the ground station software.
INS checks (e.g., accelerometer and gyroscope checks)
INS not calibrated: (INS accelerometer not calibrated)
The accelerometer is not calibrated, or it is calibrated incorrectly.
Solution:
- Recalibrate the accelerometer. Refer to the section on calibrating the accelerometer.
Accelerometers are not healthy
This could be a hardware issue; alternatively, this error might appear if the flight controller is powered on immediately after a firmware flash.
Solution:
- Power-cycle the flight controller board and reconnect.
- Contact the CUAV technical support department for assistance.
Gyros are not healthy
If the gyroscope data fluctuates significantly, falls outside the expected range, or is missing entirely, this may indicate a hardware issue. Alternatively, the device may have been moved during power-up.
Solution:
- Place the device on a flat, stable surface and power-cycle it.
- If the issue persists after several power-cycle attempts, please contact the CUAV technical support team for further troubleshooting.
Gyro calibration failed
This typically happens when you cut power while the device is on (specifically, while the red and blue lights are flashing). It can also be triggered if a value exceeds its peak limit.
Solution:
- Place the device on a level surface and power it on again.
Gyros inconsistent:
The difference in rotation rates between the two gyroscopes exceeds 20°/s; this may indicate a hardware fault or an incorrect gyroscope calibration.
Solution:
- Power-cycle the device.
- Contact the CUAV technical support department.
Check Board Voltage:
If the motherboard voltage falls below 4.3V or rises above 5.8V, a “Check Board Voltage” warning will be triggered.
Using an excessively low USB supply voltage can also trigger this warning.
If this is powered by a power supply module, you will be prompted to check the motherboard voltage; this could be a serious issue.
Solution:
Verify that the supply voltage is approximately 5V.
Use a CUAV IV power module or a standard 5V power module.
Check FS_THR_VALUE: (Check the failsafe throttle value)
The current throttle value is too low, which has triggered the failsafe.
Solution:
- Check the throttle channel settings on your remote controller; the value should not be lower than 1000, with an optimal value of around 1100.
- Check the failsafe settings in your ground control station to ensure the throttle threshold value is not set too high.
bad logging (failure to store logs)
SD card not detected. Please check if it is inserted correctly, or try removing and reinserting it.
ACRO_BAL_ROLL/PITCH:
The `ACRO_BAL_ROLL` parameter is set higher than the P-gain for roll in stabilize mode, and/or the `ACRO_BAL_PITCH` parameter is set higher than the P-gain for pitch in stabilize mode. This may prevent the pilot from controlling the tilt angle in ACRO mode, as the stabilization provided by “Acro Trainer” will override the pilot’s inputs.
Disable secure unlock check:
If you find the error messages meaningless and they are preventing you from arming your aircraft for flight, you can disable them via the ground station.
- Connect your flight controller to the ground station (using a USB cable or telemetry link).
- Go to the “Config/Tuning” tab > “Standard Params.”
- Set “ARMING_CHECK” to “Disabled,” then click “Write Params.”
Unlock the aircraft
Before arming, ensure you are in an open, uninhabited area to prevent any accidents.
Thoroughly verify that the hardware is installed correctly (paying special attention to ESC wiring, flight controller firmware, and propeller orientation). Once confirmed, proceed with the following steps:
- Turn on your remote control transmitter.
- Connect the battery to the aircraft. The flight controller status LED should flash red and blue (indicating a self-test process); do not move the aircraft during this time.
- The “Pre-Arm” check will run automatically. Once the self-test is complete, the LED will flash blue or green, indicating no Pre-Arm errors and that the aircraft is ready to be armed. If the LED flashes yellow, please refer to the “Pre-Arm Error Analysis” section to troubleshoot and resolve the issue.
- Set the appropriate flight mode: Choose “Stabilize,” “AltHold” (Altitude Hold), or “Loiter” (requires a GPS lock, which must be obtained outdoors). For beginners, “Stabilize” or “AltHold” is recommended.
- Engage the safety switch: Press and hold the safety switch until the safety LED remains solid (a flashing LED indicates the system is disarmed with no PWM output; a solid LED indicates it is armed and outputting PWM signals).
- Arm the system via the remote control: Move the throttle stick to the lowest position and the yaw (rudder) stick to the far right. Hold this position for 10 seconds. The RGB status LED will flash red and blue, signaling that the system is armed; you may then release the yaw stick.
- Successful arming: The propellers will begin to spin at an idle speed. While this may appear intimidating, it is a safety feature designed to indicate that the system is armed. You can disable this idle spin by setting the `MOT_SPIN_ARMED` parameter to 0.
- Takeoff: Increase the throttle to take off, and use the controls to manage the aircraft’s attitude and direction. (If you are a beginner and unfamiliar with the controls, it is highly recommended to practice using a flight simulator first to avoid crashes that could result in personal injury or property damage.)
If no action is taken within 15 seconds of arming, the system will automatically disarm. Additionally, if the aircraft is armed but has not yet taken off, it will automatically disarm if there is a significant discrepancy between its intended attitude and its actual orientation (for example, if the roll stick is moved aggressively or the aircraft is shaken by hand).
Locked Aircraft
To lock the aircraft, perform the following steps:
- Ensure your flight mode switch is set to Stabilize, AltHold, or Loiter.
- Keep the throttle at its lowest position and the yaw stick pushed all the way to the left (the opposite of the position used to unlock/arm).
- Press and hold the safety switch until it begins to flash.
- Disconnect the aircraft battery.
- Turn off the remote control transmitter.
First Flight
- Place the aircraft on a level surface, connect the battery, keep it steady, and wait for the self-test to complete (indicated by the cessation of the flashing red and blue lights). Ensure your remote controller is set to “Stabilize” mode.
- Disengage the safety switch, then arm the aircraft using the remote controller (throttle at the lowest position, yaw stick pushed fully to the right). Gradually increase the throttle until the aircraft just lifts off the ground.
Troubleshooting:
A. Aircraft flips or rolls over upon takeoff: This is typically caused by incorrect motor numbering, propellers installed in the wrong orientation (clockwise/counter-clockwise), firmware errors, or an incorrect frame configuration. These are almost always installation-related issues; we recommend carefully checking each component or disassembling and reassembling the unit, including reflashing the firmware.
(In our experience, over 99 out of 100 cases where an aircraft flips on takeoff are due to installation errors—please do not immediately assume that your flight controller board is faulty.)
B. Controls (pitch, roll, or yaw) are reversed: Adjust the settings in your remote controller’s menu by reversing the corresponding channels.
C. Vibrations during flight:
The default parameters are optimized for aircraft with a wheelbase of approximately 450mm. If your aircraft falls outside this range, vibrations are common and can be resolved by adjusting the parameters.
D. Aircraft consistently tilts in one direction during flight:
This may be caused by an uneven installation. Check that the motors are level and the flight controller is positioned correctly, or recalibrate the accelerometer. You may also perform an “auto-trim” (automatic fine-tuning).
If you encounter other issues you cannot resolve, please refer to the “Troubleshooting Guide” section. E. Rapid spinning (yawing): 1. In Stabilize mode (for hexacopters or octocopters): Check for any abnormal motor rotation, ensure the motors and propellers are spinning in the correct direction, and verify the firmware. For quadcopters: Ensure the correct firmware is installed. 2. In GPS-based modes: Check for interference with the compass and verify that the aircraft behaves normally in Stabilize mode. 3. Slow spinning (yawing): This typically occurs with aircraft that have a large wheelbase; it can be addressed by adjusting the “Yaw” value within the PID settings.
Pay attention to your flight environment
Multi-rotor aircraft are highly dangerous—potentially as lethal as a *xue di zi* (a legendary, deadly flying weapon). Never attempt to fly one amidst a crowd; doing so could come at a very heavy price!
Be careful not to over-discharge your battery, as this could lead to a crash!
It is recommended to use the included IV module for power supply and ensure that voltage monitoring is enabled.
If you are a beginner, it is advisable to attach a “battery alarm” (buzzer) to your battery to prevent it from becoming unusable or causing a crash due to low voltage.
Basic Tuning
This section covers the fundamental tuning of roll, pitch, and throttle.
Overview
During your first flight, you may find that the aircraft’s responsiveness and control are not quite as you expected. For instance, the attitude response might be too slow, the craft might exhibit jitter, or the throttle response could be either too sensitive or too sluggish. Do not worry; these issues can be resolved by simply adjusting a few parameters. If you are an experienced user familiar with PID control theory, you may refer to the “Advanced Tuning Guide” or explore the automatic tuning (auto-tune) feature.
The current version of the ground control software simplifies complex tuning into a few straightforward modules; by adjusting just a handful of parameters, you can generally achieve highly satisfactory flight performance.
While it is possible to perform tuning during flight—with changes taking effect in real-time—this is not recommended unless you are a highly skilled pilot.
We advise making adjustments only when the aircraft is disarmed (locked), and keeping each adjustment modest.
Tuning Roll and Pitch
Tuning is typically performed by connecting to a computer-based ground control station via a telemetry link. The following guide covers basic tuning procedures using APMPlanner2 and Mission Planner.
In APMPlanner2, navigate to the “CONFIG/TUNING” menu and select “Basic Tuning.”
The “ROLL/Pitch Rate Control” settings allow you to adjust the responsiveness, correction sensitivity, and strength for both roll and pitch.
If you find that your aircraft reacts too quickly or exhibits excessive vibration (shaking), try moving the slider one notch to the left (decreasing the value).
If you feel that the aircraft’s corrective response is too weak or that it reacts too slowly, try moving the slider one notch to the right (increasing the value).
After making adjustments, conduct a test flight to check for improvements. Repeat this process as needed until you achieve the desired performance.
Yaw Parameter Tuning
The “Stabilize Yaw” and “Rate Yaw” parameters, highlighted in orange in the screenshot above, control the yaw response. It is rarely necessary to adjust yaw settings.
Similar to Roll and Pitch, if the “Stabilize Yaw P” or “Rate Yaw P” values are too high, the helicopter’s heading will be adversely affected. If they are too low, the helicopter may fail to maintain its current heading.
As mentioned in the section on tuning Stabilize mode, the `ACRO_YAW_P` parameter controls the helicopter’s rotation speed in response to the pilot’s yaw input. With the default value of 4.5, holding the yaw stick fully to the left or right commands a rotation speed of 200 degrees per second. Higher values will result in a faster rotation.
Altitude Tuning
In the screenshot above, the relevant tuning parameters for altitude hold are highlighted in green.
The Altitude P-gain is used to convert the altitude error (the difference between the desired altitude and the actual altitude) into a target climb or descent rate. A higher value will result in more aggressive altitude maintenance, but setting it too high can cause the throttle to respond too sharply.
The Throttle Rate (which typically does not require tuning) converts the desired climb or descent rate into a target vertical acceleration.
The Throttle Acceleration PID gains convert the acceleration error (the difference between the desired acceleration and the actual acceleration) into motor output. If you modify these parameters, you should maintain a 1:2 ratio between the P and I gains (i.e., the I-gain should be twice the value of the P-gain). While these values generally do not need to be increased, for very powerful multirotors, you may achieve better responsiveness by reducing them by 50% (e.g., setting P to 0.5 and I to 1.0).
For more details, please refer to the Altitude Hold mode page.
Hover Tuning
Generally speaking, if Roll and Pitch are tuned correctly, the GPS and compass are properly configured and performing well, and vibration levels are within an acceptable range, little to no further adjustment should be required for hovering. Please refer to the Hover Mode page for more details on adjustable parameters, including horizontal speed.
Throttle Hover Adjustment
This option allows you to adjust the throttle stick position required for hovering.
If your aircraft requires a throttle position above the center point to hover, you can shift the setting one increment to the left (decrease).
If your aircraft requires a throttle position below the center point to hover, you can shift the setting one increment to the right (increase).
Throttle Response Adjustment
This option allows you to adjust the throttle response speed.
If your throttle response is too sensitive—meaning a slight nudge causes the aircraft to climb too rapidly—you can decrease the throttle response value.
If your throttle response feels too sluggish—where advancing the throttle results in a slow climb or a lack of power—you can try increasing the throttle response value.
Note that this setting can only address certain throttle-related issues; if your aircraft’s power system is poorly configured or your battery lacks sufficient discharge capability, the effect may be negligible.
Extended Parameter Tuning (PID)
Schematic diagram illustrating the various components of hyperparameter tuning
Remote control sensitivity: The responsiveness of the aircraft to inputs from the pilot’s remote controller. A higher value results in faster response; high values are suitable for FPV (first-person view) racing or freestyle, while lower values are better for aerial photography. In theory, the more efficient an aircraft is, the lower this value should be. This parameter should be the first to be adjusted when tuning PID settings.
Adjusting roll and pitch during flight (using remote control input on channel 6 for parameter tuning as an example)
First, you need to calibrate channel 6 during the remote control calibration process. Then, assign channel 6 to “Rate Roll / Pitch kP,” setting the minimum value to 0.08 and the maximum value to 0.20 (this range is typical for most aircraft), and click “Write” to save the settings.
Turn the CH6 knob on your remote control to its minimum position, then click the “Refresh Parameters” button; verify that the “Rate Roll P” and “Rate Pitch P” values have updated to 0.08 (or a value very close to it).
Turn the CH6 knob on your remote control to its maximum position, click “Refresh Parameters” again, and ensure that the “Rate Roll P” value has updated to 0.20.
Fly in Stabilize mode and adjust the knob until the aircraft’s flight is stable rather than shaky.
Disconnect the aircraft battery and connect the flight controller to the Ground Control Station (GCS) via USB. Ensure the CH6 knob is set to the position that yields the best flight performance. Navigate to the “Extended Tuning” (or equivalent) interface, note the current PID values, and re-enter them while making minor adjustments. Finally, set the CH6 function to “None” and click “Write” to save the changes.
Vibration Analysis and Testing
Overview
Flight controllers are highly sensitive to vibration, as they rely on data from accelerometers—often fused with input from barometers and GPS—to calculate the aircraft’s attitude.
Excessive vibration can lead to errors in the flight controller’s estimation and calculation of attitude and altitude, resulting in poor flight performance or even a crash.
Flight modes that are particularly susceptible to these issues include AltHold, Loiter, RTL, Guided, Position, and AUTO.
The following section explains how to measure and analyze vibration levels. If you find that vibration exceeds acceptable limits, it is crucial to address the root cause; doing so is a prerequisite for achieving good flight performance.
Common sources of vibration include a frame that is too flexible, unbalanced motors, and unbalanced propellers.
Measurement procedure for Copter 3.3 and later versions
- Fly the aircraft as you normally would for a period of time—avoid being overly gentle, but also refrain from aggressive maneuvers—for at least a few minutes. Then, download the log file (.bin file).
- Use the Mission Planner (MP) ground station software to load the .bin log file.
3. Use the VibeX, VibeY, and VibeZ values from the VIBE message, which can be viewed in a ground control station (GCS) or other GCS-related graphical displays. These values represent the standard deviation (in m/s²) of the primary accelerometer output. The image below, taken from a 3DR IRIS, shows typical levels—generally below 15 m/s², with occasional spikes reaching 30 m/s². The maximum acceptable value appears to be below 60 m/s² (see the image below).
4. Track the values of Clip0, Clip1, and Clip2, which increment whenever one of the accelerometers reaches its maximum limit (16 G). Ideally, these values should remain zero throughout the entire flight; however, a low number (less than 100)—perhaps occurring during a hard landing—might be acceptable. A consistent increase in these values across your flight logs indicates a serious vibration issue that needs to be addressed.
This is an example of an aircraft experiencing position-estimation issues due to high vibration levels.
The algorithm used to calculate vibration levels can be found in the `calc_vibration_and_clipping()` method within `AP_InertialSensor.cpp`. In short, it involves calculating the standard deviation of accelerometer readings, as follows:
Capture the raw x, y, and z accelerometer values from the primary IMU.
Apply a 5Hz high-pass filter to the raw values to remove the vehicle’s motion, creating an “accel_vibe_floor” for the x, y, and z axes.
Calculate the difference between the latest acceleration values and the `accel_vibe_floor`.
Square these differences, apply a 2Hz filter, and then calculate the square root (for the x, y, and z axes). These final three values are the ones that appear in the VibeX, VibeY, and VibeZ fields of the VIBE message.
Automatically Learn the Throttle Stick Hover Point
In firmware versions APM: COPTER 3.4 and later, a feature has been added that automatically learns the throttle hover point. This prevents issues such as a loss of altitude or a rapid climb when switching from an autonomous mode (e.g., AUTO or Loiter) to a stabilized mode.
If, for any reason, you wish to disable this automatic learning feature manually, you can set the `MOT_HOVER_LEARN` parameter to 0.
Manual testing and setting of the throttle neutral point (current versions no longer feature manually adjustable parameters)
If your aircraft is either overpowered or underpowered, the throttle level required to maintain a hover while in stabilization mode may fall below 40% or exceed 60%. While the aircraft may fly well in stabilization mode under these conditions, it creates a problem: switching to “Loiter” (hover) mode or an autonomous mode can cause the aircraft to unexpectedly ascend or descend. Conversely, transitioning from “Loiter” (position-hold) mode back to stabilization mode could also trigger a rapid ascent or descent, potentially leading to an accident.
Tuning Procedure:
- Disable the `MOT_HOVER_LEARN` parameter by setting it to 0.
- Fly in Stabilize mode for at least 30 seconds to 1 minute.
- After landing, disarming the vehicle will automatically save the flight log. Download the log file from this flight via USB or a telemetry link.
- In the Ground Control Station (GCS), navigate to: Flight Data > DataFlash Logs > Download DataFlash Log via MAVLink.
- Scroll through the logs until you find the ThrOut parameter.
- In the example shown above, the throttle value for a hover is approximately 566, which falls within a normal range.
- Note: If the throttle value is below 300 (30%), your aircraft may be overpowered. This could be due to an excessively high battery voltage (a mismatch between battery voltage and motor KV rating) or an improper weight configuration (e.g., increased weight resulting from a larger-capacity battery).
- If the average value is greater than 700 (70%), your aircraft may be underpowered; in this case, check the compatibility between the battery and motors, or investigate other contributing factors.
Automatic Fine-Tuning and Saving of Fine-Tuning Results
When is auto-trimming necessary?
If your aircraft consistently drifts significantly in one direction—even when flying in windless conditions using stabilization mode—requiring you to constantly make manual stick corrections, you should perform an auto-trim. This allows the aircraft to automatically record the offset, ensuring stable flight.
- We recommend that you first check the levelness of the frame and motor installations to see if any issues are caused by the frame or motors not being perfectly level.
- Next, recalibrate the accelerometer. The horizontal orientation of the accelerometer is critical; if it is not level, it will cause the aircraft to drift in a specific direction.
- If the above steps do not resolve the issue, you can try performing an automatic trim adjustment.
Auto-Trim
Use the auto-trim function to capture your control inputs while in a stable hover, allowing for the fine-tuning of roll and pitch.
1. Find a sufficiently large, windless area to ensure safe flight.
2. Pull the throttle stick down and hold the yaw (rudder) stick to the right for 15 seconds, or until you see the red, blue, and yellow LEDs flashing in a repeating pattern.
3. Take off in stabilization mode, then maintain a stable hover for approximately 25 seconds.
4. Land the aircraft, pull the throttle stick to the lowest position, and wait for about 10 seconds (the trim settings will be saved to the EEPROM).
5. Take off again in stabilization mode to check if the flight is stable. If it is not, repeat steps 2, 3, and 4.
Saving Trim Settings
The process for saving trim settings is straightforward and requires the use of a multi-position switch; in this example, channel 7 (CH7) is used.
1. Ensure that channel 7 has been calibrated during the remote control calibration process and that it can reach a value above 1800 (a 2-position switch can be used for this purpose).
2. In the software, configure channel 7 (CH7) for the “save trim” function.
3. Set Channel 7 to the low position (a value of 1100), then take off using “Stabilize” mode.
4. Use the trim switches on your remote controller to adjust the ROLL and PITCH channels until the aircraft maintains a stable, level hover.
5. Land the aircraft, bring the throttle to its lowest position, and then switch Channel 7 to the high position (a value of 1800) for at least one second. The aircraft will automatically save these trim values.
6. Reset the trim settings on your remote controller back to their original values—typically 0 (i.e., no trim applied).
7. Take off again in “Stabilize” mode and check if the aircraft remains stable. If it does not, please repeat the process.
The content above provides a tutorial on the settings required for the first flight of a multi-rotor aircraft. Please stay tuned for the next article:
《Advanced Settings for Multi-rotor Aircraft》