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)
I purchased this board and and the hk bluetooth adapter for this board (not the one in the related section above.) I have it wired to the FTDI port on the board. I have the correct wireing because it connects to my phone and at first I did have the TX and TD wires wrong. I switched the wires but it won't give me any info from the board to my phone. The baud rate should be set at 115200 already as its the default on the hk spec section of the bl board. What else could I check to get it to give me the board info? Is there a config.h setting I missed?
MWI ? First check baud for serial0 in config.h by default it is 115200.
Second ... you need to pair BT module with your PC bluetooth. After pairing check the number of discovered COM port via BT... Use this com port number in GUI. If this do not work ...
Last thing is verifying and setting right baud for BT module
You need FTDI adapter to connect BT via ftdi adapter to PC and use telnet program like putty to send AT commands to BT module.
Yes multiwii firmware. My pc does not have bluetooth. The bluetooth board should already have the correct baud on it per hobby kings specs on the board. I am useing the same board your useing as you posted awhile back. I will check the configuration file and I'm sure that must be where my issue lies. Should I buy the bluetooth programmer to have or would I really not need it if the baud rate is already at 115200?
What GUI you are using on your phone? Is it Android phone or iPhone or what?
Paired and connected do not mean correct wiring.. It only mean BT module is powered.
data wires may be not connected at all.
When you connect from GUI you actually connect to BT module, but futher data connection between BT module and FC may even not present phisically.
You need to connect TX0-BTRX and RX0 to BTTX (note cross rx-tx) and if baud match and connection with BT established then it must work.
I use MultiWii-EZ-Gui (on Android phone) via HK BT module with this this controller to tune my quad. Work OK
Android. The app is multiwii ez. I am connected to the controller. I had the txo and the rxo wired wrong at first and would get a wrong/bad connection. I then switched the two so txo goes to rxo and vice versa. I then connect but it's not getting any data from the fc to send to my phone. I'm thinking the baud rate is wrong because it has to be wired right.
FTDI adapter is very common tool to be used as adpter of usb to serial.
I use it not only with BT module but for GPS configuring and for reflashng my frsky RXes.
In fact you MAY not need it this particular case, but without it you can't be sure you have correct
baud set. As I remember the first thing I did with my BT was setting required baud because
default was less then 115200.
As alternative after checking physical connection you may try different settings of seral0 baud
( 115200, 57600,38400,19200,9600 ) in config.h to find what actual setting your BT module have.
And also note that reflashing will fail when BT is connected to serial0/ftdi so you need to disconect it each time.
In fact if it is set below 38400 you would need to reprogramm BT anyway...And you will need FTDI adapter for it.
Or you may write(or find) arduino sketch to use arduino (or even this FC ) as FTDI adapter, but I never try this way myself....
Agghh,,, something wrong with sensors.
It may be config or physical malfunctioning
If you did any changes in sensors section of config.h then revert it. All you need is choose board type C R I U S _ A I O _ V 1
(v1 !!!! important not v2 )
I have a microSD card breakout board from adafruit that i want to connect up to this flight controller. i know the MISO, MOSI & SCK pins are on the SPI headers, but when i connect these wires to the SD card board and run the simple cardinfo sketch it says that it was unable to initialize the card. i know that the card works because i wired everything up on an uno first and it has power. Is there a specific numbering of the SPI pins that i have to initialize? i know they're digital 50-52 on a regular mega, but if i initialize them in the sketch it still doesnt work. Any help would be greatly appreciated because i have been trying to figure this out for close to a week.
Hello all, I'm having a little trouble figuring out how to connect this FC to a FRSKY D8R-II Plus for use with PPM. I'm using the MPNG flash tool which is pretty straight forward, but I just want to make sure I'm wiring it correctly. Any help would be appreciated.
FRSKY D8R-II Plus do not support CPPM out.. So just channel by channel connection. On FC you have a single row of pins labeled on backside. Use 5v and gnd from this row to feed receiver through any channel power pins.. then connect rx signal outs to throttle,roll,pitch and yaw with a single wire
There is no official version of CPPM firmware for d8r-ii plus at least under related files section... I found on rc groups that people reflash d8rii-plus with d8rxp cppm 27Hz firmware succesfully (d8rxp_cppm 27_build120926) ... But that's on your own risk.
Google for "Simple FrSKY Receiver Flash How To with COM Port" and you will find the thread on r c g r o u p s
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)
It seems that version 2.0 doesn't have the problem of the 1.0 batch. I am using it with MegarPirateNG, NEO-6M and a bluetooth module. No problems whatsoever. If seems that HK deleted all documents in the "File" section, so search youtube for rcjoseb and you will find some great videos how to configure it. Cheers!