Multiwii and Megapirate AIO Flight Controller w/FTDI (ATmega 2560) V2.0
This board features a multiple serial interface as well as a dedicated I2C interface. You can now plug in a GPS directly, and you still have extra ports for other external devices. In addition to that, the new ATmega 2560 has more IO pins so it can both read the PWM signal from your receiver and it has enough PWM outputs to control the ESCs directly without the need to do the PWM signal in software.
This controller even has a MicroUSB port right on the board, no need to attach an extra FTDI USB interface.
The motion sensing side features a new generation MEMS Gyro, a MPU6050 by InvenSense, which has the MEMS Gyro / Accelerometer sensor on a single chip. There’s also a 3-axis magnetometer and a barometer sensor with a resolution of 0.01 millibar – approximately a 10 cm height difference.
Interested in GPS functionality? Well this is one of the most cost effective ways to get started - simply add a 10Hz GPS module (coming soon) and you’re good to go!
Features: • Supported MegaPirateNG and MultiWii firmware • Up to 8-axis motor output • 8 input channels for standard receiver • 4 serial ports for debug/Bluetooth Module/OSD/GPS/telemetry • 2 servos output for PITCH and ROLL gimbal system • 1 servo output to trigger a camera button • 6 Analog output for extend device • A I2C port for extend sensor or device • Separate 3.3V and 5V LDO voltage regulator • ATMega 2560 Microcontroller • MPU6050 6 axis gyro/accel with Motion Processing Unit • HMC5883L 3-axis digital magnetometer • MS5611-01BA01 highprecision altimeter • FT232RQ USB-UART chip and Micro USB receptacle • On board logic level converter
Flight mode for Multiwii: • One of the following basic modes – Acro – Level – Alt Hold - Heading Lock
• Optional mode – HeadFree (CareFree) – GPS Hold (Need GPS receiver) – GPS Back to home position (Need GPS receiver)
Flight mode for MegaPirate: • Acro • Alt Hold • Loiter (uses GPS) • Guided (uses GPS) • Position (uses GPS) • Circle (uses GPS) • RTL (uses GPS) • Auto(uses GPS) • Follow Me(uses GPS)
Newby here, For this board - Which board should I choose when configuring MegapirateNG?
I've got it working with Multiwii but have issues with motors not running anywhere near to similar speeds (3/4 throttle to start 1 motor) despite cal of all sensors and ESC's etc, So I thought I'd try MP...
This is clone of CRIUS ALL IN ONE PRO V1... as for throttle... first calibrate ESCs
(with MWI you can do onboard esc calibration procedure, just don't forget to take off propellers )
Second you need to set in config.h MIN_THROTTLE value. so that after arming your motors starts spin an minimal throttle...
Anyone having issues with the FTDI port? I am getting all sorts of noise on mine. I have tried different baud rates, firmware and FTDI -> USB and FTDI -> bluetooth adapters... All show the same noise. I have even powered the board externally to eliminate noise from the BEC.
The noise looks like semi random characters (depending on the terminal I use)
The noise is also present on the built in FTDI -> USB port... however it is much less...
My goal is to use bluetooth with this board.
First disconnect EVERYTHING (all what is connected to board) except USB cable and check.
If in this case connection is OK then... problem in powering...
Second check with ESCs connected.... disconnect all ESC 5v pins except one (pull out from connector and isolate) leave only one ESC bec powering your FC... try again...
I suggest you run at 9600 Baud, and see if your random characters go away. The way you Power the FC, has nothing to do with the gibberish you are experiencing. One important thing, make sure your molex connector/cable have sound crimped ends. These are tiny plugs, and may have not been terminated properly.
Hello everyone! Thank you for your suggestions. I disconnected everything as suggested by v_max and only powered it from USB. Then I reset the board s0 to 9600 baud as suggested by tricopterY.
I also manually connected the wires to s0 to eliminate any bad molex connectors.
Same issue... I also tested the blootooth by itself looping it back to my computer... no issues, so that rules out a bad bluetooth
i attached some video that shows the issues
Hi all (hopefully tricopterY) I,m trying to setup a servo gimbal. Where do i plug them in ? There are two ports on the board that are meant for camstab but im APM planner it lists channels but none work with the camstab channels. Can the aux pins output PWM signal? and then could i power the servos from the reciever?
Also im having some trouble with alt. hold and pos. hold (the only modes i have tried except stabilize) In pos hold i was hovering at about 1.5m and it was glitching and going up and down small amounts. I have covered the barometer with breathable foam. I tried pos hold on the ground as i was scared it would fly my quad into a tree and it didnt want to take of straight up. with full stick movement it was still trying to move away, i had 7 sats. Any reading you can suggest?
never try poshold on ground... first of all GPS has stohastic errors depending on satellites moves overs sky and changes of gps signal reflections from surrounding buildings... this error typically has fast several meters changes... Well... what will happens if you switched onground poshold.. current position stored as base... in next few seconds error may change several meters and coper will decide it drift several meters... what should it do? yes, will try to go to base position...
The Single Row Header Pins are Inputs to the FC. The Three Pin Header Pins are outputs from the FC (PWM Pulses of 50Hz, 1500 micro seconds wide, is deemed neutral position for a servo, FC can drive ESCs up to 490Hz i.e finer repetition leading to better resolution). Where it says Roll and Pitch on the 3-pin headers you would connect your servos (to be driven by the FC's Attitude Sensors i.e IMU), and on single header pins i.e Cam Pitch and Cam Roll you would connect your Rx channel(s), normally slider switches or rotory knobs on Tx, so you could use your Tx to command the servos to attain a new holding position. If your ESC can supply 3Amps constant you shouldn't worry about exceeding the power ratings, for driving two servos. GPS Position Hold, is most effective when the craft is hovering at 50% throttle. This is implementation dependent, and you should theoretically be able to lift-off in Position Hold and fly around. As explained above the Stochastic nature of GPS data should Allow and not impede an accurate interpretation by the FC navigation control loop, for determining current position i.e a moving target commanded/controlled by Tx stick positions. Barometer on this FC tends to send the craft up and down in a column and cannot be considered very accurate (I have managed to get it hovering very stable when flying inside). You should enable Baro in combination with GPS Position Hold. Happy flying.
so i can plug one esc back in as it is only powering 2 servos, great! I'm going to try mounting my gps away from other electronics to see if that helps.. So i should just get it in a stable hover and flick the switch? thats scary ill have to do it somewhere that is not my tiny driveway surrounded by trees. how good is the area the gps will hold in? When i had it plugged into my computer the gps was moving sometimes 10meters off where it actually was... although im below another level.
Thanks you should be paid by hk!
The jumper must be off, and only connect one ESC's 5V and GND to run your Roll and Pitch servos on the 3-pin headers. You can test your servos operation by tilting your craft and they should compensate for that movement.
Hi I have two questions. I am running MP 3.0.1 on the board and I tried to do a motor test through the apm planner 2.0 CLI but got not motor movement. Anyone had similar problems? Second I bought this power module: http://www.hobbyking.com/hobbyking/store/uh_viewItem .asp?idProduct=43766&pb=1 I plugged it directly into the A0-A5 serial port and this seemed to provide power and sensing etc but I was wondering if this connection is correct. Thanks
A0-A5 are Analog Inputs to the FC. They are configured to read in values from analog sensors, or monitoring battery voltage etc. But, this is not the way to power this FC. I am even surprised to hear that it boots (only explanation - Open Drain/Collector setup that causes the FC to experience 5V, but in a weird way). Power the board either from one of your ESCs (connected to a motor port) or get yourself an external SBEC and connect it to External Power In header pins (must remove jumper J1 in this case). You must also Calibrate your Accelerometers and Compass/Magnetometers using MissionPlanner. Then do your motor test.
bought my third controller and i hope that i do not have to solder the vreg on this one a big plus for this board are the sensors they all work flawles i fly with 2 of the faulty????? boards that i have soldered the vreg and for sure i can say it is worth the money
yes its not a crius but works the same for half the money
AND PLEASE HK DO NOT I REPEAT DO NOT ERASE THE REVIEW AGAIN
because that PISSIS the buyers off
No comments. Reply..
Ahh, I can finally write a review on this product. I'm an original owner of the first version of this board, the one with a faulty GND trace. Upon receiving the board, I highly recommend you go over it with a fine comb. Aside from the known fault on the original board, I also had a lifted pin on the 2560 (A11) which resulted in intermittent yaw control. We're talking really really small pins here, unless you have expert-advanced soldering skills, and even if you do, it's probably best to just request a RMA and send it back. Now that's out of the way, on to the review. If you're new to the multirotor scene, this board is not for you. There's a lot going on with this board and to use it safely, you'll need to have a sound understanding of working/tweaking with firmware, how all the elements work and connect together, and the ability to troubleshoot/fly a buggy multirotor. If you've worked with Multiwii in the past and are looking to move on to something a little more advanced without busting your wallet, then this might be the board for you.
It's ability to handle different flavors of firmware is what drew me to this board. As per the description, it can handle Multiwii, MegaPirateNG, and although it's not mentioned, I have been running ArducopterNG on it as well. It's worth noting that the MegaPirateNG and ArducopterNG are both ports of the Arducopter2 firmware. Bec
No comments. Reply..
Opened up my FC today and wasnt really happy. I got someones returned board. HK didnt even take the time to remove all the the previous persons double sided tape from the back of the board. After reading all these reviews I am wondering if it is worth my time to figure out which version I have and dive in. Man those KK2 boards are making this thing look like a nightmare! All these features better be worth the time investment.
1 comment. Reply..
Top, no problems with it. I use it with Multiwii Software. Altitude hold, Level mode, mag, bluetooth, gps hold and return to home, all works fine with high precision. Nice Board... Altitude sensor must be covered with foam... Gps is a Locosys from a Tiny OSD 2 with serial interface, 10Hz and 112500 data transfer rate... You can use one gps modul for Flightcontroller and Osd (it needs only TX from Gps Modul)