I get errors in log writing on file whenever i have any other mavlink object on the aircraft (in my case basecam).
I have had this problem for years now, if i enable log to file and store it with mavproxy or mavlink-router it works if ardupilot is the only object that has a mavlink id on board. As soon as i have any other object with a mavlink id it generates an error and doesn’t write logs to companion directory anymore. As soon as i remove the gimbal it restart working again.
I hoped that this problem would have been resolved in 4.1.x but i still have it on latest rc release.
I can’t make the serial comunication to the gimbal private because i need its mavlink messages to be visible.
I guess this is really an issue with the logging software on the companion computer? My guess is that it is not related to the the software on the autopilot (but I could be wrong of course).
@WickedShell has also recently reported some issues with logging on the companion computer (I think) so he may have some advice.
I guess @peterbarker might have some advice as well.
By the way, I think that on our companion computer images for the RPI4 (and other companion computers) we install dflogger.