Who should be a beta tester?

We love our beta testers. They help us find bugs, fix them and test all those variations of hardware and configuration that no single dev team could test themselves. Much of the sucess of APM, ArduCopter and all the other DIY Drones projects is due to a large and incredibly supportive group of beta testers.

But beta testing is not for everyone. The code is, by definition, unfinished and probably buggy. It changes by the day, and sometimes by the hour. The documentation may be lagging. And when things go wrong, you can lose your aircraft.

Here's who should consider being a beta tester:

--Experienced users

--People with well-tested hardware/airframes, so we can differentiate between hardware and software errors.

--People familiar with Arduino, so they can deal with code if need be.

--People with loads of patience who want to contribute to making something awesome.

Here's who should NOT consider being a beta tester:

--New users

--People with airframes and electronics that have not already been tested and flown on non-beta code

--People who don't want to geek out a bit with code

--People who just want to fly NOW

--People who don't want to risk their expensive equipment on experimental software.

We love both groups, but my advice to all of our users is to think carefully about which group you're most comfortable in.

APM 2 is out of beta, so this is not an issue there. But ArduCopter 2 was just launched in beta two weeks ago, and although it's improving at light speed, I'm concerned that new users are using the beta code without being prepared for what beta testing means and requires. It helps nobody when new users who have never set up their hardware before swamp the beta testing feedback process with basic setup issues. It's understandably frustrating for them and it's frustrating for the dev team, too.

So, if you don't fit the criteria for the first category above, please use the tried and true ArduPirates software for ArduCopter. It's very solid. Please only use the AC2 beta if you DO fit the first category above.

As always, you can get the latest status updates on the ArduCopter news page. When AC2 comes out of beta and is appropriate for everyone, we'll let you know there and here on DIY Drones.

Thanks!

Think carefully about how you format your code when you write.
Find your style and be consistent.
It makes for easier to read code and also helps in spotting errors.

Here is your code re-formated to my style as an example:
I also fixed some bugs while at it. ( hint: = is not the same as == )

void waypoint_check()
{
// Take pictures at WP-2 thru WP-12
if( g.waypoint_index > 1 && g.waypoint_index <= 12 )
{
// Get as close as it can for you
if( wp_distance < 10 )
{
// DO SOMETHIMNG
arducam_pic();
}
}

// Start video recorder at WP-2
if( g.waypoint_index > 1 && g.waypoint_index == 2)
{
// Get as close as it can for you
if( wp_distance < 10 )
{
// DO SOMETHIMNG
arducam_vid();
}
}

// Take pictures at WP-13
if( g.waypoint_index == 13 )
{
arducam_pic();
}
}

You need to be a member of diydrones to add comments!

Join diydrones

Comments

Russell B. Sutton May 21, 2011 at 11:17pm

I started with the PiratesNG code first. My quadcopter flew great with out any PID tuning, very nice. Although This code is tested and true. I'm getting spoiled with the new AC2 code and the mission planner.
Developer

Jason Short May 21, 2011 at 10:13pm

The RC2 or Pirates code is the preferred non beta code AFAIK.
diego colonnello May 21, 2011 at 5:44pm

Hello people, maybe i am mistaken, but, if a code is in beta, and it is not ready for everybody to use it, i think it can´t be in the wiki page, or at least as the primary option for the one hwo gets there hoping to fly fast....

What i mean is this, i have built my arducopter and the first thing i saw on the wiki was the AC2 information to finish my new device and start my testing...

Now Chris takes the time to clarify that not everyone is able to try beta codes......... today i saw one part of the wiki that says "legacy" Arducopter 1 code.......

So, i am going to start by the AC1 first, just to see how it behaves and what i should espect....

Tranks people, thanks to the developers and the testers..... i am very happy with my arducopter.....
Developer

Mark Colwell May 20, 2011 at 5:20pm

Thanks for the = vs == , I missed that, I use others code and just can't see the breaks sometimes. I also add my own notes for ending ifs and loops etc.

Developer

John Arne Birkeland May 20, 2011 at 1:55pm

Developer

Mark Colwell May 20, 2011 at 11:27am

Found the last compile error !, I messed up parens again, All good now.

Now to upload and test Camera_Tilt to home with Remzibi_OSD.

Then add new function for using uploaded waypoint as point of interest for camera.
Developer

Mark Colwell May 20, 2011 at 11:15am

Thanks Jason, I tried that, and found other errors.

arducam_pic(); // DO SOMETHIMNG }

arducam_vid(); // DO SOMETHIMNG }

The trailing parens are commented out !

fix = add new line before }

arducam_pic(); // DO SOMETHIMNG

}

Now I can chase down next issue in void recalc_climb_rate()

Thanks, I just needed a little push...
Developer

Jason Short May 20, 2011 at 10:28am

if((g.waypoint_index > 1) && (g.waypoint_index <= 12)) {

// Take pictures at WP-2 thru WP-12

Missing parens.
Developer

Mark Colwell May 20, 2011 at 8:02am

I really hate beta testing, I is a big time killer, but without it I would have a pile of trashed UAVs, I do enjoy adding the latest new options, HIL, OSD, and Camera Tracking. But debugging is difficult. Code is tight and not easy to decipher sometimes. Current compile issue with "void waypoint_check" calling "climb_rate"

What does this error message mean??

ArduPilotMega_2_1_mjc.cpp: In function 'void waypoint_check()':

climb_rate:9: error: expected identifier before '(' token

climb_rate:9: error: expected `;' before '(' token

test:671: error: expected `}' at end of input

Any Hints?

waypoint_check code:

void waypoint_check() {

if(g.waypoint_index > 1) && (g.waypoint_index <= 12) { // Take pictures at WP-2 thru WP-12

if(wp_distance < 10) { // Get as close as it can for you

arducam_pic(); // DO SOMETHIMNG }

}

if(g.waypoint_index > 1) && (g.waypoint_index = 2){ // Start video recorder at WP-2

if(wp_distance < 10){ // Get as close as it can for you

arducam_vid(); // DO SOMETHIMNG }

} if(g.waypoint_index = 13){ // Take pictures at WP-13

arducam_pic();

}

}
Developer

Doug Weibel May 20, 2011 at 7:30am

Although APM 2.X is out of beta if you are testing some of the latest features you are still a beta tester ;) APM has grown in complexity to the point that there are MANY combinations of configurations and features that have not been tested. The core functionality and popular configurations have been pretty well tested, but if you have something unusual, you may be the first and are a beta tester. Always proceed with a bit of caution.

of 2

This reply was deleted.