PIDtoolbox

KO | EN

gitlite — search

#javascript #golang #go #rust #deep-learning #linux #macos #java #windows #kubernetes #vue #awesome-list #pytorch #openai

(★ 12)

Matlab-based blackbox analysis tools

PIDtoolbox 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# PIDtoolbox

PIDtoolbox is a Matlab-based GUI for analyzing Betaflight blackbox log files for multirotors.

![](https://raw.githubusercontent.com/ianrmurphy/PIDtoolbox/master/images/PIDtoolboxGUIexample.png)

The motivation for the development of this tool was to create a user-friendly GUI for analyzing blackbox data, using a high-level language with simple plotting and visualization tools that are more accessible to a larger part of the FPV community. A second goal was to develop an objective method for comparing between flights. It was inspired by the way we often troubleshoot flight performance issues (e.g., vibrations, mid-throttle oscillation, propwash), where we make back to back test flights with slight changes in software/hardware/mechanical settings with each test, and then make subjective inferences about flight performance. The problem is subjective bias becomes a real issue when the differences between tests are subtle. PIDtoolbox was designed with this in mind.

PIDtoolbox is also devoted more to spectral analysis than tuning per se, since filtering out vibration seems to be the number one concern. A major part of flight control software development has been devoted to filtering noise from the gyro, particularly in the ~200-500Hz range associated with motor vibration. From my analyses of blackbox data, I've noticed a consistent pattern between copters that fly well and copters that do not, specifically in the 30-90Hz range. Commanded motion is generally below ~20Hz (even if you're a 'Mr. Steele' on the sticks!), but elevated activity in the 30-90Hz range tends to correlate with the kind of vibrations we SEE during flight and in HD video (e.g., mid-throttle oscillation, propwash, jello). Although these frequencies can't be filtered out, a goal of PIDtoolbox is to use this as an objective measure of flight performance, to help the user decide whether a manipulation of software/hardware/mechanical settings was effective. I'll show some examples that support this idea. As always, the goal of a well-performing copter still requires reducing +100Hz noise, so PIDtoolbox supports the ability to plot the throttle x freq spectrograms that we've come to love about <a href="https://github.com/Plasmatree/PID-Analyzer" target="blank">Plasmatree PID-analyzer</a>, and extends this functionality to many other flight variables.

Below is everything you need to begin using PIDtoolbox. I hope you find it useful, and I welcome feedback from the FPV community.

-Brian

# Download

There are a couple of ways you can download PIDtoolbox.

**1)** If you have Matlab, you can simply download the repository of mfiles, place them in a folder, and run `PIDtoolbox.m` from the Matlab command prompt. You will need several toolboxes installed for this to work (control toolbox, signal processing toolbox, image processing toolbox and statistics toolbox). I am also working on converting the code to run in <a href="https://www.gnu.org/software/octave/" target="blank">Octave</a>, a free high-level programming platform that was designed to be largely compatible with Matlab (thanks <a href="https://www.facebook.com/UAVTech1/" target="blank">Mark Spatz</a> for bringing this to my attention!). It would be great if this were to become part of a wider FPV community development, and using a high-level free language like Octave should make it more accessible.

**2)** If you do not have Matlab (or Octave), you can download a standalone Windows version of PIDtoolbox. You must first install Matlab runtime (MATLAB® Compiler Runtime, MCR), which then allows you to run any standalone Matlab program.

- **(i)** Install Matlab runtime <a href="https://www.mathworks.com/products/compiler/matlab-runtime.html" target="blank">(Matlab-runtime)</a> for Windows **(64bit only, version 9.3 R2017b**; it will not work on 32bit machines). The good news is this is a one-time installation, after which you can run any Matlab standalone!

- **(ii)** Download PIDtoolbox for Windows here <a href="https://github.com/bw1129/PIDtoolbox/releases" target="blank">(releases)</a>. Unzip and place entire folder in a preferred location on your computer. `PIDtoolbox.exe` can be found in `PIDtoolbox\for_redistribution_files_only\PIDtoolbox.exe`. IMPORTANT, `PIDtoolbox.exe` MUST remain in the original folder, so I'd recommend creating a shortcut and placing it on your desktop. For Mac/Linux users, if you have a bonafide copy of Matlab and can create your own standalone version of PIDtoolbox, it'd be greatly appreciated if you could share it here!

PIDtoolbox has been confirmed to run on Windows7/8/10 64bit machines, but it has not yet been extensively tested, so your feedback will be helpful. If you have issues installing Matlab runtime, or running PIDtoolbox, please give feedback here
<a href="https://github.com/bw1129/PIDtoolbox/issues" target="blank">(issues)</a>,
or drop a post to the Betaflight BlackBox Log Review Facebook group <a href="https://www.facebook.com/groups/291745494678694/?ref=bookmarks" target="blank">(Betaflight BlackBox Log Review Facebook group)</a>.

# How to use

A few points before some real-world examples:

- **(i)** PIDtoolbox will only read `.csv` files exported from <a href="https://www.github.com/betaflight/blackbox-log-viewer/releases" target="blank">Betaflight Blackbox-log-viewer</a>. Open your `.bbl` or `.bfl` log file in Blackbox-log-viewer and export as `.csv`. Do not use `blackbox_decode.exe` (it excludes important header info used by PIDtoolbox).

- **(ii)** I would recommend always logging at 2k (unless you're running 1k loop rate in which case log at 1k), because the spectrograms only go to 1k. From my experience, I have had some really large log files crash when trying to convert to `.csv` in Betaflight Blackbox-log-viewer. In addition, PIDtoolbox will run much faster with 2k files. For 32k mode users, I don't know what to say ;-)

- **(iii)** Always set debug mode to `gyro_scaled` for PIDtoolbox. This is because the program expects the debug variables to contain the unfiltered gyro data, which is needed to plot the filtered vs unfiltered gyro spectrograms, and compute gyro phase latency online. In time I will write a script that reads which debug mode is selected, and plot the appropriate data.

If you have issues installing Matlab runtime, or running PIDtoolbox, please give feedback here
<a href="https://github.com/bw1129/PIDtoolbox/issues" target="blank">(issues)</a>,
or drop a post to the Betaflight BlackBox Log Review Facebook group <a href="https://www.facebook.com/groups/291745494678694/?ref=bookmarks" target="blank">(Betaflight BlackBox Log Review Facebook group)</a>.

Now, let's get on with a few examples:

### E.G. (i) Mid-throttle oscillation
'Glen' posted a log file (A) to the Betaflight BlackBox Log Review Facebook group: <a href="https://www.facebook.com/groups/291745494678694/?ref=bookmarks" target="blank">(Betaflight BlackBox Log Review Facebook group)</a>
describing a vibration issue with his copter. He then made some changes to the PIDs and filters and reposted a second log file (B). I imported each log file (`.csv`) using the `select` buttons, then clicked `load+run`. Below is a screenshot of the main results, with line plots of flight data on the left (gyro filtered and unfiltered lines selected), and spectrograms on the right. Test A and B are coded orange vs blue, respectively, and the orange/blue shaded regions indicate the window of the data used for subsequent analysis (these windows can be adjusted from the control panel on the right). If you click within the white region of any of the line plots, it expands to facilitate viewing and control with the zoom tools. Now based on the full spectrograms (heatmaps below), the post filtered Gyros (right panels) look relatively clean in both test flights A (upper) and B (lower). 
![](https://raw.githubusercontent.com/ianrmurphy/PIDtoolbox/master/images/PIDtoolboxGUIexample2b.png)

Using the drop down menus and `<100Hz` check boxes in the control panel, I then selected the specrograms to compute sub-100Hz throttle x freq plots for set point and PID error, then clicked the `refresh` button to recompute the new spectrograms (see plot below). I know, you're thinking "why are you plotting set point?" Since set point is RC input in deg/s, the freq spectrum of set point is a good measure of the range of frequencies associated with commanded motion. Theoretically, anything above this is uncommanded motion (i.e., stuff we don't like, such as mid-throttle oscillations, propwash, etc.). PID error is the difference between set point (commanded motion, or what we ask the copter to do) versus the gyro (actual motion, or what the copter actually did). The horizontal red and yellow dashed lines on the spectrograms demarcate this region (which, incedentally corresponds with the cutoff used in UAVtech's <a href="https://drive.google.com/drive/folders/1jCIJ2FKL7t-ZADcErNrZOcWfWtkgSVdr" target="blank">filter calc tool</a>. Now, when we look at the spectrogram of PID error (right panels), we see a clear band of activity around 40-50Hz in the mid-to-upper throttle range, mainly on roll and pitch for test A, and less so for test B (despite the fact that the full spectrum looked clean for both!). To corroborate this, we can see clear oscillations in the Gyro and PID error traces blown up on the left, with peaks ~22ms apart (which is 45Hz!). Remember, this was not obvious when viewing the full spectrum.
![](https://raw.githubusercontent.com/ianrmurphy/PIDtoolbox/master/images/PIDtoolboxGUIexample2c.png)

To go a little further, we can plot the mean absolute value of PID error as a function of throttle (see below). For these plots, we window the analysis to flight data where the set point remained relatively low (100deg/s; see `max stick deg/s` window in the control panel), to minimize the potential confound of large error induced by fast flips/rolls (fortunately, snap flips/rolls usually occur at min throttle, so it's actually not a major issue here). In agreement with the earlier spectrogram data, you can see a systematic increase in mean |PID error| starting around mid-throttle, particularly for roll in test A (orange bars). From these results, it's clear that the adjustments made in test B were an improvement over test A. So we're on the right track! 
![](https://raw.githubusercontent.com/ianrmurphy/PIDtoolbox/master/images/PIDtoolboxGUIexample2d.png)

### E.G. (ii) Propwash
This past summer I was asked by Mark Spatz <a href="https://www.youtube.com/channel/UCI2MZOaHJFMAmW5ni7vuAQg" target="blank">(UAVtech)</a> to compare propwash handling between 1k and 8k pid loop rates, on the same copter with identical settings with the exception that the 1k setup did not have the dynamic notch active. Thus, the 1k setup had a minor disadvantage in terms of potentially more motor-related noise (though a potentially steeper lpf cut @ lower loop rate <a href="https://www.facebook.com/UAVTech1/photos/pcb.2185446125049843/2185447555049700/?type=3&theater" target="blank">(for example)</a>; see fig at the beginning of this document for pre- vs post- filtered gyro of this data), but this was offset by an advantage of having lower total phase latency (3.01ms vs 3.71ms for A vs B, respectively, abbreviated as PsD-A and PsD-B in the lower portion of the control panel; side note, phase latency is computed directly in PIDtoolbox via cross correlation between filtered and unfiltered gyro and dterm). Some time ago I posted an HD video <a href="https://www.youtube.com/watch?v=Tbx--JI01NE" target="blank">(Propwash Video Test)</a> of both flights on the Rotor Riot Facebook page, and then polled observers to decide which one showed less propwash in a blind test. Turns out more people chose test (1) (but not all). See if you can guess which one that corresponds to in the following results of both flights:
![](https://raw.githubusercontent.com/ianrmurphy/PIDtoolbox/master/images/PIDtoolboxGUIexample1b.png)

In this case we are plotting the spectrograms only (Test A left and Test B right) for sub-100Hz PID error and motor sigs 1 and 2. Test A shows less activity in the 20-90Hz window in both PID error and the motor 1-2 signals (the same was true for motors 3-4, not plotted here). For test B, there is a bigger 'blob' of activity above the red dashed 'commanded motion' line, indicative of more vibration/propwash. Incidentally, it turns out that flight (1) in the video corresponds to Test data A here. It's also worth noting that these spectrograms are normalized such that the amplitude spectrum is unaffected by the length of the file/flight, which makes it more of an apples-to-apples comparison. This shows the novelty and value of being able to plot spectrograms across different kinds of blackbox data (the noise was especially noticeable on the motor outputs). PIDtoolbox gives you the option to easily plot spectrograms for several other variables, change the heatmap scale, and select from a list of color maps.

I hope you find PIDtoolbox useful, and I welcome feedback from the FPV community.

Cheers! -Brian

PIDtoolbox

PIDtoolbox 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

PIDtoolbox

PIDtoolbox 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README