Closed GoogleCodeExporter closed 8 years ago
I get this too, APM2 will not arm motors until reset button is pushed. Blue LED
flashes then goes solid but red LED is off and stays off until reset is pushed.
Original comment by graham.d...@gmail.com
on 6 Mar 2012 at 3:05
Presumably you're using the latest version of the code from the mission planner?
Any chance you could provide a dataflash log? These can be downloaded through
the apmission planner's terminal screen. Maybe one log of you being unable to
arm the motors and one of it after you've pushed the reset button and are able
to arm the motors.
It must be a timing issue. The question is whether it's a radio problem (i.e.
the APM can't see the message in from the rx (unlikely) or it's the outgoing
message to the ESC.
Original comment by rmackay...@gmail.com
on 14 Mar 2012 at 2:38
I have the same issue that reported before. I´ve noticed also that just after
switch-on and having the issue, I connect to MP thru USB cable the issue is
solved alone (red led start to work and then I can arm).
I´ll try to get a log for you to study.
Original comment by afd...@gmail.com
on 14 Mar 2012 at 3:07
This has been reproduced by a good number of people including a few on the dev
team. We know it affects arducopter more than arduplane. It's somewhat
related to the bootloader and the order of the start-up time of the sensors.
It's being actively looked into so I suspect we will have a solution shortly.
Whether that means a new ArduCopter/ArduPlane release or a 328 firmware upgrade
remains to be seen!
Original comment by rmackay...@gmail.com
on 16 Apr 2012 at 12:34
Issue 411 has been merged into this issue.
Original comment by rmackay...@gmail.com
on 28 Apr 2012 at 11:46
This has been fixed in trunk and in 2.5.5-beta that is in the downloads area.
IT should go out in the next patch release which should be very soon! Maybe
today.
Original comment by rmackay...@gmail.com
on 13 May 2012 at 5:53
I have simulare problem. APM2 factory assembled bard. closest description is
from the Troubleshooting guide:
The APM board works when it's plugged into the USB, but not when it's powered
by the RC rail (ESC/Lipo).
If I connect OSD-mavlink, the board red lights start flashing when powerd by
lipo. If I start board without OSD-mavlink, the red light never start flashing.
When I use Usb, it newer fails..
Original comment by haugsv...@gmail.com
on 1 Aug 2012 at 5:47
I've got the same problem and everything was updated today. When I boot from my
lipo the blue led flashes then the yellow barely comes on and then they are
both dead. I can get it to arm if I hook the lipo up and the usb then
disconnect the usb. I just hope I don't have problems in the air.
Original comment by taylor.l...@gmail.com
on 22 Sep 2012 at 2:09
@taylor,haugsvaer,
Although on the surface it sounds a bit similar to your issue, my guess is that this is a different issue. Not 100% sure but your issues sound more like a power problems, possibly caused by mistakes in the wiring?
You need to provide 5v of power from a BEC or ESC into the input rail of the APM2 to provide power to the main CPU and miniOSD (if you've got one). Plugging the ESCs into the output rail will not provide power to the main CPU..perhaps this sounds strange but the reason it's done this way is that for some configurations (planes and helicopters) they don't use ESCs but rather servos and we need to separate the power provided to the servos from the power provided to the CPU to avoid interferece.
@Taylor, is it possible you're plugging power from the ESC into the side of the
APM instead of into the input pins? the power input lines on the side of the
APM go through a voltage regulator..that regulator eats 1 volt or so you may be
getting a brown out. I'm not totally sure, but that's my guess.
I'm going to close this issue but please feel free to raise a discussion on the
main forums. you can also PM me to point me at your discussion in case i miss
it.
Hope this helps.
Original comment by rmackay...@gmail.com
on 23 Sep 2012 at 4:04
Original comment by rmackay...@gmail.com
on 23 Sep 2012 at 4:05
Original issue reported on code.google.com by
wayneabo...@gmail.com
on 2 Mar 2012 at 9:42