I tried to check the Ardupilot v4.0.1-dev(4a688e59) firmware on the Pixhawk 2 CubeBlack, but the issue was still coming out.
The details are as follows.
*Note that no sensors are connected to the FC board for testing purposes.
[Case1. Ardupilot v4.0.1-dev(4a688e59) firmware on the Pixhawk2 CubeBlack]
The parameter values related to logging are as follows.
Logging was performed on the CC board connected to FC board through the dataflash_logger module included in Mavproxy. As a result, the log file size is 1825000 bytes
If I check the log file size recorded on the SD card of FC board through Mavproxy, the log file size is 3266725 bytes
[Case2. Ardupilot v3.6.2 firmware on the Pixhawk2 CubeBlack]
The parameter values related to logging are as follows.
Logging was performed on the CC board connected to FC board through the dataflash_logger module included in Mavproxy. As a result, the log file size is 726000bytes
If I check the log file size recorded on the SD card of FC board through Mavproxy, the log file size is 195584bytes (Result after deleting all logs by “log erase”)
Is it correct that the timeus value from log downloaded from the FC board and the timeus value from log collected by dataflash_logger in mavproxy are different from each other?
Logging was performed on the CC board connected to FC board through the dataflash_logger module included in Mavproxy. As a result, the log file size
is 1825000 bytes
image
Well, it’s cool that dataflash_logger is working for you. But the data
that you get from this will NOT be the same as that you get from
downloading the logs; they do log slightly different things. (DFS and DMS
messages).
If I check the log file size recorded on the SD card of FC board through Mavproxy, the log file size is 3266725 bytes
image
OK, that disparity is a little too large. You’re dropping vast numbers
of packets (See DMS.N and DMS.Dp) - almost certainly because your serial
baudrate is too low and the data simply cannot be shifted fast enough.