Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uSD card: Add synchronous logging mode. #414

Merged
merged 1 commit into from
Mar 28, 2019

Conversation

whoenig
Copy link
Contributor

@whoenig whoenig commented Mar 25, 2019

The synchronous logging mode can log variables synchronously in the
stabilizer loop. This helps to analyze flight crashes etc. where
the order and consistency between variables is crucial. The older
(asynchronous mode) is retained, although the config file format
changed slightly.

Tested on a CF 2.0 (both synchronous and asynchronous modes using
the config.txt that is part of this repository.)

The synchronous logging mode can log variables synchronously in the
stabilizer loop. This helps to analyze flight crashes etc. where
the order and consistency between variables is crucial. The older
(asynchronous mode) is retained, although the config file format
changed slightly.

Tested on a CF 2.0 (both synchronous and asynchronous modes using
the config.txt that is part of this repository.)
@tobbeanton tobbeanton merged commit 0583fa6 into bitcraze:master Mar 28, 2019
@tobbeanton
Copy link
Member

Great functionality. Our dream would be to be able to configure and trigger it from the cfclient, maybe one day :-)

@tobbeanton
Copy link
Member

Out of curiosity I checked the task-load and the USDTASK is taking around 40% when testing the config.txt file in synchronous mode. Since the IDLE task is also at 40% there shouldn't be a problem but might be worth to have this in mind.

@krichardsson krichardsson added this to the next-release milestone Aug 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants