You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the flight test, if THR_MDL_FAC was set to a value > 0, such as 0.2-0.5, the VTOL motor would continue to spin (observed and confirmed by eyes). I also checked the flight log and saw that the VTOL was spinning at minimum PWM, e.g., 1080.
In the next flight. I set THR_MDL_FAC = 0, and the VTOL motors stopped spinning.were
To Reproduce
THR_MDL_FAC > 0 and transition to fixed-wing mode (in-air or on ground have the same behavior).
Expected behavior
THR_MDL_FAC > 0 and all VTOL motor stop spinning during fixed-wing cruising phase.the
Screenshot / Media
No response
Flight Log
No response
Software Version
No response
Flight controller
CubeOrange
Vehicle type
Hybrid VTOL
How are the different components wired up (including port information)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Good find. I could reproduce in SITL. See the two screenshots below: if THR_MDL_FAC is non-zero, the output of the hovering motors in fixed-wing flight (vtol_state 4) is 1000, while it should be 900 (disarmed).
Describe the bug
During the flight test, if THR_MDL_FAC was set to a value > 0, such as 0.2-0.5, the VTOL motor would continue to spin (observed and confirmed by eyes). I also checked the flight log and saw that the VTOL was spinning at minimum PWM, e.g., 1080.
In the next flight. I set THR_MDL_FAC = 0, and the VTOL motors stopped spinning.were
To Reproduce
THR_MDL_FAC > 0 and transition to fixed-wing mode (in-air or on ground have the same behavior).
Expected behavior
THR_MDL_FAC > 0 and all VTOL motor stop spinning during fixed-wing cruising phase.the
Screenshot / Media
No response
Flight Log
No response
Software Version
No response
Flight controller
CubeOrange
Vehicle type
Hybrid VTOL
How are the different components wired up (including port information)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: