well, that bitmask is every option enabled, which you will don’t need and can bog the CPU down. Currently there are twenty options in the log file
As you can see, each option is given a value. You add up the values selected to find out what the log_bitmask value is. In your case, EVERY option would be enabled to get that result. IMO that’s far too much logging going on.
I don’t have optflow, but my bitmask setting is 10230. That enables the following: ATTITUDE_MEDIUM, GPS, ControlTuning, NavigationTuning, RCIn, IMU, Commands, Current, RCOut and Compass.
My opinion, the most important things to log are RCIn and RCOut as well as IMU.
Bizarrely I have been checking all the earlier log files on the SD card and found that they are all readable except the three from when I was actually flying, all the ones built whilst testing on the workbench are fine.
Just to test I have formatted the memory card and will start again this weekend. Tests done on the bench show new logs are readable so perhaps it was just a card corruption issue.
Mine is set at 176126 from when I loaded 3.3.3. I’ve never done the math to see exactly what I’m logging but everything I have ever needed to view has been logged. Not a very educated answer but all is working well.
RC In: ON
RC Out: ON
From what I understand, some new logging parameters have been added since 3.2.1. They always get added to the end of the bit list is my understanding. I’m not sure that 3.2.1 has the last three (MOTBATT, IMU_FAST,IMU_RAW).