List of default params that need an update

[RomanBapst]

This is to track parameters which have a default that does not work well on practice or leads to inferior performance on pretty much every airframe.

Parameter name	default	suggested
MPC_Z_VEL_I	0.02	0.1
MPC_ACC_DOWN_MAX	10.0	3.0
MPC_ACC_UP_MAX	10.0	4.0
SYS_FORCE_F7DC	0	2
MPC_POS_MODE	1	3
MPC_ACC_HOR	5	3
MPC_ACC_HOR_MAX	10	5
FW_RR_I	0.01	0.1
FW_PR_I	0.01	0.1
FW_YR_I	0.01	0.1
MPC_Z_MAN_EXPO	0	0.6
MPC_XY_MAN_EXPO	0	0.6
MPC_YAW_EXPO	0	0.6
MPC_MAN_Y_MAX	200	150

[LorenzMeier]

I think we need this in v1.9.2 already as we otherwise keep this issue too long.

[DanielePettenuzzo]

SYS_FORCE_F7DC worries me a bit because the default is set to disable dcache. With dcache disabled we are very close to 100% cpu on fmu-v5 if we have a companion link, run uavcan or run the avoidance interface (many users could be hit by this). I just think that currently the risk of crashing due to a maxed out cpu is higher than actually hitting the dcache errata.

[dagar]

SYS_FORCE_F7DC worries me a bit because the default is set to disable dcache. With dcache disabled we are very close to 100% cpu on fmu-v5 if we have a companion link, run uavcan or run the avoidance interface (many users could be hit by this). I just think that currently the risk of crashing due to a maxed out cpu is higher than actually hitting the dcache errata.

@DanielePettenuzzo I'm pushing for a proper fix. #12435

[dagar]

@RomanBapst more updates coming or should we start making these changes (for v1.9.3 at this point)?

[bresch]

We're using MC_POS_MODE 3 (jerk-limited smoothing) since at least January on all our vehicles and I think it's the right time to change it to the upstream default. It will also help to receive more feedback from the user and the test team to improve it further.

[fabianschilling]

The default EKF2_EV_DELAY of 175 ms seems rather high for flight with motion capture systems. A value around 50-100 ms could be a better default.

[julianoes]

@LorenzMeier

I think we need this in v1.9.2 already as we otherwise keep this issue too long.

No, v1.9.2 is a patch release to fix critical bugs. I don't think people are expecting tuning changes. v1.10 is only 1.5 months away anyway.

[LorenzMeier]

@julianoes My comment was in relation to a different list you’re looking at now. However, we need to talk through a couple of these parameters - a broken configuration is as bad as a broken piece of code. What is clear is that the core dev team has been flying different defaults than were released, which makes this a 1.9 release bug. We should treat this as bad as an actual code issue, because the consequence for users is the same: The performance is worse than what has been demonstrated in pre-release QA testing.

[MaEtUgR]

Just wanted to mention the pr for UX parameter default changes here because it seems related: #12346

[jkflying]

Another potential one is THR_MDL_FAC, it defaults to 0 which is a linear relationship between PWM and thrust, when the relationship is theoretically quadratic. A better value would be ~0.65, to take into account some linearities, and make the PIDs work correctly at all different thrust values.

Edit: actually, going back to when it was added, it was 0.65. It was set back to 0 in #6073 after flights with a QAV250, but no explanation why. I guess it made the throttle stick feel different in stabilized/acro? Maybe we then need an inverse function to apply to the throttle stick to keep the feel the same.

[julianoes]

Notes from devcall:

• @RomanBapst: there might be one more param for trigger interval
• @RomanBapst: will be done when the PR is merged, presumably it will go into 1.10 since 1.10 should be released in 5 weeks already.