Hey there,
I have a few problems involving recording flight data with the dataflash logs:
Problem 1:
I recently tried to change the type of information that was stored on the dataflash logs on board my Pixhawk, and to change this I went to the parameter LOG_BITMASK and I changed this parameter to the recommended bitmask value of 65535 and then clicked "write params". After doing this, I proceed to open my dataflash logs and I found that I was basically recording no information at all in these files. No ATT data, no GPS, nothing.
On various websites on the internet, they say use the Log Bitmask parameter in order to select what data you want recorded (I originally wanted my RC commands to be recorded, as they were not being stored in any of my dataflash logs). Can someone please enlighten me as to how I can change what data is being stored in the dataflash logs?
Problem 2:
After seeing that my dataflash logs were giving me no data, I have been trying to create dataflash logs and download them through MavLink in order to see if they would somehow correct themselves and have the data that I originally requested (LOG_BITMASK = 65535). As I was doing this, I tried deleting all of the files though Mavlink in Mission Planner. First I clicked "clear logs" and then I got a message saying that I should wait for 30-90 seconds. I waited for a few minutes, I got no message at all about the status, and then I closed the box. I am not sure if this messed up my Pixhawk/SD card, but now there are absolutely NO dataflash logs being recorded at all. Did I corrupt my SD card and/or Pixhawk? How can I get my Pixhawk to record dataflash logs again?
Any help is always appreciated.
Thanks for your time. Happy flying!
Cheers,
-Andrew
Replies
Andrew, I just came across the same problem today. I was learning how to access and graph the dataflash logs to check vibration levels. I noticed that there were quite a few log files on the Pixhawk so I hit the "clear files" button. Following that move, no further log files were being created. I looked at the log_bitmask parameter and it was a number that was not listed in the suggested options, 176126. So I tried the Default+IMU setting, 958 and presto, it started recording again. Went back to 176127 and nothing...
I have no idea what the original number was before I did the clear command, but 958 worked both times I tried it. I did not try any other bitmask settings so I can't comment on 65535.
Regards,
Doug