This FC uses onboard dataflash memory instead of a SD card and it seems that I may be running out of memory which prevents completing Autotune and writing the complete log?
When running Autotune on two occasions, one in pitch and roll and the other in roll, the autotune seems to complete on both occasions but instead of the usual beep and LED signal the quad just sits there. After landing with autotune still enabled and then disarming the PIDs are not written.
Attached is the .bin file of the autotune in the roll channel and it just stops midflight.
If anyone can provide some guidance on this issue or parameter settings (LOG_FILE_BUFSIZE or LOG_FILE_MB_FREE??) that would help, it would be appreciated.
It appears that when the log is downloaded it initially stores it on my machine with a name of â1 1-01-1970 1-00-00 pm.binâ. When the download is complete It then converts the file to one with another date.
If for some reason, there is already a file called â1 1-01-1970 1-00-00 pm.binâ in the download folder, it wonât overwrite the file and gives an error and the log is not downloaded. This only my guess what is happening, but I know I have to delete the â1 1-01-1970 1-00-00 pm.binâ to get the download to work. Anyone know how this works?
Thanks for the replies and it seems this FC is not ideally suited for ArduCopter. I have Kakute H7 V1 which I might try instead, unless others have issues with this or there are other better suggestions?
I flew this board fine. Obviously you have to be a little bit careful with the logging, but its manageable. A lot of the newer H743 boards have this logging setup.
The reason you ran out of log space is you have FAST ATTITUDE logging enabled - this will fill up the log really quickly. Try with 4112382 in LOG_BITMASK - should work a lot better. Not really worth setting FAST ATTITUDE until you are ready to do a test flight.
@Peterarnold I have seen that if you have a working gps and activate the geofence the log files are downloaded with the correct date and the correct name. Here you see a full log message (chip full) after flying 18 minutes with my 3" coper 2s li ion powered
I tried the LOG_BITMASK setting with Autotune which ran for about 3 minutes then stopped. Nothing written in the log so I thinks it is a faulty FC. A dog destined for the thrash can!
Thanks for all the help with this!
Note that the flash log can get corrupted. If you think this is the case do âclear all logsâ in mission planner - this will wipe it and often solves logging problems with this driver. Longer term I have a plan to support littlefs which should be more reliable than the current scheme.
@andyp1per.
The bit I donât understand is why the autotune stopped. If logging failed or became corrupted would that stop the autotune? Both issues seem to occur together.
Yeah, I am not sure. Generally if logging has failed this will show up as an error on boot and you wonât be able to arm. It does sound a bit strange - and you may be right, maybe the flight controller has a defect - just pointing out that flash-based logging is a little flaky, but as long as you realize this its fairly straightforward to work around. Are you using log rotation? You should with this board.
