- Jan 09, 2018
-
-
Daniel Agar authored
-
Daniel Agar authored
-
- Jan 08, 2018
-
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
This is required for generating documentation
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
This allows to build all params and test them.
-
Lorenz Meier authored
This hides these parameters by default from the user.
-
Lorenz Meier authored
This helps with param transfers and will hide these params by default from the user.
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
This makes it easier for QGC to parse.
-
Lorenz Meier authored
-
Lorenz Meier authored
This allows to mark parameters as volatile.
-
Lorenz Meier authored
No functional change, but this avoids numerical issues in the check routine. Since the routine will tend to false positives, we will tend to send more param updates than required in case of numerical noise of the float representation. This is desired, as we prefer to send two updates rather than not sending one.
-
Lorenz Meier authored
Volatile parameters are ones that do not represent a fundamental configuration change but rather than incrementally changing settings. These include logged flight hours or sensor offsets. Marking them as volatile avoids these parameters forcing time-consuming telemetry updates.
-
Lorenz Meier authored
Parameters can change not just based on GCS request, but also due to internal code or requests by a different valid connected control authority such a cloud service. This change ensures that all connected systems get updated via MAVLink asynchronously.
-
Lorenz Meier authored
All param handling happens in the param manager.
-
Lorenz Meier authored
Pure comment edit
-
Lorenz Meier authored
This helps subscribers to understand if they should update their parameters or not. We will extend this with other flags such as the current save status and alike.
-
Lorenz Meier authored
-
Lorenz Meier authored
This should help keeping the GCS up to date about asynchronous changes on the autopilot.
-
Lorenz Meier authored
This marks the learned bias parameters as volatile (as they change in flight without external configuration) and marks them as system level, which should hide them by default from the UI
-
Lorenz Meier authored
-
Lorenz Meier authored
This has been out of use for more than a year now and is no longer required.
-
Daniel Agar authored
- fixes #8621
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
- Jan 07, 2018
-
-
Anthony Lamping authored
two xml log files are generated for each rostest. they're named according to the launch file, which is reused for each mission test. currently subsequent tests overwrite the previous test's logs. this renames them after they're generated, appending the mission name to the end of the file name.
-
yinjiajie authored
-
yinjiajie authored
-
- Jan 06, 2018
-
-
stmoon authored
-
stmoon authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-