We are going to upgrade the firmware from v1.14.3 to v1.15.0 for all UAVs in our fleet.
During the flight test after uploading firmware v1.15.0. I noticed that the throttle output suddenly changed in a way I had never faced before. I looked at the log file and discovered that the airspeed/indicated_airspeed_m_s appeared to be correct, but the airspeed_validated/indicated_airspeed_m_s occurred a peak in airspeed, causing the true airspeed abrupt change. As a result, the throttle output abruptly dropped to reduce speed.
The issue seemed serious during the climb test; the throttle should have been steady, but I heard the propeller spinning sound decrease caused by this problem.
I continued to do the flight test, 3 flights. I found the peak (both too high and too low speed) every flight. This is an unsafe condition.
After carefully reviewing the log file, I am confident that the airspeed peak is more than we can observe since the logging rate is inadequate to capture the peak in a short period of time.
Expected behavior
There is no rapid change in the throttle, especially during the climb phase, and the fixed-wing throttle appears more stable.
Describe the bug
FCU: CUAV V6X Airspeed: MS5525DSO Firmware: 1.15.0 Airframe: VTOL
We are going to upgrade the firmware from v1.14.3 to v1.15.0 for all UAVs in our fleet.
During the flight test after uploading firmware v1.15.0. I noticed that the throttle output suddenly changed in a way I had never faced before. I looked at the log file and discovered that the airspeed/indicated_airspeed_m_s appeared to be correct, but the airspeed_validated/indicated_airspeed_m_s occurred a peak in airspeed, causing the true airspeed abrupt change. As a result, the throttle output abruptly dropped to reduce speed.
The issue seemed serious during the climb test; the throttle should have been steady, but I heard the propeller spinning sound decrease caused by this problem.
I continued to do the flight test, 3 flights. I found the peak (both too high and too low speed) every flight. This is an unsafe condition.
After carefully reviewing the log file, I am confident that the airspeed peak is more than we can observe since the logging rate is inadequate to capture the peak in a short period of time.
Expected behavior
There is no rapid change in the throttle, especially during the climb phase, and the fixed-wing throttle appears more stable.