I have been experiencing some weird logging behavior by APM. Im running APM 2.26, and im using the default flight logging settings.
After every flight, APM somehow auto reverts its logging settings to the following:
logs enabled: GPS PM CTUN NTUN MODE CMD.
And the list of log number displayed does not tally with the ones that I can download. ie. CLI shows I have log 42-57, but I can download only 1-16.
GPS PM CTUN NTUN MODE CMD is definitely not the settings that I have made, and I have tried reloading and erasing the EEPROM for several times now, and the same behavior persists after some flights.
Does anyone seem to have this problem?
In the event that the logs are corrupted, is there a way for me to extract some of the data out of it? Some of the data are important to me. Thanks!
It has been my experience that APM's datalogging just doesn't work very well. Telemetry logs from the mission planner are great and are timestamped, though.
Datalogging has been totally reworked in ArduCopter 2.1 and ArduPlane 2.7 (not yet released in the Mission Planner, but available in the Git repository). It should work properly for everyone now.
That's good to know.
Speaking of 2.7, is there going to be a code split where the purple board will get more functionality because of the new IMU coprocessor but the old board will stagnate?
Yes, but we'll continue to support the old board for at least a year.
How soon do you think the new board is going to get desirable functionality that the old board won't support? Is it already in the works or is it only planned?
MPU-6000 DMP support (offloading sensor fusion to the MPU-6000's processor) will be added by the end of Jan on APM 2, which will free up about 40% of its Atmega2560 processing power.
So I should probably look at buying it in a couple months?
Will be neat coming up with alternative projects for my current APM =P Suppose it could be a combination antenna tracker and weather station.