I am having trouble logging my flights for tuning purposes.
Unfortuately I am using a speedybee f405 mini with 8mb flash, which seems to be very limiting.
My proceedure is the following:
Do a tuning flight, finish before the flash is full, land, disarm, wait a little bit, arm again and enjoy the rest of the battery, land, disarm, wait again, unplug. My intention is to create a log specifically for tuning and a second one for flying around.
I am loosly following Chris Rossers tuning guide.
My questions are:
Why was only one log created? (see log below)
Why are so many information missing? (RPM, vibes…)
I tried to do north-south/east-west shuttle runs in the beginning to tune the Horizontal Velocity Controller but the data under PIDE and PIDN are useless.
Are my parameters generelly suitable for logging, keeping my FC in mind?
I also have a copter with SpeedyBee F405 mini (I know, I know - I do also have a couple of copters with H7).
My logging setup is still sub-optimal, but I’m using the following parameters:
LOG_FILE_DSRMROT,1
LOG_FILE_MB_FREE,7
The idea being that every time I arm the copter it clears the flash and starts a new log.
I’ve also tried setting
LOG_BLK_RATEMAX,10
but that doesn’t reduce the log file size much, and seems to cause problems with some of the Ardupilot log review tools.
You should have usable vibes, PIDE & PIDN data. If the log is truncated due to lack of space you may find that it isn’t read properly. Your LOG_BITMASK is set to record data that you don’t need, and the FC might not be able to keep up. I’m using 145406, and could probably turn more logging off.
Do you have Speedybee Mini ESC with Bluejay firmware? If you have the correct Arducopter parameters (including SERVO_DSHOT_ESC) you should have partial telemetry for each ESC, including motor RPM.
