VTOL Early Transition

I have a VTOL that is transitioning early. I have it paying attention to the airspeed sensor, but it appears that the transition to fixed wing does not rely on the airspeed. I have the transition airspeed set to 21. The UAV pretty much takes off in MC mode, and when i start to transition it just falls out of the sky

Here are two logs from similar flight:
https://review.px4.io/plot_app?log=f68e7cee-e753-4f69-b498-ec49d111aa16
https://review.px4.io/plot_app?log=01369c82-3d88-48c3-9633-1f2cc813e96e

I havenโ€™t found any wrong parametrization yet.

I think though we have two separate issues:

  1. finishing transition too early
  2. not accelerating during transition

For 1), the best guess I have is that you got an airspeed sample that was above the threshold. Given how noisy the sensor is that is possible.
I would try to transition in airspeedless-mode (see FW_ARSP_MODE) (only after 2) is though addressed).

For 2) have you checked functionality of the pusher? You should also be able to use in in hover, see VT_FWD_THRUST_EN param.

That is a good idea.

I took a look at the airspeed I do see it being noisy. I am unsure WHY it is that noisy, but I dont see it going over my setpoint of 21 in the logs

@sfuhrer Had my airspeed threshold set to 21
image

Airspeed is calculated using static and dynamic pressure data. When the airspeed is low, noise occurs in the static pressure, making airspeed calculations inaccurate.

Which airspeed sensor do you use?

MRO i2c

Even though they are inaccurate it does not appear that they surpass 21 m/s though

Even though they are inaccurate it does not appear that they surpass 21 m/s though

Well we donโ€™t see a sample it the log above 21m/s, but as we only log airspeed at the low frequency of 5Hz itโ€™s totally possible that we simply missed it by chance.
If you want to investigate that route you could reduce the logging interval here.

Yeah that makes sense to me. Going to ensure that pusher motor is working correctly, then move onto trying to clean up that airspeed sensor. If i have time will increase the logging rate

THank you @sfuhrer

Tried to activate the back pusher for forward flight. Once the back pusher turned on the UAV immediately lost altitude.

https://review.px4.io/plot_app?log=7e551571-6403-4b8e-9c8f-ce7e4aa4abb0

I thought this was a power issue, but I put the drone on the bench and all of the motors were spinning at 100% simultaneously.

Obviously motors under load consume more power than on the bench.

As soon as you start the pusher the MC system gets unstable, the MC motors saturate and the vehicle thus comes down.
I would first validate the MC tuning a bit more: In Stabilized or Altitude mode give it some strong pitch/roll/yaw inputs and see if it tracks decently.
Then try again with the pusher - I would though reduce VT_FWD_THRUST_SC to 0.5 for a start. If you still see a strong effect of it spinning up on the MC system then power issues are the most likely cause.

Yes.

You might be able to see on this that the arms are duct taped together. this thing has already been through a few crashes. It is definitely not PID tuned correctly for MC mode, but it seems like once that back motor kicks on the other 4 lose power. From the logs the vehicle is still telling the motors to spin at high PWM values. It just seems like it doesnt have enough juice.

We are getting a replacement airframe soon. Should be able to test out on an airframe that has better MC PID values (that is more rigid of an airframe as well). THank you for taking the time to answer these questions @sfuhrer

Will post updates once we get the new airframe up in the air

This was a power module issue. The first crash must have damaged it. We figured this out by putting the VTOL in MC mode and enabling the VT_FWD_THRUST_EN parameter. Upon the back thrusting up the UAV fell out of the sky.

Apologies for thinking this was in firmware.

Resolved

1 Like