After a week spent working on my Arducopter 2, I have still failed to get it airborne and I've broken two props already. In the interests of other people avoiding the misery I've had to go through, I'll post my lessons/experience here in a summarised form. The brevity of what I've written doesn't reflect the amount of effort put in, or combinations of solutions attempted. I'll conclude with that I think the problem is and I invite suggestions from more experienced users.
My first mistake was to not check that the GPS cable was plugged into the correct port. I believe my AC was shipped with it plugged into the incorrect port, and this prevented it from arming. I spent a long time trying to get the motors to arm, setting up again & again, trying different TX/RX combinations and even switching between two APM1.4s that I have. Eventually I pulled out the GPS and got it to arm, and that prompted Chris to suggest that I may have it plugged into the wrong port. Given that the ports on the IMU and the APM board are identical, some sort of warning about this in the 'Troubleshooting' page may be helpful.
However my problems were not over. I then could not get the AC off the ground - it flipped first time out and broke a prop. I went through the appropriate troubleshooting menu for flipping and wobbling and got no further.I decided to change radios from DX7 to DX8, because the latter has a throttle curve and permits very slow throttle advance - allowing one to catch a flip before it goes over and analyze it. I couldn't get an AR7000 or AR8000 to send signal to the APM, eventually an OrangeRX 9 channel worked. I did some slow 'flips' and noticed that it was pitch instability - in both directions, implying that the stabilizing compensation was reinforcing rather than offsetting a change. Roll and yaw stability seemed to be working.
I ran the latest firmware, reset everything and saw that various sensor feedbacks in the APM Planner were now garbage (fluctuating all over the place). I switched IMUs again, set everything up again, and my second IMU showed stable feedback although the compass on this one seems to be broken. Nevertheless, encouraged by the stable gyro feedback I decided to try to fly again. I set up and slowly raised the throttle, but although I tried to catch it, this also ended in a flip and another broken propeller.
This is about as much as I can stand at the moment. Given that there are two different issues on two different IMU boards & that I have ruled out all other options, I have to assume that they are both faulty. My question then is - has anyone else been sent out-of-box faulty goods by uDrones? Is quality control an issue? I don't know if sending the boards back to them will help, but maybe someone else has done this and had success?
I also fly a GAUI 330x with a HoverFly Pro board, and I also fly two MK hexas, so I'm not a total newbie when it comes to quads. I've just never had this many problems on any one project.
John, sorry to hear about your problems, which do indeed sound frustrating. As always I'm here to help--you just have to ask. Did you contact Udrones for customer support?
I can help set up a Skype call with them to walk you through the issues.
I always do a hand test after setting up a quad. Hold the quad, props on, and give it 1/3 throttle. Make sure your careful that the props won't struck your hand as you slowly bring up the throttle to 1/3. If it will flip on the ground it will not feel stable in your hand and you can easily tell by feel. Try and pitch the copter, does it resist and try to come to level? When you push the pitch and roll control, does it pitch and roll accordingly?
The CLI includes many helpful tests to verify your radio is configured properly and you IMU is functioning.
Thanks for the feedback guys.
@Chris: thanks, I will take you up on an offer of a Skype call. Will coordinate via email. Haven't spoken to uDrones yet but I will once I've read through the feedback here, maybe 'pilot error' is yet the problem!
@jason: good feedback, I've never done the hand test because I've never yet needed it. Believe it or not, these are the first props I've broken on any quad of mine. I've never experienced such a violent flip, seemingly accelerated & hard to stop. But yeah, I certainly will next time as part of my preparation.
Re the CLI, I went through every single test mutliple times. The Wiki doesn't explain how to interpret the tests, but I just applied common sense. The IMU test, for example, seems to represent sensor feedback and if the AC is static you would expect close to zero data. In the 'gauges' part of the APM Planner flight data, I could also see gyro feedback etc & could tell when my one IMU went haywire.
Re radio setup - no problems. I made sure the endpoints/travel were acceptable and mapped the correct switches to AUX1 and 2 etc. I tested all the radio output in the CLI test and the guages window in APM Planner. I successfully enabled AH on the ground so I'm sure the switches and the sticks are correct. Radio setup is part & parcel of other quad setups so I'm sure I'm ok on this score. I love the DX8 for its advanced options & especially the throttle curve - makes quad flying without AH much easier.
@ Matthew - I did scour the wikis. One thing I find confusing is 'disappearing' wiki pages. For example, in May I printed out and filed most of the AC2 Wiki, but I now can't find some of those pages. I couldn't find any reference, for example, to what role the dip switches play in quad setup. I assume none therefore. Re PIDS - since I run a stock standard AC2 with 28cm arms and standard motors & ESCs, I haven't changed them. Also haven't found help on how to analyse & adjust them either. Will check though - and if someone has a link to a reference on the PIDs I'd appreciate it.
@ Mike - OK send me some luck mate! Alternatively, maybe you can point me to a resource/wiki page on PID Tuning?
Hi John sorry to here about your mishaps, I've those days or weeks with those issues and it can really be frustrating. My first ACM board was from Udrones and it had fair share of crashes some 20-30ft drop and even had the IMU slightly detached to ATMega board but it is still runing until now (lesser crash). I've had 2 other boards that I soldered myself and they had their fare share of mishaps as well specially my latest frame (3rd). I am in no way saying you have missed anything or trying to think that you did not read wiki but for me if something is not right I will go back to basics.
A few things I find could cause flip during take off, my personal observation
1. Not properly leveled quad
2. wrong motor rotation CW / CCW or motor numbers
3. Oscillation during spool up (sometimes oscillating during take of seem to confuse IMU on whats level)
Things I do when everything goes wrong
1. Re-uplaod via arduino, i know they are trying to eliminate this but I find it my last resort
2. use CLI to preconfigure in the steps mentioned on wiki
Erase EEPROM/RESET/reboot/set frame/level/enable mag/set declination/enable sonar/go to test/run IMU (to initialize offsets)/go back to setup run radio calibration/then esc calibration then connect to Mission Planner and cofnigure my known PIDs/configure modes
(new version have the reset command configure to erase eeprom after reboot)
3. Run the the pretest the hand test 1/3 throttle Jason mentioned if everything seems to point correctly on pitch roll input and it stabilize when leveled then I would do the spool up
In my experince (personal) the combo of mission planner 1.0.57 with ACM 2.0.38 is my base setup. When newer firmware doesnt cut it for me I would go back to those. Again personal preference.
It is quite frustration when you have mishaps and sometimes cause you to even do more misjudgement but if you pause and reminisce for a while a light bulb moment happen. Just to share some stupid mistake, on my third frame I can never get it of the ground without it will always flip in different direction. I then attempted a hand launch and it flew but PID needs some adjustment so I brought it down and tried something. I then tried to take off from the ground and it took off but not stable I had to counter a bit again during flight notice I need more PID tuning needed so brought it down and change settings but it wont take off so I did hand launch but lucky I was alone as it tilted backwards towards the ground. all in all I broke 2 CCW blades. I almost gave up, but decided another go, loaded back v38 and had to replace the Groupner E-prop as I run out of spare with jdrones composite blades and to my surprise it is about a 70% success on take off and thats where I notice the oscillation on take up, my LG seems to cause the quad to be a bit bouncy during take off so I put some foams as feet bot it will take off without issues. Event got confident to put a gopro on the frame and had my first blog here on diydrones.
Sorry for the long reply but just hang in there some mishaps will happen but after those it will make you a lot more experienced and easier to spot issues in the future.
The quality of the data in the manual is getting better every day, but as a newbie, I can admit that I had some trouble putting it into context with what I was seeing on my quad. I simply did not have much in the way of reference, and I have been using a hanging tether rig, weighted to take up the slack, and that invariably results in a circling (as the quad tries to move about in any direction, it will swing in an accelerated circle because of the tether, I think my tether has too much tension.)
So the information in the manual is great, but what I needed to take better advantage of it was some visual examples of what bad PID settings look like, in flight. I found that in this video:
I am using non-standard frames, with much wider motor placement, but similar weight. I also hoped to locate some information/explanations of which values and in which direction you can expect to move the PIDs if your quad is larger, smaller, heavier, etc. I haven't found it yet, and I am gaining in my own experience. This is a DIY community, and I have been collecting photos and notes as I go. When I have developed more confidence in my experiences, I plan to contribute. For the moment, I am cautiously collecting and organizing data. I don't want to provide misleading information that might cause someone else to step backwards.
But that video above, if you put some mental work into it to translate the concepts and terms, helped me a great deal to be able to use the information in the wiki/manual.
I have to say, I really learned a lot when combined that video with what Jason says, hand-testing. Holding the quad in your hand has been the best technique for me to understand what is going on. Once you have a little experience with PID tuning, the information in the manual really starts to help. I don't want to sound like it is not good, it is great. But as I had absolutely no context, that video helped me a lot to be able to use the wiki/manual.
Jeff and Mike, thank you, that is valuable advice & took time to put together. My problem is not any of the basics, but I'll go through what you've advised step by step. Non-levelling, non calibrated ESCs, bad radio setup, oscillations are definitely ruled out. I haven't ever uploaded via the IDE, I wanted to avoid installing another app on my PC, but I'll definitely consider that so I can revert to an earlier firmware/mission planner combination.
I'm taking a little break from AC and APM for now, so I can get some flying time in :-P. When I pick it up again I'll go through the items you guys suggested.
OK I've now done the 'hand' start test and I have an interesting result. With the copter level in my hand and motors running, it feels basically stable, but when I ease the throttle up & start to tilt it - in whatever direction - it immediately accelerates into that direction. This is consistent with flipping off a ground launch.
@Jeff - believe me, it would not have flown for a second like that - as it is the copter was nearly ripped out of my hand. Whilst I really do see the value of PID tuning, I fail to believe my AC would be so unstable using the default PIDs for my configuration. Presumably they were set using exactly the configuration that I have.
I took that APM out and installed my other APM1.4. I erased, reset and set everything else up. In Mission Planner Flight Data, the gyros are still haywire. Basically the data coming back makes it look like the thing is performing acrobatics, while all the time its stationary on the floor next to me. Clearly there is a ghost (pilot) in the machine!
I then tried to arm the motors but I can't even get that far with this board. I guess its not surprising given that the processor thinks that the copter is highly unstable.
So in summary - board number 1 seems to be inverting the response to gyro feedback. Its as if the stabilization algorithm is doing the exact opposite of what its supposed to do. This could be a software or hardware issue.
Board number 2 simply has haywire sensors. This seems like a short in the electronics?
Just a reminder that its not one of the following (all checked many times over):
This must be a hardware problem, since many others are running the same software without problems.
Did you check that all the esc's are plugged into the right output port ?
If you move the sticks foward or sideways, does the quad want to move in the right direction, or also in the opposite direction ?
I'm going to assume you do not have this problem I will describe, but as it happened to me, I'll mention it.
I was using Castle ESCs, phoenix 50 lite (great ESC, by the way; a little heavy for our purposes, but if you are using a heavy quad... I mainly got them for motor testing, and in my flight builds I switch to lower amp/lighter ESCs) and had the cutout voltage too high. Everything worked great until I reached about 50% throttle. The drain on my power source pulled my voltage just low enough that one of the four motors cut out, resulting in an abrupt loss of throttle on one side (flips like a switch!) So I'm assuming your motors all keep spinning when yours flips (mine would spin for a while but was unpowered, just spinning on its own and stopped within a few seconds)
Something to perhaps try, swap the ESC and motor combo to the other side of your quad, see if it still pulls to the same side or if it pulls to the new side. It is a pretty easy thing to do, and may help to isolate the fault (I'm leaning toward u4eake's diagnosis here) to either the motor/esc or the APM?