I’ve just maidened my Durandal in an Edge 540. I downloaded the log, but when I try to read it plot.ardupilot.org just gives a “parsing error”. I also can’t open it with Mission Planner or QGC. Help!
I’m seeing the same thing with a Durandal. Looking at the downloaded .bin files directly, they’re the expected size, but the content seems to be nothing but spaces or 0x00. I changed the LOG_BACKEND param to 6 (Block) and generated a DF log, and Mission Planner is OK with that file. The rest of the logs I’ve collected are just empty, looks like.
OK, I take back what I said. Logging on the Durandal seems super weird. Setting LOG_BACKEND_TYPE to 4 (block) seemed to work for a test where I armed it on the bench with the props off, but then I took it out for some flights and got nothing at all in the way of log files. Changed back to 1 and did another flight (~60 seconds hovering in Alt Hold) and checked the logs, and there were 360 log files, all 0 length. Did another bench test with LOG_BACKEND_TYPE set to 1, and got another log. Haven’t gotten anything useful out of it since then.
Yes, I found LOG_BACKEND_TYPE = Block didn’t work at all. No logs were written. What did work was a brand new 32G SD card and using LOG_BACKEND_TYPE = File. I’m downloading now (so slow over radio 3k/s) so lets see if they have zeros or data. Update - the first log is great. So it looks like the problem was the SD Card, and also Durandal doesn’t support Block logging I guess.
Sidenote: I tried a highlend/fast 128G SD card and it did not work at all. It seems 32 G is the max supported.