Atmega 328P on Super X 125mm

[ACME Milli-Rotor]

Hi I'm new to the MultiWii quad control and have some questions I hoping someone will be kind enough to answer. My first flying MW project is a Super X 125mm quad from Bangoods. I updated my Arduino to the latest version. Choosing the board is a bit different than when I flashed it last year with an older version. Under Arduino Pro or Pro mini I find the 328 Processor (but no p) it is asking if this is a 3.3V 8hz or a 5V 16Hz.
http://www.hobbyking.com/hobbyking/store/__58128__Super_X_Brushless_125mm_Micro_Quad_Copter_With_MWC_Flight_Controller_BNF_KIT_.html Although I see that Bangood no longer has a page on their site for the Super X Here is a link to the Hobby King version. I want to stop the motors from spinning on the arm but I'm not sure which 328p processor This FC is using. I would think it would be the 5V but in the add it says it has a 5V converter. How can I identify this board for sure?

My next question is I can not enter calibration modes with the sticks I checked in the GUI and my sticks go full through past 1900. I have drift I want to correct for, although I calibrated the gyros on a known level surface in the GUI. Any suggestions on haw to use the sticks for calibration on this FC?
Thanks again for any help.

[PatrikE]

Conclution from the specs..

• Integrated DC/DC voltage booster/Step down for 5v 1~2 cell operation

Processor runs on 5V and regulator accepts 3.3 to 7.4 volts.
You should probably select 5V in the IDE.
It will fail flashing if it's wrong.

[brm]

no - 24 bits are missing!

[ACME Milli-Rotor]

Thanks PatrikE for the explanation. I guess this isn't a 32 board, posted this in the wrong place sorry bout the noober mistake. My Fc is flashed with the new sketch and it flys great. I also found out why I couldn't enter calibration mode with the sticks I had to change my Tx setting from 22ms to 11ms. I was checking to make sure I was on DSM2 when I noticed the ms choice so I changed it jsu to see what happens and WALA (as they say in India) my stick calibration works.
Thanks for the help I really appreciate it

[brm]

Thanks PatrikE for the explanation. I guess this isn't a 32 board, posted this in the wrong place sorry bout the noober mistake. My Fc is flashed with the new sketch and it flys great. I also found out why I couldn't enter calibration mode with the sticks I had to change my Tx setting from 22ms to 11ms. I was checking to make sure I was on DSM2 when I noticed the ms choice so I changed it jsu to see what happens and WALA (as they say in India) my stick calibration works.
Thanks for the help I really appreciate it

to speed up the transition from 8 to 32 bits we leave the 8 bitters in the dark.
alas i am going to test an 8 bit fc :-/

[PatrikE]

Weeeelcome to the dark side brm...

[brm]

Weeeelcome to the dark side brm...

oh oh - to defend myself.
when counting possible hw breakpoints an atmel sucks.
debugging arm cortex devices is much nicer.

writing a new altitude hold controler with no delay ...

[Crashpilot1000]

Weeeelcome to the dark side brm...

oh oh - to defend myself.
when counting possible hw breakpoints an atmel sucks.
debugging arm cortex devices is much nicer.

writing a new altitude hold controler with no delay ...

Hi BRM! Great to hear that!!
BTW, I have seen this in Armazila https://github.com/ARMAZILA/FlightCode/ ... ltFilter.c but have not tested it. Maybe that is helpful.
Cheers Rob.

[brm]

hi rob,
ok, i have armazila boards ... the base package is close to not flyable.
way to much jitter on the time axis.
i haven't tried the baro filter - might work or not ...
at the moment i am rewriting the whole stuff.
what doesn't work right is now the usb connection.

cheers rob

[ACME Milli-Rotor]

thanks! a long time late