Closed jesseishi closed 1 year ago
The reason why the Cn_deltaA is zero, is because the FN (yaw moment) was forced to be zero from the FSI model. I do not remember correctly why this was the case but I think it had something to do with the controller. We track a zero sideslip angle and did not want the instability of the yaw moment to affect this. Also the values were relatively small compared to the other coefficients. However, it is true this value is not zero. Bear in mind that the matrix is based on steady state solutions from the FSI, therefore it looks at a deformed wing state. I will send you the updated allocation matrix, if this does not crash the aircraft we can update the library file in the future.
Hi,
In
Dyn_6DoF_v2_0_r2019b/AirborneSystem/FlightControlSystem/AttitudeAndRateLoop/RateLoop/ControlAllocation/allocation
the control effectiveness matrixBa
is calculated based on the DE2019 model. When executing the following code (after having loaded the DE2019 aircraft model and having initialized the sim):You get:
This is unexpected from what I generally know about aircraft control because
Cm_deltaA
is nonzero andCn_deltaA
is zero. This is strange because you would expect that an asymmetric aileron deflection does not have an effect on the pitch moment (soCm_deltaA = 0
) and that it does have an effect on the yaw moment (soCm_deltaA != 0
). Maybe them
andn
subscripts got mixed up somewhere? Or this is correct and just different from what I would expect (very possible)?I dug a little bit further into it and the fits that are done in
Src\Common\initAllSimParams_DE2019.m
seem correct so the data it uses might be false. In that case,B_Axx
are not correct which are loaded fromLib\6DoF\Control_allocation_V60.mat
.