search

Guitarmath / arducopter

Automatically exported from code.google.com/p/arducopter
0 stars 0 forks source link

APM2... Copter.. 2.5. on a tri-copter.. #393

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Arducoper NG or ACM?
What steps will reproduce the problem?
1. Hard pull back on the stick then level..
2.
3.

What is the expected output? What do you see instead?

Nose up 40 deg.. then level..
but it 
Nose up 40 deg... then up 90 deg... then crash..

What version of the product are you using? On what operating system?

APM2... AuduCopter 2.5.. 

Please provide any additional information below.

Original issue reported on code.google.com by eddiewe...@aerialimageryla.com on 18 Mar 2012 at 7:55

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks Eddie, i report now on the dev list... i'm sorry for this bad event!
Stay tuned...

Bests, Marco

Original comment by robustin...@gmail.com on 18 Mar 2012 at 8:11

GoogleCodeExporter commented 8 years ago 
Eddie, what is motor2motor distance ? 
And what tail servo do you have ?

Original comment by levine...@gmail.com on 18 Mar 2012 at 9:07

GoogleCodeExporter commented 8 years ago 

Each stick is 1 meter long... so motor to motor is like 1.7 meters.. ?

Tail servo is 333 oz Digital.. Kind of like this one..
http://servocity.com/html/hsr-5990tg_servo.html 

5 amp BEC powers the servo directly with no power comming from the AMP2

Original comment by weeksg...@gmail.com on 19 Mar 2012 at 12:25

Attachments:

GoogleCodeExporter commented 8 years ago 
Any updates on this? I'm anxiously waiting for this issue on tri's to be fixed 
so that i can finally fly my try that has been grounded for months now, all in 
hopes for a better future ;(

Original comment by igorio...@gmail.com on 21 Mar 2012 at 2:14

GoogleCodeExporter commented 8 years ago 

I repaired my tri above and am flying it alot, no wireing was damaged so I am 
sure the back motor did not loose power... I am not pulling back all the way 
any more.. Just flying around in Stab..  This has only happend to me twice and 
I fly hard and a lot... 

Eddie Weeks
www.jetlens.com

Original comment by eddiewe...@aerialimageryla.com on 21 Mar 2012 at 1:45

GoogleCodeExporter commented 8 years ago 
Thanks Eddie, it just seems that there are very few people flying the code 
w/tri's and hence no support or interest.... I've had similar issues a few 
times as well on my tri (same, just 50% smaller ;-)... actually, come to think 
about it, the only time I brought it back w/o a crash was when i put the KK 
board on it (because i was frustrated with arducopter)... and i think i have > 
100 flights on it... funny that $15 hardware performs better than the hardware 
that costs ~15 times as much ;-( upsetting really...

Original comment by igorio...@gmail.com on 22 Mar 2012 at 1:15

GoogleCodeExporter commented 8 years ago 
I had a look at the logs and I couldn't see anything that indicated a code 
failure.  My only guess is that one of the motor's reached the maximum power 
that it could deliver and the copter lost the ability to stay upright.  Or 
maybe it was just a hardware failure.

If you could turn on the motors logging that would be good.  I.e. connect via 
mission planner's terminal screen, then "logs" then "motors"...but then you'd 
have to re-enact the incident and I don't really want you to put your tri in 
danger..

Original comment by rmackay...@gmail.com on 22 Mar 2012 at 12:45

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 

New flights seem to indicate the rear prop going into deep stall...
I say this because, I have been getting closer to reproducing the event but 
this time right next to me.. The back props is making all kids of noise and is 
moving downward at great air speed rel to itself, and low rpms at first  .. 
12x3.8 APC slow fly.. I have reproduced this problem to a far lesser degree and 
for less than one sec.. In all cases the tri was moving forward fast, then full 
up was applied.
Makes since this would happen to large Tri and not Quads and Hex.

Eddie Weeks

Original comment by eddiewe...@aerialimageryla.com on 30 Mar 2012 at 4:33

GoogleCodeExporter commented 8 years ago 
Eddie,
     If you can recreate it fairly easily, is it possible to turn on the motors logging?  It can be done by connecting to the mission planner's terminal screen, then typing "logs" then "enable motors".

Original comment by rmackay...@gmail.com on 30 Mar 2012 at 1:27

GoogleCodeExporter commented 8 years ago 
Eddie,
     If you're able to recreate, the problem, I think we should try removing the stability patch and see if that makes it better:
   http://code.google.com/p/ardupilot-mega/source/browse/ArduCopter/motors_tri.pde?name=ArduCopter-2.5.3#48

     The way it works at the moment is that if any motor hits it's upper limit, the reduces the other two motors evenly.  But if two motors hit their upper limit then poor motor #3 could be reduced too much (this is my guess).

     Logging the output from the motors will be very useful.

Original comment by rmackay...@gmail.com on 10 Apr 2012 at 2:48

GoogleCodeExporter commented 8 years ago 
Please resubmit on the new issues list (see below) if it's still a problem

Original comment by Benny.Si...@gmail.com on 20 Jan 2013 at 7:59

GoogleCodeExporter commented 8 years ago 
Issue closed. 
If you find this is an error please report it in the new issues list
https://github.com/diydrones/ardupilot/issues?labels=ArduCopter&page=1&state=ope
n

Original comment by Benny.Si...@gmail.com on 20 Jan 2013 at 8:00