Greetings all ardumates, I am almost loosing my faith for my quadcopter! :(

The basic quad installation has been providing me plenty of joy during the past months. I counted that there have been dozens of succesful missions and in calm and quiet evenings the escorting of the flying companion has been just mint... but lately something has changed and I cannot trust my installation any more.

The copter has now crashed four times in short time and each time most of the mechanical parts had to be replaced - twisted arms, sure all the propellers, one motor and one HD camera. The scene goes each time the same way: while you are flying the quad even in easy conditions, typically first three to ten minutes everything is just normal. Then without notice the copter starts to keep odd oscillating noise, like "wo-wo-woow-woow", then flips and hits the ground immediately. You never know when it happens.

I have carefully checked that all the propellers are balanced, rotating as intented and well fixed. Also all the motors are consuming the same amount of the current or replaced and ESCs have been calibrated to perform similar way. While I have build the construction now four times (and almost from the scratch with the new mechanical parts), there should not be any major defects with the arms, motors or propellers. And just the same construction was used when the flying was just perfect. Any ideas what error I am now repeating each time?

Please find attached the picture of my quadX still without the camera installation:

arducopterV2.png

The construction has been build based on the ArduCopter Quad v1.1 kit. However, the dome has been replaced to get a bit more weatherproof enclosure.

  • ArduPilot Mega 2560 board
  • ArduPilot IMU V1 board
  • Attached magnetometer + GPS + sonar
  • The firmware used 2.5.5
  • Default configuration settings
  • Motors 4 x AC2836-358 880kv
  • ESCs jDrones 30A
  • Props 12"x45
  • Lipo 4S 4500mAh or 4000mAh
  • Xbee telemetry 2.4GHz (up band)
  • Video 2.4GHz (low band)
  • Futaba 7ch 35MHz controller / EU air band
  • GoPro Camera Mount + camera


This installation was working just fine for several months. Only the firmware has been updated every now and then. The first pretty bad crash was done with 2.5.4 and now three flips with 2.5.5. 

Unfortunately I did not manage to film the crashes with observing camera, but perhaps the onboard camera might give a hint what is happening. So, I am enclosing two short videos that might give a glue?

The first one is just about 10 seconds. After some succesful flying and switcing the battery to a fresh one I made another takeoff. Almost immediately the copter flips while being still close to the ground:

Arcucopter3Crash (7MB)


The second 35 seconds video might give a better example. After assembling the copter again to the original shape it was time for give it yet an another opportunity and test the installation to check how stabile it is:

Arcucopter4Crash (17MB)  

Notice around the spot 29s (at least it is audible) the woow-woow-woow effect that comes without warning and drops your drone down!

I tried to figure out what log files might match the videos, but it was a bit difficult to be sure without proper timing information. Most likely the Arducopter3Crash is in the log #43 and the Arducopter4Crash is in the end of #45:

Flight Log #42

Flight Log #43

Flight Log #45


I am really wondering what makes it to do such things? Even if I assemble the copter the fifth time, it is clear that I do not dare to fly it until the root cause is solved. Really frustruating... any suggestions mates how I should proceed?

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Update: the root cause for the problem has been found!

    One of the four ESCs was broken and really nasty way: in that specific ESC there is a small segment of the control area (about 60..70% of the power) where the motor still spins but is just more or less shakes rather than makes any real good. It was really difficult to find the problem, but when making a fresh start with the latest software version and making the ESC calibration with 0...100% range I noticed that the "audio output" of that motor had a specific distortion within a really small control area. Actually, it was possible to stop the motor with fingers when the power stick was in just in proper position. Otherwise the ESC output acted just same way as any of the tree other ESCs. The fact seems to be that everything cannot be corrected even with great software - especially problems of the ESC that has a mind of its own. :)


    The compass problems were coming from the camera tilt servo just below the unit. I presume the actual problem of "the dropping drone" was the fault in ESC, but perhaps the compass was also getting bad data when the copter was oscillating based on the issue of one rotors loosing power every now and then in short segment of the control area and camera mount rocking accordingly. 

    Thanks for the help and support. Next I am throwing the ESC so far as I can and soon replacing it with new one. :)


  • Thanks for your input, that was really a good one!

    The magnetometer anomaly is a good finding in this case. However, what makes such measurement to become unpredictable? But still, when flying with stabilize mode... I am really disapointed that I loose the control of a flying object... when it is not following the controls of any decent RC model.

  • Moderator

    I'm sure some of the dev's will be able to diagnose better than I can but the graph of your yaw and mag heading (from #45) doesn't look right to me, surely the mag heading should not be bouncing all over the place? Maybe something's wrong with the magnetometer or something's affecting it that shouldn't be?

    3692424430?profile=original

  • Your experience mirrors mine.

    I am just learning to tune a jDrones hexa and was getting it quite stable.

    All was going well until I updated the firmware to 2.5.5 and then random short times after launch the copter just cuts the motors for no apparent reason.

    I am watching with interest if anyone else is having similar problems.

    The hexa was delivered built and test flown and I have taken it back to factory defaults but it is still doing it.

    Anyone have any suggestions?

This reply was deleted.

Activity