Hi to all,
I still have a strange problem with yaw getting locked after some time of flying and not listening to the radio input. This happened over the versions from 2.0.xx to 2.1 final (the one I am currently using).
It seems that if I am not using yaw over some time during flying and do not change much the throttle input, the yaw input gets locked. I can give full yaw left/right without any effect. If I change the throttle stick position a bit, it seems to recover from the lock and gives me an unclean reaction, if I use yaw then the copter yaws but rises/falls quite a lot and the motors change rpm pretty much.
After recovering from this situation, yaw works good until I don't use yaw for a longer time, it then gets stuck again.
I don't know if I'm mixing up two different problems, but during hover in low heights (2 meter) and without throttle change, the copter begins to rise up and won't stop flying upwards until I reduce throttle.
I am using the new 3dr frame with the stock 880kv motors, the APM board (red and blue) and mostly standard PID settings (rate_p in stab mode lowered a bit). Reloading the firmware did not have any effect.
As yaw is realised by changing throttle on the motors, could there be some strange issue on yaw/throttle that causes this problem?
Btw, when constantly using yaw, this issue does not happen.
I hope someone can figure out what this is all about, so thank you in advance.
Hi to all, today during some video flight, I hat this yaw-lock multiple times. I could recover the ever-yawing/not responding copter from this by applying full throttle up and down.
Ok, so here ist the video:
After backwards flying, I wanted to turn around but the copter didn't stop yawing. You can hear when I apply full throttle to get control back and the copter "releases" yaw and can be controlled again.
I have uploaded the complete logfiles from this flight and the current settings from the Mission Planner, too. What I can see in the *.kmz file is that the orientation of the copter is not right. I don't know if this is normal behavior for copter-firmware, I know with arduplane the orientation was right.
I hope someone can help!
this morning I attached a servo with a long rod on the servo arm through an y-cable to the receiver output so I could see if the inputs from my transmitter are passed correctly to the APM.
After a few seconds of flight yaw did not respond, I could give full yaw left and right input and one could clearly see the servo going from full left to right without any reaction from the copter. I held down the yaw stick for a few seconds to full left and suddenly the copter reacted again correctly and yawed full left.
I took a look into the mavlog data and one thing seems to be very suspect:
The value for yaw in the ATT message varies from about 32500 in the beginning to somewhat 2900 to the end of flight, peaking back to 32500 over the entire flight.
Can anybody help please?
Have you the same yaw issue In Acro mode?
Have calibrated the throttle limit of the esc?
Your magnetometer responds correctly in the planner?
Have tried to make some corrections on the yaw pid?
The issue persists in Acro mode.
The ESC's are all calibrated.
The magnetometer responds correctly in tne Mission Planner. It shows the correct direction when connected and reacts correctly when I turn the copter around by hand.
The PID's of yaw are untouched, as I have a stock 3DR frame with 880kv motors. Anyway, the yaw should respond SOMEHOW if I apply FULL yaw left/right, but it seems to be stuck for some seconds or until the next bigger throttle change.
I know, since I start with ArduCopter I immediately noticed mismanagement of the yaw compared to other systems not necessarily more expensive, just for example the little KK (25$) have a nice yaw control, unfortunately there is still much to be placed in this direction, it all depends on a non-optimal matrix table of motors and it is something sadly lacking in AC.
Anyway i think you have a bad yaw or throttle pid, or some bad solder around... i hope you do not have bullet connector between esc and motors.
If the problem persists even in Acro the magnetometer has nothing to do.
Thanks for reply, Marco.
As I have relative good soldering skills and already double-checked EVERY soldering joint on the board after this happened, i can be pretty shure that there are no issues with this.
It seems to me that the yaw-routine (if there is one) lags or hangs, while the rest of the control loops keep on working. I will try to change the PID-values of yaw and throttle and see if the behaviour changes.
But I still would like to know if the very high value for yaw in the ATT message of the log files is correct or not. Could someone compare this with his own logs?
Marc, i created a short video with AeroSim that shows very well sometimes anomalous behavior of the yaw with throttle and altitude climbing.
I'm in Acro mode, without stabilization, magnetometer is disable.
I hope that in future it will be enabled better control of the yaw, perhaps with the potential for the planner to manage the matrix table of the engines due correct the yaw control with different configuration.
it seems like I have a defect board. Last weekend I nearly lost my copter because it was not responding on CH5 and did not RTL. The yaw-issue is still there, I just repeated the beaviour with the HIL-firmware and X-Plane. Yaw does not work while all other commands (roll, pitch, throttle) behave normal. I even attached a servo between tx and apm to filter out the possibility of a defective receiver.
For some reasons, yaw is not recognized sometimes, CH5 commands too, they sometimes dial in after a couple of seconds, sometims never. Something seems to be wrong with the pwm-encoder onboard. Solder joints are all perfect soldered, even carefully resoldered, cables and tx/rx changed a couple of times.
I bought my kit on December 2011 by a german reseller (lipoly.de), shall I contact the reseller or 3dr directly?
Thanks in advance and regards