I am trying to use the raw logging feature on the Cube Orange Plus to characterize motions and vibrations while in flight. I have set up raw logging and set it to 8k Hz, but I see that there are times where logging stops for up to 700 ms. I bought a new SD card (30 MB/s) hoping to fix the issue, but I saw marginal benefit. It seems to be logging the GYR at 2000 Hz , with 100 Hz samples every 15 samples. There are also periods where it is logging at 2000Hz with jumps to 200 Hz.
I was wondering if anyone has experienced this or corrected this issue before. I think I can handle the jumps to 100-200 Hz, but I would like to eliminate the large gaps on the order of 100s of ms.
Thank you for the reply Siddarth, I double checked the parameters and there were some that were different. I walked through the steps again and I seem to be getting better timing now. There are still some spikes where it drops below 10 Hz, which I think we can tolerate, but should I expect it to be better? I am attaching a graph of the differential times. I see that it defaults to around 60 kHz, 3.3 kHz, and can jump to under 10 Hz.
@opti Worth trying disabling CAN (if enabled), potentially other IMUs to see if that makes any difference.
I know in ardupilot the speed is limited to around 12.5MBytes/s (25MHz frequency) for SDCard, so SDCard faster than that might not be very helpful. It can be increased, hardware is capable, software will need some work.
These steps did not improve the logging any. I think this is sufficient for what I am trying to do.
I will note that the speed should not be a problem using the size of the log file (Cube writes bin but log is worst case) and the maximum timestamp, the write speed was less than 1 MB/S.
