My 210 quad has a Naze Rev 6 board and it is upside down in the frame. I just changed over to Beta Flight from Clean Flight. I had things working fine in Clean flight. Now, I can't seem to get Beta flight to recognize that the board is up side down so when I try to fly it flips over and literally goes crazy. What am I missing.   Thank God for this forum.

  Willie B

There's a section for that in the Configuration tab. You have to set how many degrees the FC is shifted from its default, in your case probably 180 on roll or pitch (or both). You can set a value, save and then verify in the setup tab if it moves as you expect when you tilt it around with your hand - that should save you time and probably some props since you don't have to actually try to fly it to check if it's right. Remember to calibrate the accelerometer once you get it right.

tozes, Thank You that quick and accurate diagnosis of the problem.

Gotta love this forum, and of course the people who make it work!

This didn't work out. It still jumps up and go CRAZY. 

In the   "board and sensor alignment" in Beta Flight , I set roll and pitch to 180 to compensate for the upside down flight control board in my frame. Do I need to set the ACCEL Alignment to CW 180 or maybe CW 180 flip. I had the Go Pro on it last time and don't want this to happen again...........................help

Is there a reason why you haven't just mounted it normally? I know sometimes it makes the USB port more accessible if the board is rotated 90 or 180 degrees, but I've never heard of anyone mounting one upside down.

Which way does the arrow on the fc point right now?

To eliminate the possibility, you could also double check your motor connections to make sure each motor is connected to the right pins in th FC (motor 1 to motor output pin #1 and so on)

(28-Jan-2017, 05:37 AM)CaCondor Wrote: This didn't work out. It still jumps up and go CRAZY. 

In the   "board and sensor alignment" in Beta Flight , I set roll and pitch to 180 to compensate for the upside down flight control board in my frame. Do I need to set the ACCEL Alignment to CW 180 or maybe CW 180 flip. I had the Go Pro on it last time and don't want this to happen again...........................help

If you set both roll AND pitch to 180 (at the same time), then you are back where you started.  Set one or the other to 180, not both. (Try it with a coin

(28-Jan-2017, 10:19 AM)sloscotty Wrote: If you set both roll AND pitch to 180 (at the same time), then you are back where you started.  Set one or the other to 180, not both. (Try it with a coin

You actually backwards. Try it with your hand

Just to make sure, in this pic posted above:



You have to use either

• the left column which accounts for all sensors (gyro/acc/etc) at once, and offers more precision but takes more CPU power, or
  
• the right column which only allows certain presets (90°-steps), is less math-intensive, and has to be set for each sensor individually (set gyro & accel the same usually). Warning, there's some boards/firmware versions where "default" alignment does NOT mean 0°.
  

With accel enabled, you should be able to see in the configurator wether the movement of your quad matches the screen. Don't power it up/don't arm before you get this right.

(28-Jan-2017, 01:45 PM)oyvinla Wrote: You actually backwards. Try it with your hand

Yeah, you are correct, but I was talking about just the upside down part.  If you change pitch 180, then indeed you have to change yaw 180

(Now I'm sure we've confused the OP totally - or I may have even confused myself....) 

Forget all that - do what fftunes says 

(28-Jan-2017, 08:57 AM)oyvinla Wrote: Which way does the arrow on the fc point right now?

The arrow is pointing forward.

OK, I got it working right. The problem WAS that I didn't need to change pitch AND roll 180 degrees. I only needed to change roll to 180 degrees, under "board and sensor alignment"  I appreciate everyone who made a suggestion as it DID lead me to discover the solution.

Haha, sorry for the confusion with the suggestion to change both axis and thanks Scotty for pointing it out. And most importantly, I'm glad it's working now!