Browse Source
Setting a parameter on ArduPilot causes the autopilot to emit the new value in a PARAM_VALUE message, so we do not need to fetch it ourselves. Fetching it ourselves causes subtle problems for the autotest suite where a PARAM_VALUE is currently in the uart buffer - so the autotest set_parameter has consumed one PARAM_VALUE message (the auto-emitted one). If it immediately does a set_parameter then the next PARAM_VALUE it sees will be the OLD value as the value comes out of the uart.c415-sdk
1 changed files with 7 additions and 1 deletions
Loading…
Reference in new issue