-deleted-

So does anyone know where the inputs and outputs are on this thing if you want to use Arduplane? It's unmarked, the "D" pins are usually there for motors on multirotors. But what about servos?

Can someone explain me these 3 param.?
-----------------
1. Land speed (LAND_SPEED)
The descent speed for the final stage of landing in cm/s
Is this the final stage of the RTL, just before RTL_ALT_FINAL?
-----------------
2. Auto pilot's max vertical speed in cm/s (AUTO_VELZ_MAX)
The maximum vertical velocity the autopilot may request in cm/s
Does this apply just for WP in AUTO MODE?
-----------------
3. Pilot maximum vertical speed (PILOT_VELZ_MAX)
The maximum vertical velocity the pilot may request in cm/s
Does this restrict the vertical speed in LEVEL, ALT_HOLD or both modes..?

hmm this is odd...

I just updated my crius to MPNG 2.9 R5 (286) and everything works great controls all do what they're supposed to do, throttle goes up and down in mission planner when I move the throttle..

but...

the throttle % shows 0 all the time and so on my MinimOSD where I got throttle % with MPNG 2.7 I now get zero...

EDIT: nevermind... it now only shows when the quad is armed, before it used to show all the time if you moved the stick..

does anyone has power-up diagrame for aiop2?

thanks

Originally Posted by abriosi

the new calibration method worked really well for me. I dont need any trim now to achieve almost perfect level. Even with a huge CG offset(aka camera gimbal)

I can't get the new method to work only the old one.

I'm running 2.9 R5 and the new level procedure reports failure every time. I have tried both Mission Planner 1.2.35 and 1.2.30. Tried clearing eprom and reloading etc...

If I use the CLI to run level it does work but its not doing the new method.

Just to make sure I was thinking we would have to do this in 2.9 builds..

ArduCopter 2.9 Accel Calibration (2 min 34 sec)

I also read on DIYDRones there is an issue with the level not looking right in MP and they advised not to use the CLI level command because it would cause an offset issue with the new leveling stuff. Can those running 2.9 let me know what they did to get it flying?

Originally Posted by charlienofun

....Can those running 2.9 let me know what they did to get it flying?

Works for me. Running 2.9_R5. The only issue I have is that I can't get the new level routine to work over telemetry radio.
I have to do it with USB. Never bothered to figure out why...
Oh, and the "press any key", means a keybord key...(Don't ask...)

Once that was done, I used the "Save Trim" function to iron out the last litte drift I had.
Flies really nice in stab now.

Alt.hold is another issue, but we all know that.....

/J

Originally Posted by JNJO

Works for me. Running 2.9_R5. The only issue I have is that I can't get the new level routine to work over telemetry radio.
I have to do it with USB. Never bothered to figure out why...
Oh, and the "press any key", means a keybord key...(Don't ask...)

Once that was done, I used the "Save Trim" function to iron out the last litte drift I had.
Flies really nice in stab now.

Alt.hold is another issue, but we all know that.....

/J

Yea I'm doing it directly via the USB cable. I will try once more before I roll back to 2.8 tonight.. the 2.9 videos I see people posting on youtube look great I wanna get it working

Thanks

Hi guys,

Finally got around to wiring up my FPV and MinimOSD (RCTimer clone) yesterday.

Flashed OSD with MinimOSD Extra. Wired in the digital side, very tidy if I do say so myself Connected the analog side minus the camera and could see the OSD feed. Changed the settings in Mission Planner as per the wiki and everything seemed to be working as it should.

Then spent a while trying to create a wiring harness from camera > MinimOSD > TX.

When I hooked everything up now what I get is a black screen with the video feed flashing up every 2 seconds and no OSD

A quick Google later and I found a number of threads (mainly on DIYDrones) saying by using one battery the board is fried and I should have used a separate flight pack.

Is this the case? Does this also apply to the RCTimer clone? I have not seen any mention of it on the MinimOSD site, the RCTimer site or here that it was a no-no to use the same battery....

Originally Posted by wetpanda

Hi guys,

Finally got around to wiring up my FPV and MinimOSD (RCTimer clone) yesterday.

Flashed OSD with MinimOSD Extra. Wired in the digital side, very tidy if I do say so myself Connected the analog side minus the camera and could see the OSD feed. Changed the settings in Mission Planner as per the wiki and everything seemed to be working as it should.

Then spent a while trying to create a wiring harness from camera > MinimOSD > TX.

When I hooked everything up now what I get is a black screen with the video feed flashing up every 2 seconds and no OSD

A quick Google later and I found a number of threads (mainly on DIYDrones) saying by using one battery the board is fried and I should have used a separate flight pack.

Is this the case? Does this also apply to the RCTimer clone? I have not seen any mention of it on the MinimOSD site, the RCTimer site or here that it was a no-no to use the same battery....

If I recall correctly the RC timer clone is the older version of the MinimOSD I'm not sure if that matters though

Originally Posted by Titus Gordon

If I recall correctly the RC timer clone is the older version of the MinimOSD I'm not sure if that matters though

The latest rctimer clone of the minimosd does not have the regulator/heat issue as the earlier versions. It does require 5v from the crius board on the digital side and 12v from the analog side. I believe this is mentioned on their website

Got mine working, I had to completely rewire the quad due to a ground loop (I think) causing only a black screen. I still need to tweak the layout and position.

FPV 16.02.2013 | MinimOSD tests (4 min 17 sec)

Originally Posted by WiseDuck

So does anyone know where the inputs and outputs are on this thing if you want to use Arduplane? It's unmarked, the "D" pins are usually there for motors on multirotors. But what about servos?

Hi. You can have a look at Jean-Louis Naudin's blog on DIY drone, there are several pictures explaining the way to connect servos & sensors to use arduplane on this board:

http://www.diydrones.com/profiles/bl...ource=activity


[Edit] You also have a picture here:
http://www.rcgroups.com/forums/showp...8&postcount=82

When I do an automatic esc calibration with Arducopter 2.9 R5 everything works as described on the arducopter wiki. All four esc's calibrate and when I give it throttle the motors are synced. When I arm the FC for the first time, after the auto calibration, 3 of the 4 motors go into calibration mode as soon as the FC is armed. This then screws up the initial auto calibration. I'm using simon k flashed esc's.
Why are the esc's going into calibration mode after arming the FC and only on the first arming of the FC after an auto calibration procedure? Seems like if this weren't the case the auto calibration would work fine.

GPS issue CN-06 with Crius AIO Pro V1.0 - any one can help? Thank you in advance.

I have used MegaPirate 2.8r3 AIO Pro v1.0 on hexa frame with CN-06 GPS. The FC work well on ALT HOLD with barometer (rock steady - no wind).

The GPS able to lock (GREEN signal on FC and flashes on the GPS module); when I activate ALT HOLD with GPS - the copter drop from the sky and I have to go back to STABILIZE mode to recover/safe the copter.

I check the GPS and test with u_blox GPS utility, appear to work fine. I used the 3DR-ublox.txt scripts - and set the GPS BAUD to 38,400. This also appear to work fine.

Has anyone have this issues? Is the GPS BAUD correct requirement @ 38,400 for the MegaPirateNG 2.8R3?

Further check with Mission Planner, the GPS found to be working - verify and pickup location fine.