Did I blow my outputs?
Hello,
I got to the point in my first quad arducopter build where it came time to load the code, exciting!
With everything connected, (including ESCs) I proceeded to power up the board via USB.
The dim LED struck me as kind of odd, but at this point I don't know that what i've just done is a no. So I make 1 attempt to load the code whith no success obviously. That's when I unplugged it.
Upon closer inspection the manual I found it rather casually mentioned here:
"3. Upload the ArduCopter firmware to the APM.
- Plug the board into the USB. If you have ESCs connected to the board, you must also be powering the board via a battery (though the power distribution board if you're using the standard ArduCopter frame). If you do have the ESCs connected to the APM board and you don't power the independently of the USB cable, the code will not load and you may blow your outputs. (You can tell you're overloading your board if your APM LEDs are dim). "
I connected the battery, made a minor correction to my sketch folder name/location and the code loaded fine.
now when I power on the quad the motors beep really fast and nudge just a little....
I calibrated the esc's according to the manual and tested each motor idividually for proper spin direction
Thanks,
Toby
Post script,
in kinderkram's build log, at the bottom (after you fry your outputs)
there is this warning
IMPORTANT WARNING!!!
When you plug in the USB make sure you don't have your ESCs and motors connected.
Otherwise you will blow your outputs!
you guys know the next question.
Why is this warning not in the ArduCopter manual?
Replies to This Discussion
-
ModeratorPermalink Reply by Chris Anderson on -
Very sorry to hear that! The warning is in the manual as you note, but I agree that it could be more prominent. The manual is in constant revision, so we can ensure that this is introduced sooner and with more emphasis.
-
Permalink Reply by Joel on -
With this happening, i'm curious what repairs will be needed to the board?
-
ModeratorPermalink Reply by Chris Anderson on -
Your IMU shield is fine, but the MUX chip on the APM board is probably fried. Given that's the cheaper of the two boards, the easiest option is to replace it. If it's any consolation, I've done this myself a few times, even though I know better. It's not an issue with airplanes, and I keep forgetting to take extra precautions with quads.
-
Permalink Reply by Toby Stein on -
Chris,
At $80 after shipping it ain't that easy. Believe me. This is not happening whith the Mikro Kopter, it doesn't happen with my UAVX it doesn't happen with my X3D-BL and it certainly shouldn't be happening to the APM/oilpan copter. This is particularly frustrating because it usually happens rite as you are about to configure your copter. Correct? Unless and until the flaw is corrected, it will happen to you and me again invariably.
there is not much dialogue on DIYdrones regarding this issue although it's happened to so many.
Let me be the first to say, this problem needs to be addressed. And on this website I might add.
We should not have to go ahead and put together our APM/oilpan arducopter and then have to disconnect all power lines coming from ESCs, add a 3-5 USD +5V/5Amp switching regulator just to fly.
most people are not that technically inclined. including me.
I wouldn't be able to add much to it, but I think there should be a thread called
"avoiding ESCs draining too much power from the USB if the flight battery is not connected"
Best,
Toby
-
ModeratorPermalink Reply by Sebastian Gralla on -
just cut all + voltage lines from the esc and connect the apm with the battery (where it says 6V+)
there you go
-
ModeratorPermalink Reply by Chris Anderson on -
PM me your address and I'll send you a new board. I've put huge warnings in the manual, so perhaps this will help others avoid this.
-
Permalink Reply by Toby Stein on
-
Chris,
Outstanding customer support! Very nicely done!
Thank you,
Toby
-
ModeratorPermalink Reply by SciFly on -
Too bad to hear that but a simple precaution based on common sense could have prevented that problem.I would argue that one never knows the state of the board and thus input/output port assignments etc., prior to loading a program. Always double checking code and diagrams and hardware followed by loading the software prior to hookup helps to prevent foul ups. So does reading through the manual/build log to completion prior to hooking up anything. Adding components step wise in increasing complexity is always good practice IMO. I know we all get the spirit and jump in feet first, but a small bit of diligence can go a long way.
-
Permalink Reply by Michael Munson on -
I have been there as I just fired an output on my MUX chip due to a cross plugging in of my esc with power on the signal input instead of signal - Might be handy if the MUX was a "plugin" style chip rather than a soldered on chip for such problems. could save alot of future headaches for Arducopter users and others - Making it a simple failure point vrs small solder point
Mike
-
Permalink Reply by Ron Jacobs on -
If you email Chris Anderson, he will put your name on the list of people to help write the manual. That's the best way to get this into the manual.
I see it has been added, perhaps there should be a warnings section, listing all the potential-to-fry or potential-to-crash warnings.
-
Permalink Reply by Phoenix on
-
I am by no means an expert, but wouldn't wireless programming via XBee be a great solution to get rid of this problem? This would also be extremely helpful for those of us who are developing and playing with the code as it would allow for us to do wireless uploads of code changes while debuging, especially during test flights.
I am not sure how this setup would work with our current ArduCopter config as I don't have my Arducopter fully built yet, but HERE IS A LINK to a XBee wireless programming tutorial that seems like it might be something to look into as a solution to this problem and maybe even add to the WIKI as a required step. (We can add COMPLETELY WIRELESS PROGRAMMING to the ArduCopter feature list!)
I know I would love NOT to have to unlplug my ESC's etc and plug my board in via USB during test flights just because I am an idiot and mis-typed one of my variables, or forgot to uncomment parts of my code!!
Forgive me if this is already posted somewhere in the forum, i haven't quite made it through all of the posts yet
-
Permalink Reply by Dan Sibisan on -
so, how can we tell if the MUX is fried ?
In case of nay non function to know that is not the problem?
I understand that all functionality is OK , all blinking leds etc. no problem connecting to pc , but the out signal is not working , in case of MUX prob ?
I`m still waiting for my motors and esc, but I connected 2 servos to OUT 4 and 5 with this code.
APM_RC.OutputCh(4, APM_RC.InputCh(6)+(pitch)*1000); // Tilt correction
APM_RC.OutputCh(5, 1500+(roll)*-400); // Roll correction
The servos are receiving electricity when system started , but not responding to the giro etc.
Contests
Season Two of the Trust Time Trial (T3) Contest has now begun. The third round was a reliablilty/aerial photography round for both planes and copters, which is now closed. Stay tuned for the next round, beginning soon.A list of all T3 contests is here.
Top Content
Groups
-
Moderators
58 members
-
ArduCopter Evolution Team
106 members
-
Learning to program the …
54 members
-
UK Ardupilot Group
27 members
-
DIYDrones - CNC Project
59 members
© 2012 Created by Chris Anderson.
