mirror of https://github.com/ArduPilot/ardupilot
1075e13352
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. |
||
---|---|---|
.. | ||
ArduCopter_Tests | ||
ArduPlane_Tests | ||
ArduRover_Tests | ||
ArduSub_Tests | ||
Generic_Missions | ||
XPlane | ||
aircraft | ||
default_params | ||
jsb_sim | ||
logger_metadata | ||
param_metadata | ||
pysim | ||
template | ||
web | ||
web-firmware | ||
win_sitl | ||
README | ||
__init__.py | ||
antennatracker.py | ||
arducopter.py | ||
arduplane.py | ||
ardusub.py | ||
autotest.py | ||
balancebot.py | ||
bisect-helper.py | ||
build-with-disabled-features.py | ||
common.py | ||
examples.py | ||
fakepos.py | ||
fg_plane_view.bat | ||
fg_plane_view.sh | ||
fg_quad_view.bat | ||
fg_quad_view.sh | ||
junit.xml | ||
locations.txt | ||
quadplane.py | ||
rover.py | ||
run_in_terminal_window.sh | ||
sim_vehicle.py | ||
swarminit.txt |
README
This is an automated test suite for APM