Hello
Does someone know why after downloading log files with the “Download DataFlash Log Via Mavlink” option, a new log file will not be created until only rebooting the Ardupilot?
Thanks
Hello
Does someone know why after downloading log files with the “Download DataFlash Log Via Mavlink” option, a new log file will not be created until only rebooting the Ardupilot?
Thanks
That is probably a bug. But after downloading logs the ekf drifts, and you need to reset anyways.
Why do you want to avoid the reset? What is the use case?
Thanks
Why the EKF drifts?
The use case is for working with the PX in ground tests, connected with USB and performing some test runs with downloading logs in between. Opening and closing logs is done with arm/disarm commands. Reboot of the unit causes some trouble in activating the setup again.
The EKF drifts because rest time tasks do not run in real time any more during log download. Timing jitter is too big during download
Hi, I am facing a similar issue. A new file is only generated after reboot and not after arming. If I arm disarm multiple times without rebooting it keeps writing in the same file. Is this a bug or just configuration (could not find anything similar in the docs)
It is a configuration issue. Just configure it to do one log per arm event using LOG_FILE_DSRMROT
It`s all there in the documentation