Hi – can I request some help with my home built 680 Pixhawk controlled quad please. Sorry if I’m not in the correct place in this forum.
The craft has done several autotunes and in some ways seems to fly ok however on most flights, possibly when yawing, it will over balance and being unable to recover, hits the floor. I am flying low altitude to avoid damage and have seen it recover once.
I am not familiar with analysing logs beyond the obvious – GPS, voltage, current, altitude info etc. and would really appreciate someone with more experience taking a look at this short log please.
Something is obviously going wrong around the 10300 line mark. The later error and failsafe are just about the radio being turned off.
Here are the PID settings:
Thanks in advance
David :-)
Replies
Hi - yes, but only one of them.
This is the ESC I'm using and only 1 of the 4 ESC's has earth and +5
He has each individual signal wire grounded. It does not matter where wires are connected - on esc or on pixhawk. And it not looks like out of sync. Too fast recovery.
Of course it would be good to check that there is no noise on signal.
It looks like hardware problem for me when viewing your log. FC controlled banking, but copter went to a different side. Same with pitch.
Does all your motors spin good? Al escs are calibrated? And so on...
diydrones_quad_crash.png
Thanks for your assesment. I noticed a dry solder joint on one of the pair of parallel batteries i power this craft with so it is possible this is the issue. I have repaired the joint but not had oppertunity to test it yet.
My batteries are rated at 60C so that should be plenty of power even if one fails to supply, however maybe the sudden dropout in supply is disruption enough - what do you think?
David
There shouldn't be dropout if one battery disconnects. It's a pity that there is no battery and current in this log.
But as we can see from screen that i attached - first thing what FC was done: increased throttle to almost maximum. Then copter starts to rotate in all axis, apm increases throttle to maximum, but with no luck. There is no power from motors. And it's falling.
May be your battery disconnected at start? If it is esc protection - one motor shuts off due lack of voltage and can cause such a thing.
Have you charged your batteries? May be one is fully discharged?
Hi - batteries have less than 15 short flights on them so this should not be the issue. The quad is recently completed and has never flown properly. Every time I get a short successful flight I think it is sorted and purchase a new undercarriage. When I come to fly it with new bits it does this, crashes and breaks another set of legs.
I tried another flight today (on long soft grass) lasting 7 mins and it faltered at least 3 times at about: 15:53:52, 15:55:18 and 15:57:55 - fortunately it did not hit the ground. Overall the flight seemed to go well and the craft is responsive.
This is my first self-built copter and I am making it up as I go so I may have something obvious going on. It has been stable enough to have auto-tuned.
I have posted a zipped log file of my flight today as opposed to the bin file, I was not aware that bin files did not contain all attribute information.
I would really appreciate any assistance I can get
Many thanks
David :-)
2015-09-17 15-51-25.zip
I was trying to say: if batteries was in parallel they will be discharged to a same amount. If one battery was disconnected due to soldering issues - it will be visible, that one battery is discharged more than another.
Bin files do contain all data. In fact bin file is downloaded from your vehicle, and then converted to log. So there is more or same data in bin a-priory.
I reviewed your log. Yes, there was three strange things at 15:53:52, 15:55:18 and 15:57:55. In last copter banked harder and first two were more smooth.
It is interesting that in first two glitches copter was banking only on roll axis. And one time to left, second time to right.
This should say that there is no problem with concrete motor.
But looking at copter behavior except those three moments I can say that it's tuned ok. It definitely can fly. And those three moments are looking as hardware issues. But i do not believe that it is battery or motor\esc defects. One thing to inspect - power distribution from battery to all escs. Maybe there is cold solder too?
Can you post video of your flight?
Vital - Hi, thanks - I now understand the battery stuff and the Bin/Log files.
The ESC i am using is 4 in 1 from Unmanned Tech HERE. I can look for more bad solder but the wiring is very simple and shared by everything on the ESC.
I will also see if i can find someone to opperate a camera :-)
Many thanks
David
Have you kept the 3.5mm bullet connectors on the motor connections? - they have caused grief in the past and received wisdom was to solder the motors to the ESC.
A 4in 1 ESC is an interesting concept but gives no option to swap a bad ESC out for testing and if one ESC goes down then the 4 have to be replaced.
Peter
Soldered directly to the board to save space and keep things tidy.
I had issues with the ESC though - it needed firmware revision to make it compatible with pixhawk. I may raise a query with UnmannedTech to see if this could be the issue
Thanks