- Apr 09, 2019
-
-
Daniel Agar authored
-
- Apr 03, 2019
-
-
Daniel Agar authored
-
- Mar 21, 2019
-
-
Beat Küng authored
-
- Mar 16, 2019
-
-
Daniel Agar authored
-
- Feb 11, 2019
-
-
DanielePettenuzzo authored
-
- Jan 24, 2019
-
-
Daniel Agar authored
-
- Jan 20, 2019
-
-
Daniel Agar authored
-
- Jan 09, 2019
-
-
Beat Küng authored
- I enabled it by default mostly for testing purposes - Disabling it reduces resource usage as most setups don't need it
-
- Dec 22, 2018
-
-
Julian Oes authored
This is a step towards isolating time from the system.
-
- Dec 21, 2018
-
-
Christian Rauch authored
-
- Dec 07, 2018
- Nov 26, 2018
-
-
Daniel Agar authored
-
- Nov 23, 2018
-
-
Mara Bos authored
The threads running commands for clients through the Posix daemon used to write to a char buffer through snprintf (etc.) which was then written directly to the file descriptor, whereas in the other case printf (etc.) was used to write to stdout (FILE*). Both versions used some macro's and repeated code to have the same output. This change unifies these two cases by using a FILE* in both cases. The (line) buffering is done by the standard C library's implementation (just like with stdout), and px4_log.c now uses the same code in all cases (using fprintf, etc.) for printing (colored) output.
-
- Nov 20, 2018
-
-
baumanta authored
-
- Nov 19, 2018
-
-
Daniel Agar authored
-
- Nov 16, 2018
- Nov 06, 2018
-
-
bresch authored
- move the update after the integration: a new computed jerk has an impact at the next epoch only - add jerk reduction in case of too large integration time: when a jerk of "min_jerk" during dt is too much - add jerk reduction if the integration time is larger than the predicted one and that integrating that jerk would lead to an acceleration overshoot - rename some variables
-
Beat Küng authored
- fsync can be a long blocking operation, so we need to make sure the main logger thread does not block during this time, when it tries to aquire the mutex - fixes calling fsync on an invalid file descriptor
-
- Oct 26, 2018
-
-
Beat Küng authored
-
Beat Küng authored
-
Beat Küng authored
To get it field-tested. This can be reverted for a release...
-
Beat Küng authored
-
Beat Küng authored
- mission logs are stored in a separate directory mission_log - It's disabled by default - Does not increase RAM usage if disabled (if enabled, only 300 bytes) - Log rotate does not apply to the mission logs
-
Beat Küng authored
Some message formats are longer than the 300 bytes. We can split the writes because we have to wait until they are written anyway.
-
Beat Küng authored
256 subscriptions are enough for now. Reduces RAM usage by 300 bytes.
-
Beat Küng authored
Not used yet, it should not affect anything, except for slight RAM increase.
-
Beat Küng authored
Previously the formats of all known uorb messages were written. - reduces header size by about 13KB - reduce ulog_message_format_s size to reduce required stack size. Largest message format is about 1000 bytes.
-
Beat Küng authored
-
Beat Küng authored
-
- Oct 03, 2018
-
-
David Sidrane authored
-
- Sep 27, 2018
-
-
Julien Lecoeur authored
-
- Sep 24, 2018
-
-
Beat Küng authored
Make sure vehicle_air_data & vehicle_magnetometer are logged if ekf2 replay is disabled.
-
- Aug 31, 2018
-
-
Daniel Agar authored
-
- Aug 30, 2018
-
-
Daniel Agar authored
- fixes #10345
-
- Aug 27, 2018
-
-
Hamish Willee authored
-
- Aug 20, 2018
-
-
Hamish Willee authored
-
- Aug 17, 2018
-
-
Paul Riseborough authored
This data is published at the GPS publication rate and only when on ground.
-
- Aug 16, 2018
-
-
Daniel Agar authored
-