Beat Küng 1dbeec6a19 logger: do not write param changes if _should_stop_file_log is set ...

_should_stop_file_log is set after disarming: logging continues for 1s
to measure the CPU usage.
During that time, other modules might change params (such as ekf), and
we don't need to have these the log. However currently all modules do
not notify the system when setting params after disarming.
Meaning this patch is not strictly needed, it's more a preventive
measure.

2017-12-07 11:55:51 +00:00

..

array.h

logger: add copyright to files

2016-05-14 11:27:07 +02:00

CMakeLists.txt

ignore -Wsign-compare per module

2017-09-07 10:27:36 +02:00

log_writer_file.cpp

log_writer_file: register hardfault handler before opening the log file

2017-08-16 16:46:56 +02:00

log_writer_file.h

hardfault_log: move hardfault_store_ulog_filename to logger module

2017-07-07 17:06:48 +02:00

log_writer_mavlink.cpp

mavlink ulog: advertise ulog_stream topic before subscribing to ulog_stream_ack

2017-08-16 16:46:56 +02:00

log_writer_mavlink.h

logger: add mavlink write backend

2016-10-19 13:13:47 +02:00

log_writer.cpp

astyle src/modules/logger

2017-01-29 01:18:32 +01:00

log_writer.h

logwriter: fix shadowing compiler warnings

2016-10-19 13:13:47 +02:00

logger.cpp

logger: do not write param changes if _should_stop_file_log is set

2017-12-07 11:55:51 +00:00

logger.h

logger: Add logging profile to support comparison of multiple sensors (#8134)

2017-10-20 09:30:55 -04:00

messages.h

ULog: add INFO_MULTIPLE & FLAG_BITS messages

2017-07-07 17:06:48 +02:00

params.c

logger: Add logging profile to support comparison of multiple sensors (#8134)

2017-10-20 09:30:55 -04:00