OSD5 min/max/increment parameters keep changing after flights

ArduCopter Copter 4.6
1

I’m having an issue with the OSD parameter editor screens 5 and 6 which I’d set up using MavProxy. For each parameter I set custom min, max, and increment values. I can see that Mavproxy populated the OSD5_PARAMn_ parameters correctly and everything works nicely for a short while.

But after flying the values OSDn_PARAMn_MIN, MAX*,* INCR values have often changed to different numbers. Sometimes this changes on one paramater, other times it affects several.

It happens on three different quads running Matek H743 Mini and Matek H743 Slim. And was happening on Arducopter 4.6.3 and 4.6.2.

There’s no obvious pattern: sometimes the values survive a flight, but usually they’re correct before the first flight and wrong by the second one that day. I now reload my full .param file before every flight, which is inconvenient.

Is this really odd ? Should I raise an issue on Github?

2

My all means raise an issue, but I need a way to reliably reproduce it otherwise I won’t be able to fix it. It seems very odd - the values you describe are regular parameters.

3

I’ve never been able to pinpoint when exactly it happens. What do you think if I write a script that beeps as soon as the change happens?

4

See if you can replicate in SITL with your parameters. Please post your parameters here as well. There is likely some kind of memory corruption going on.

5

I assume memory corruption is unlikely as (a) it only happens to the OSD5 MIN, MAX, and INCR parameters, and (b) happens across three flight controllers.

6

I’m thinking it’s more like some sort of rogue code, maybe Ardupilot tries to estimate the values if they’re not set and forgets to respect them if they have been set.