#4 Test Flight and Black Box Analysis - T-Motor Mini Racer F7 + Betaflight 4.3 + BLHeli 32.8.3 Installation and Setup

ChineseBilibiliFPV knowledge5:29
Watch on Bilibili
← Return to Simplified Chinese tutorials and video guides

This is the fourth in a series of installations of the T-Motor Mini Racer F7, Betaflight 4.3 and BLHeli 32.8.3, focusing on evaluating the complete configuration using test flights and black box curves. The conclusion of the video is not that "the preset is perfect", but rather: the noise control of this 20×20 flight controller is generally good, and there are no obvious abnormalities in actual flight. However, the current Preset still does not fully match the aircraft, and oscillations can be seen in some control signals, so further fine-tuning of the frame, motors and blades is required.

Establish a comparable usage baseline first

The author made a subjective comparison between the new board and another 20×20 flight control that he has used for more than a year, and said that it is difficult to clearly distinguish the advantages and disadvantages for the time being. This conclusion is important: when the difference in actual flight is not obvious, the curve should not be over-interpreted to prove that the upgrade is effective. Size, ease of installation, configuration process and stability were also included in the overall rating.

This article corresponds to the combination of Betaflight 4.3 and BLHeli 32.8.3 in 2022. The filtering, preset and log fields of modern firmware may be different, so when reproducing, you must record your own firmware version, rack, motor, propeller, installation hardness and sampling conditions.

Look at noise from a black box rather than just relying on hearing

After the test flight, a log with sufficient duration and relatively complete movements should be selected to check the overall outline of the gyro noise and control curve. The video rated the aircraft as generally quiet, indicating that there were no obvious major problems with noise control; this is mutually confirmed by the fact that there was no strong sense of abnormality during the flight.

"Overall quiet" does not mean perfect in every band and on every axis. Whether the curve is trustworthy also depends on the log sampling rate, throttle range and action content. Hovering, acceleration and rapid attitude changes should be observed separately to avoid using one short clip to draw conclusions about the entire aircraft.

Preset is the starting point, not the final answer

The author points out that the current Preset's adaptability to this aircraft is still not high enough, and some low-frequency or control signal curves are not smooth enough and oscillate, although it is not easy to feel it directly during actual flight. This shows that presets can quickly establish a security baseline, but they cannot replace log review for specific hardware.

In the next step, only one type of parameters should be changed at a time, and the black box records before and after modification should be retained. First eliminate mechanical looseness, blade damage and flight control installation problems, and then evaluate filtering and PID. Don't drastically reduce filtering or increase gain just to make the graphics smoother; the goal is to balance noise, response, temperature, and repeatable real-flight performance.

Form traceable debugging conclusions

Record the firmware, Preset, Rates, filtering, PID, blades and environment for each test, and mark the corresponding changes in the log. In this way, it can be determined whether a certain oscillation is caused by parameters, mechanical state changes, or different test actions. The configuration management and black box tools provided in the video introduction are suitable for preserving this history.

If the flight feel is normal, the overall noise is controllable, and the motor temperature is safe, you can use the current configuration as the baseline and then optimize it in small steps; if there are obvious oscillations in both logs and actual flight, you should roll back the latest changes first. The value of black-box analysis is to narrow down the scope of the problem, not to replace security checks with a single curve.

Operation steps

  1. Record hardware and firmware baseline

    Save T-Motor Mini Racer F7, Betaflight 4.3, BLHeli 32.8.3 with current Preset and mechanical configuration.

  2. Combined installation and actual flight evaluation

    First determine whether there are perceptible abnormalities in use, configuration and flight, and then enter the black box for detailed inspection.

  3. Select a log segment that is long enough

    Select records covering steady throttle and representative movements to observe the overall noise profile.

  4. Identifies oscillations not covered by the preset

    Pay attention to the low frequency or control signal that is still rough, and use it as a basis for small adjustments, rather than making big changes to the parameters immediately.

FAQ

What does the author think of the flight control noise performance?

Generally quieter, it is difficult to directly distinguish the advantages and disadvantages from the 20×20 flight controller used by the author before, but the curve still has oscillations that can be further optimized.

Do I still need to look at the black box after applying Preset?

Required. The Preset is just a general starting point, and the specific frame, motor, propellers, and installation methods may require further fine-tuning.

Can the log be ignored if the actual flight does not feel any oscillation?

Cannot be completely ignored. Minor problems may not be obvious temporarily; check the logs, mechanical status and motor temperature at the same time before deciding whether to adjust.

Can the 2022 parameters be directly used in the new version of Betaflight?

Not recommended. Filtering, Preset and default values ​​may have changed, the current firmware documentation should be used and the log baseline re-established.

Full timeline transcript

Transcripts are arranged according to video time, making it easy to quickly locate the explanation content. Transcript language: Simplified Chinese.

OK Finally, let’s briefly talk about the use experience. I have been using a 20x20 board from Helenation for about a year or so. I think that board is the smallest board I have ever used. But with this board, I still can’t.

There is no way to tell which board is familiar with which one. So I think this board is pretty good for noise control. Then on the other hand, the use and configuration have been summarized during our previous installation. Overall, I think this is a pretty good board, although when we were flying

Let’s take a look at the noise. Find a longer one and look directly at the cable modification for this noise. Generally speaking, some aircraft are relatively quiet.

Although this place is not particularly perfect, the suitability of this Presets for an aircraft is still not particularly high, and some further adjustments are still needed, but overall it is relatively quiet. Here, you can see that this low signal is still not special, not particularly smooth, and it still causes a lot of vibrations, although I don't feel it when flying.

That’s it for these videos. If you have any questions or feedback, please leave a message or acknowledge it below. Thank you all for liking, collecting, following and forwarding. I am Hua Ran. See you next time.

English