We're not scared of BUGS, here's how to find them.

Joined
May 5, 2015
Messages
856
Reaction score
666
Unlike a certain brand of white multicopters, Arducopter is open about its bugs, so you can search them, comment on them, watch them until they are closed. You can use this information to keep yourself informed and flying safely.

If you have a problem you can check the bug list and see if it's already known, also if you plan a hardware upgrade you can check for known issues, for example I was going to install 2 GPS pucks onto my Pixhawk, but I found a bug that said 2 GPS units were causing glitches, so I knew not to install it until the bug was fixed, e.g:

https://github.com/diydrones/ardupilot/issues/1875

So I'll explain to you how to use GitHub for checking for bugs and enhancements:

Go to this URL (this is Solo specific): https://github.com/3drobotics/ardupilot-solo/issues
Also check the main Arducopter code: https://github.com/3drobotics/ardupilot/issues

At the top right you will see a search window with:
Code:
is:issue is:open


After that type (leaving a space after open) your description, so if for example you wanted to search for GPS bugs your search line would look like:
Code:
is:issue is:open GPS


You can also search for bugs that have been fixed, using the same syntax (just with is:closed)
Code:
s:issue is:closed


If you want to search purely for bugs (so excluding enhancements) the syntax is:
Code:
is:open label:bug


If you want to keep an eye on safety features, which if you're a commercial operator especially you may want to be aware of, use the syntax:
Code:
is:open label:"Safety Feature"

I hope you've found that helpful.
 
Last edited:
Unlike a certain brand of white multicopters, Arducopter is open about its bugs, so you can search them, comment on them, watch them until they are closed. You can use this information to keep yourself informed and flying safely.

If you have a problem you can check the bug list and see if it's already known, also if you plan a hardware upgrade you can check for known issues, for example I was going to install 2 GPS pucks onto my Pixhawk, but I found a bug that said 2 GPS units were causing glitches, so I knew not to install it until the bug was fixed, e.g:

https://github.com/diydrones/ardupilot/issues/1875

So I'll explain to you how to use GitHub for checking for bugs and enhancements:

Go to this URL (this is Solo specific): https://github.com/3drobotics/ardupilot-solo/issues
Also check the main Arducopter code: https://github.com/3drobotics/ardupilot/issues

At the top right you will see a search window with:
Code:
is:issue is:open


After that type (leaving a space after open) your description, so if for example you wanted to search for GPS bugs your search line would look like:
Code:
is:issue is:open GPS


You can also search for bugs that have been fixed, using the same syntax (just with is:closed)
Code:
s:issue is:closed


If you want to search purely for bugs (so excluding enhancements) the syntax is:
Code:
is:open label:bug


If you want to keep an eye on safety features, which if you're a commercial operator especially you may want to be aware of, use the syntax:
Code:
is:open label:"Safety Feature"

I hope you've found that helpful.
That is the ultimate beauty of this machine ........open source. No secrets here.
 

New Posts

Members online

Forum statistics

Threads
13,120
Messages
147,970
Members
16,107
Latest member
vze2rsky