Im currently using Holybro Tekko32 4in1 ESC & 880Kv motors with10 inch props.
The issue im facing is incorrect logging during arming.
When I was using motor test and have given 70% throttle, at that time RCou is logging properly as u can see in the video below and at that time drone has also took take off.
but While arming im seeing that ch11 is not logging correct RCOU even if drone has taken Takeoff.
in the picture below.
what is actually happening is while im giving take off, all channels are increasing there RCOU values accordingly but after 5-8 secs ch11 is setting to 1080, all the time.
Am I correct to assume this was done with the props removed? (Flat line I-term values suggest so) If so, it’s an invalid test of anything. The PID loop is trying to make corrections (even subtle ones) and because nothing is happening it just winds up and takes values to extreme. Might be fun to do, but it doesn’t tell anything useful.
You have Dshot enabled, so use it to set up a notch filter. That should be done before tuning.
Reset ARMING_CHECK,1 If it won’t arm, fix the problem, don’t disable the safety.
No, I was using props.
I have used drone test setup on which i have mounted my drone then i gave take off.
and I have explicitly disabled the arming checks for this setup only to check how the drone will perform in the air.
As previously, I got a crash just because of one motor was not able to give proper thrust.
I m attaching that log too.
Please have a look. 00000045.BIN
If the test is done with the drone secured it’s just as useless as doing it without the propellers. The PID loop will try to make corrections but the drone does not move or does not move as expected, so the controller will make unusual outputs.
So if this log is also done with the drone secured there’s no reason for me to look at it.
Run mission planner motor test. Make sure the motors run in the proper order, and the proper direction.
Reset arming checks to all.
Use the guidance material provided in the wiki or I suggest you try AMC.
You should rename the title of this post to “should I reset all to default and start over”. Then you would get a reply in the affirmative and with your level of knowledge use the AMC after doing so.
I just want to confirm whether my drone can achieve a proper takeoff, which is why I conducted the test in a secure environment. During the test, I observed that the drone does lift off when I give the takeoff command, and this is clearly visible. However, the logs are not reflecting the correct data.
Because of this mismatch, I’m hesitant to test it in an open field, as there is a risk that it may not achieve a smooth takeoff and could crash again.
I would also like to mention that I was using propellers during the test.
No, the logs aren’t reflecting the answer you want. Your test is invalid. Use the mission planner motor test. Verify that all motors are running in the right order, and right direction. Any test based on you arming the motors and using throttle will not validate motor function (Props on and secured, or props off, they are both invalid).
Do not try to test the attitude controller without propellers, it will not work, such tests are inconclusive and meaningless. Do not try to test the attitude controller with the vehicle tied down on the ground, it will not work, such tests are inconclusive and meaningless. At this point, the vehicle does not react to roll, pitch, yaw or thrust inputs in the way most people expect.
