-
Notifications
You must be signed in to change notification settings - Fork 0
Post‐Session Operations
This is the main approach we used to analyse the performance of the rover after a mission.
Ensure there are at least 500MB left on SD card to prevent wiping off old logfiles. The limit can be changed in the parameter LOG_FILE_MB_FREE.
The fastest method is to transfer the logs from SD card to host machine directly. The logs are stored in the SD card in the folder APM/LOGS. However, if the SD card is not accessible, the logs can be downloaded from the flight controller using ground control software e.g. MavProxy/MissionPlanner etc., albeit at a much slower rate. Another alternative is to use the telemetry logs (tlogs) from the ground control software as long as the option to save tlogs is enabled and the ground control software is connected to the flight controller during the mission.
Options:
- UAV Log Viewer: Good for visualisation and trim tlog files. Can even trace the messages & Params from the log file.
- MATLAB: You can use this GUI app but it is only available for tlog files. Alternatively, you can use Mission Planner to export the binary log file to a .mat file and then use MATLAB to analyse the log file. (Navigate to DataFlash Logs tab in Mission Planner and click on the "Create MATLAB File" button, see here)
The MATLAB script in Appendix (download) can be used to calculate some of the performance metrics used in the report.