Thank you for reporting the issue, we'll have a look at this. In the
mean time, the sdlog in master has changed a bit in order to log
into several files, with "flight recorder" feature using the
periodic telemetry system (https://github.com/paparazzi/paparazzi/pull/1144,
to be documented...).
Maybe the issue is fixed in master now, but we still need to check
for both master and v5.4.
Le 24/04/2015 09:23, Andreas Philipp a
I'm using the SDLOG function for the "humid_sht" and
"airspeed_ets" modules (TEMOD-I2C-R1 would be a next candidate
...) on the APOGEE board (see below at PS for the files I use for
It works fine, however the filenames that are created by SDLOG
cause reproducible troubles:
sometimes the mechanism of counting up the file name numbers
(depending on the already existing files) does not work.
Instead there are filenames including negative numbers (-36 and
-2147483648 (smallest 4byte integer) are frequently appearing) and
these files are frequently overwriting old files with the same odd
name. We have lost some measurement data (very very early in the
morning :)) by this, when we switched the plane off and on after
Please find four directory listing screenshots attached, each
captured after switching off and on the APOGEE and after some time
of measurement plugin in the USB cable to the computer
respectively. First (01.png) everything is fine (pprzlog_001.LOG),
next (02.png) there is an additional file pprzlog_-2147483648.LOG
(ugly but containing the new data), at the next measurement
(003.png) we get a pprzlog_-36.LOG which is finally (04.png)
overwritten (see the size and date of the file).
It seems, the integer which is used for the filename is sometimes
uninitialized or so.
I found the function "getNextFileName" in
But there the integer maxCurrentIndex is initialized to zero in
Can this be a hardware or filesystem issue? However, it happens on
other APOGEE boards too. The filesystem is 8GB FAT and it happens
on other (class 10) micro-SD cards too. I'm running the APOGEE on
3S Lipos and 4S Lipos and don't think it's a power issue.
I'm currently using Paparazzi version
I know that this didn't happen half a year ago or so, however I
cannot say exactly with which version ...
Can someone please help in finding this bug?
PS the modified files for using SDLOG with humid_sht and
airspeed_ets were reported formerly here (still not included in
Paparazzi-devel mailing list