MegaPirateNG development officially dead?

[DerFlash]

Based on the updates here on the project (none) I assume the project is officially dead? I've seen the new FABI board but let's be honest, there are already a bunch of boards out there which are directly compatible to the official APM firmware, so I can't see any reason for another clone.

The one (and important!) reason for this project is and was the support of the "old" non-32Bit boards like the Crius and the others. And without any update here, this is now useless. The main code has made some huge steps and they did fix a lot of bugs, but MPNG is way behind...

So PLEASE just finally be honest to your community, users and yourself and answer this simple question: Will there be any progress in the code regarding the non-32bit boards? And if so, please don't just say "yes" and provide an estimation then. Otherwise it would be great to know what to expect!

Thx

[SirAlex]

Aehm, this is exactly what we got when we checked out on git and compiled on 4.8.2, right ? Or did you improve / update / fix the sources from 2 weeks ago ?

R2 has some modifications, you may read commit history at Git: https://github.com/MegaPirateNG/ardupilot-mpng/commit/6a636eb46b4dfc927259658e7803f734fcec83c1

Most important, now it compliles on Build server (so available via FlashToo). Fixed baro issue for HK Multiwii Red board (also BlackVortex). CLI enabled by default and logging enabled for Crius V2

[SirAlex]

I'm just checked FlashTool and seems it works fine. Please, before upload, delete all files in firmware subdirectory of FlashTool.

[Espenf]

Hi Nils, I compiled included 3.0.1 R3 on R4 I used flash tool. Is it just to download FlashTool and 3.1.5 R2 code for varius configs is included?

[nilsheidorn]

Hi Espenf, if you have one of the boards directly supported you just need the flashtool and can flash directly. Voila, Kudos to SirAlex !

I cannot do so as i am using a funduino + 10DOF and need to patch several things. Give it a try...

Nils

[Espenf]

I downloaded and extracted FlashTool-2067cdba637ce092a639672ed5261faa1fa59149 and FlashTool-master. They look very similar, but it looks like I need some Java to make this run. There is no flashtool.exe. I have the old flashtool I used for 3.0.1 R4, is this to be used?

[SirAlex]

How to use FlashTool: http://docs.megapirateng.com/documentation/flashtool

[smurfy]

I have the old flashtool I used for 3.0.1 R4, is this to be used?

to answer your question: yes its the same tool for 3.1.5 R2. The list of available version is refreshed upon start of the flashtool.

I downloaded and extracted FlashTool-2067cdba637ce092a639672ed5261faa1fa59149 and FlashTool-master. They look very similar, but it looks like I need some Java to make this run. There is no flashtool.exe.

this is the source code of the flashtool. (Qt C++ code and java script code) Normally you just need the exe, linked at the page siralex linkend, and you already have.

[Espenf]

Tnx all, I found it, I will try to flash the new version soon. :) My setup, 450dji,HK_red, Gaui Kv1050, cheap one daim 20Amp speed ctr, neo 6M, 3dr, FrSky 8XR, Taranis. I flashed today using this setup, worked fine. Testing just brief flying in stabilize, no problem. :) Guess I will test the autotune after a while.. Is this supposed to work like described here ? http://copter.ardupilot.com/wiki/autotune/

[CrashDBN]

Well I tried the dev version of 3.1 and the first flights was great. Did the autotune, loiter and althold everything fine. Put 3 or 4 batteries through it no problem. Then went back to my older trusty 2.9R3 for awhile. A few nights ago I decided to try the dev version again and well it went badly. Took off went into a nice stable hower in acro mode. Next thing the copter pitched forward and slammed into a wall. Ignored all inputs from the TX and continued to try fly on the ground, smashing all my props.

So now I've loaded the latest version via the flash tool and going to test that version.

The only thing I can thing of that was different between the weekends flight and the one during the week that almost trashed my quad was that on the weekend I had more than 6 SAT links while on the week flight I only had 4. I didn't think it would matter since I was flying in acro but I guess it did.

Will let everyone know how the R2 version flies later today once I come back from testing.

One last thing. Hobbyking V2 AIOP board, NTM 800kv motors and 10x4.7 props.

[marlb64]

Hi, i had a bluetooth connection to droidplanner2/andropilot working on serial3 with v3.0.1 firmware,i compiled v3.1.5 r2 without trouble and uploaded it. When i try to connect droidplanner2/andropilot it looks like the mavlink is up but no data is transfered. Any thoughts ? serial3 baudrate is set the same as in v3.0.1

hk aio board.

[Espenf]

Hi marlb64, I can confirm that serial 3 is working with the 3dr radio connected (using hk_red board and v3.1.5 r2 ). I believe you may change baudrate via MP if needed, parameter "serial3_baud". On the hk_blue board I used the 3dr on serial 0 and this worked after using flash tool and v3.0.1 R4. I hope this will work in v3.1.5 r2, but have not flashed this board yet.

[CrashDBN]

Marlb64 don't you normally connect a bluetooth module to com 2 not 3 as 3 is normally used for the 3DR radio like Espenf mentioned. I've got mine connected to com2 and there is no issue with bluetooth connection using the new software.

On that note I must say v3.1.5R2 flies great. Uploaded the software via the flash tool on Saturday even. Did the calibrations for compass, accel and radio and the compassmot for mag interference. Took it out for a fly yesterday. Hopped straight up into a nice stable hover, no need to do the auto trim or anything. Tested drift, loiter, althold and RTL. All worked great, copter seems to fly a lot smoother with the new firmware on it. Also tested arming and taking off in loiter and it also works great, but does take some getting used to.

Quad setup: SK450 frame, NTM 2830 800kv motors, 10x4.5 Props, 4S 3300 Lipo, HK AIOP board, neo6 GPS

[marlb64]

I'll try the other serialport and report back.Strange thing is when i go back to ver 3.0.1 r4 the connection to droidplanner2 and andropilot works like a charm.

[SirAlex]

While testing 3.1.5, I'm used 3DR telemetry connected to Serial 3 and connected to my phone with AndroPilot on other side - all works fine.

P.S. Until now, I'm have only one issue with 3.1.5 - I'm flying too long and my battery fully drained so bird fell down ))) (-1 one prop, and seems like -1 motor)

[erevert]

I have a bluetooth module connected to serial 0 and it does not work. With 3.0.1 r4 it works but with 3.1.5R2 something is wrong. With andropilot the HUD works but neither waypoint nor parameter is downloaded from my crius v2.I have change it to serial 3 and the same.

[marlb64]

Hi, i figured it out: in missionplanner i had to set SERIAL_1_BAUD (first telemetryport baudrate) to 115200 used by the crius bluetooth module connected to SERIAL_3 !! (hardware side). SERIAL3_BAUD was set to 115200 in APM_Config.h.

Grtz and tnx to all

[Raider1284]

When using the flashtool, with PWM selected for the RC input, what's the difference between the 'channel order' options? Default, vs JR, vs multiwi, etc.

What determines which one you should choose? Does that channel order option apply to both PPM and PWM? thanks.

[CrashDBN]

Not sure what the differences are but I know I've alwayd used thr multiwii option and I'm using a Futaba radio. Also the multiwii option works for the cheap HobbyKing 6ch radio as well. I think it has something to do with how the channels are mapped on your radio I.e. in what order they are.

[smurfy]

As the name already says. "channel order". It defines which channel is which input on your board. So you can use any of the options, but if you change the order you probably need to reconnect your wires to your RC Receiver.

I'm not sure about PPM thought. But i guess it will affect that as-well.

[Raider1284]

Just flew 3.1.5 r2 for the first time and it worked beautifully! I'm hoping to get more info on the RC input channel order though.

With respect to the RC channel input order, On the crius aio board at least, I believe that "default" is: Yaw on A8 Elevator on A9 Throttle on A10 Roll on A11

Is this correct? What happens if I then switch to "Multiwii" instead?

[smurfy]

From the source:

#if RC_MAPPING == RC_MAP_STANDARD
    static uint8_t pinRcChannel[8] = {0, 1, 2, 3, 4, 5, 6, 7}; // ROLL,PITCH,THROTTLE,YAW,MODE,AUX2,CAMPITCH,CAMROLL
#elif RC_MAPPING == RC_MAP_GRAUPNER
    static uint8_t pinRcChannel[8] = {1, 3, 2, 0, 4, 5, 6, 7}; // PITCH,YAW,THROTTLE,ROLL,AUX1,AUX2,CAMPITCH,CAMROLL
#elif RC_MAPPING == RC_MAP_HITEC
    static uint8_t pinRcChannel[8] = {1, 0, 2, 3, 4, 5, 6, 7}; // PITCH,ROLL,THROTTLE,YAW,AUX1,AUX2,CAMPITCH,CAMROLL
#elif RC_MAPPING == RC_MAP_MULTIWII
    static uint8_t pinRcChannel[8] = {1, 2, 0, 3, 4, 5, 6, 7}; // ROLL,THROTTLE,PITCH,YAW,AUX1,AUX2,CAMPITCH,CAMROLL
#elif RC_MAPPING == RC_MAP_JR
    static uint8_t pinRcChannel[8] = {1, 2, 0, 3, 5, 6, 4, 7}; // FLAPS:MODE, GEAR:SAVE TRIMM = apm ch7