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 have this and original crius 1.1.. both works perfect. IMHO this is the best choice for MWI... As for Megapirate.. I afraid MPNG is now drifting to other hardware and may soon discontinue support for this board type. Also MPNG has significant porting delays from base APM project. That's why I decided to give a try for HKPM MINI in my next build...
this board has MWI firmware by default... So MissionPlanner wouldn't work....
And see the thread below... looks like last batch of this boards was without bootloader.. It connects with MWI GUI, but Arduino fails to connect.. You need to flash bootloader yourself with USBASP programmer connected to ISP port if you want to reflash firmware
Sorry I forgot to mention that i did manage to upload Arducoper firmware (MPNG-3.0.1 r4) via a PC. But I want to use my MAC to configure the board. But went I go back to the MAC board doesn't show up in the serial port list.
Who uploaded the "Solution.JPG" file? Because it would help to know where all the wires go and most of them run out of frame. It looks like the GPS connects with red, yellow green and black, to the right end of the header nearest the 'A' of the A B C on one edge of the board, but according to the schematics, that's ground, 5, TX Telemetry (or OSD) and RX Telemetry. Then four twisted wires, purple white orange and blue go who knows where. I have to assume the telemetry transceiver goes to FTDI, but where do the other two wires end up? I'm trying to figure out from all this whether this board will support the new Turnigy NEO-7 GPS. The info above says "simply add a 10Hz GPS module (coming soon) and you’*re good to go!". Ok, the new NEO-7 is 10hz, so am I "ready to go"? The confusion for me is that the GPS appears to have a six pin connection. I assume I'll have to abandon the compass on it, but how do you plug six pins into four?
GPS must be connected to serial2 port GPSTX to RX2 and GPSRX to TX2 cross tx/rx connection. (gnd and 5v power assuming) That's all... never trust wire colors! Check pin labels on board and pinout for s1-s3 connector in manual (under files tab)... To make GPS work you need to define serial 2 port baudrate in config matching your GPS.. and set protocol matching your gps protocol... I'm not sure what settings NEO7 have by default, but GPS settings can be changed with uCenter configuration utility... to do this you need to connect GPS to PC using FTDI adapter... Or you can simply find required settings in contoller changing baud and protocol... Start with NMEA and 38400 (this was defaults for NEO6)
and neo7 with compass has 2 connectors... 4 wires on main connector is gnd,5v,tx and rx for GPS.. 2 additional wires on smaller connector is I2C SDA and SDL data wires only for compass.. just leave it unconnected.
Sorry, it's the uBlox NEO-7 I'm looking at. The description includes: "Connection: Compass 4 pin/ GPS 6 pin (Pixhawk/PX4 compatible)" When I look more closely at the (really awful) picture, I can see the NEO-7 GPS has four pins in a five-pin header, just like the others. It was the description that threw me off, and the total absence of documentation that left me that way.
So I've got this board, and I'm getting ready to build my configuration.
But before I upload a new build of firmware, I'd like to know how to recreate the installed firmware, just in case. Yes, I know I can download the currently installed firmware with avrdude - in fact I've already done that. But what I'd really like to be able to do is see what the configuration options are and be able to rebuild it (perhaps with updated firmware sources) and re-upload it.
So - Where might I find the configuration/setup for the default MultiWii firmware that is installed?
First you need to download firmware and eeprom state if you want to revert it back sometimes.
You can do this with avrdude... Second downloaded firmware is compiled binary code, so
you have no chance to convert it back to source code... As for configuration... part which is defined in config with #define directive is also part of compiled code and can't be altered. All you have under control is settings stored in eeprom... Assuming by default board is preloaded with MWI you can connect MWI gui, read current eeprom config (press read button) and save this state into file. (save button at top left corner)...
Yes - I know the firmware when downloaded is binary. Also that I can't get the configuration from the compiled firmware. I'm a software developer, so I kind of understand all of that pretty well.
That's what I asked specifically about the configuration used when the firmware that is installed on the board by default. Yes, the default board is loaded with MWI.
I guess I'll have to ask HK directly - it doesn't appear that anyone here will likely have the answer.
If I get an answer, somehow, I'll post it - perhaps even upload the config.h file to the files area...
First thing I do with all my controllers is reflashing with own configured and compiled firmware...
What's the matter what was there before... (oh yeah sometimes I do dumps of original firmware, but never used it, just a garbage on my hdd)
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
1 comment. 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)