Skip to content

5.Performance Analysis

Kevin Guest edited this page Feb 12, 2016 · 17 revisions

The APM or Pixhawk Flight Controllers (FC) running APM:Copter have the ability to log an update status of how much stress the FC is under at each point of a flight. It is important to consider that Performance Analysis refers to the Flight Controllers ability to process the internal threads / code and not the overall performance of the model and other hardware.

Where information is available the APM Log File Analyser will attempt to review this information and summarise it along with pointing out any issues found.

Towards the top of the text based analysis we detail the type of Flight Controller, the installed firmware and as part of the Performance Analysis the internal clock frequency. Older firmwares would clock at 100Hz, newer firmwares at 400Hz.

Clock Frequency

The datalogs do not contain any errors related to flight controller performance issues, however we can determine the status of the Flight Controller by analysing data provided. The APM Log Analyser does this and will detail any issues during the text based analysis where the Flight Controller becomes under pressure to perform all that is being asked of it.

Warning Long Loops

In the above example we are getting very close to the maximum number of Long Loops allowed as specified by the APM:Copter developers as 15%, should it reach 15% the Warning will become an Error message.

To the left of the main text based analysis panel there is the option to see additional information about the performance of the flight controller. This can be handy at times but by default this is unchecked. Activating this option will provide Information about the % of long loops between 3% and 10%, where the default is only anything over 10%.

Performance Monitoring Addition Info

Information Long Loops

Clone this wiki locally