Balduin e4f4d240b6
last few hacks to make standard_vtol pass
- higher airspeed targets
 - higher pusher thrust
 - higher takeoff attitude (arsp failure test)

   in the airspeed failure case, the lowered airspeed reading causes the
   controller to want to speed up until the (wrong) airspeed is at the
   setpoint, i.e. the real airspeed quite a bit faster.  without these
   fixes, tecs does a nosedive to regain airspeed, but never becomes fast
   enough (with already maxed out pusher thrust). we pervent this with
   the first two adaptations, while the last one gives space for the
   remaining nosedive.

   fix this permanently by:
    - ensuring the model makes sense definitely (pusher thrust, mass, aero
      properties)
    - noticing the failure faster
    - adapting tecs so it doesn't nosedive?

 - stop sending airspeed in sih

   src/modules/simulation/sensor_airspeed_sim/SensorAirspeedSim.cpp
   is already doing that. in the sensor failure case (wrong), that implements
   the failure, but the SIH one not, giving conflicting data. so switch
   it off

 - larger acceptance radius

   quadx position mode is just not that accurate. is it a control/model
   mismatch problem, or a simulation problem?

 - wait longer for disarm in test_vtol_rtl

   this would fail at large speed factors previously. timing bug or
   acceptable small variation?
2025-11-24 09:13:14 -08:00
..
2025-08-21 16:46:06 +02:00