I just posted a new experimental version of Arducopter with new PIDs and control laws for Yaw. It's download only for now and I wouldn't recommend trying it unless you can rigorously test it. Please be careful. I've flown this in Stable, Simple, Acro, Loiter, and Alt Hold with no known issues. But you never know! This version is not yet compatible with the mission planner.
New PIDs - I rewrote the control laws from scratch to add a PI Rate function. The end result should fly nearly identically to the current version. The nice detail is that we can use NG PID values for easy transition!
Before: -> After
Stabilize P –> Stabilize P (Use NG values, or 8.3 x the older AC2 value)
Stabilize I –> Stabilize I (Stays same value)
Stabilize D –> Rate P (Stays same value)
–> Rate I (new)
I added a new value – an I term for rate. The old stabilization routines did not use this term. Please refer to the config.h file to read more about the new PIDs.
I added the framework for using DCM corrected Accelerometer rates. Code is commented out for now.
Added set home at Arming.
Crosstrack is now a full PID loop, rather than just a P gain for more control.
Throttle now slews when switching out of Alt hold or Auto modes for less jarring transitions
Sonar and Baro PIDs are now combined into a throttle PID Yaw control is completely re-written.
Awesome when wil it be ready for th MP?
Hi Jason, very good enhancements. Like to set home at arming, but why the 'tune down compass' (dmc_yaw_kp & ki) in the arming routine?
Another question, don't know if I'm wrong, but is altitude kept in the path between waypoints?.
Guess the framework is made ready for rate controlled waypoint approach ?, speed up to next waypoint, slow down near the waypoint?
You're one excellent coder!
Wow, you certainly have been busy !
Those improvements all sound really promising. I'm gonna take my copter to a show tomorrow, so I won't fiddle with it now, but on monday I'll give the new code a shakedown !
you need to convert that to decimal degrees. = 0.733
and how about my ask about motor+prop+frame size, you using for this test?
can you share?
Convert that to decimal degrees here:
I believe the answer is 6.65
What I sent you is an Angle, Minutes, seconds to decimal degrees converter. You take the declination and enter in to convert it to decimal. So 6° 39' will be 6.65° once converted. Enter that into the Mission planner or CLI.