I am configuring apm2 on my Zephyr2. I have the throws down to about +-35% on my futaba9c. In mission planner I configure, and then set the endpoints for each channel. I save and boot up the plane in manual mode... reduced throws work perfect! I switch to stabilize mode and the apm2 supplies FULL servo range nearly bending my pushrods.
How do I get stabilize, RTL, automission, (every mode) throw values to match the limits of manual mode? I want all the flight behaviors to match.
I just verified your report and find the same behavior. I have not looked at elevon mixing since last fall and don't remember this behavior in earlier revisions.
I have submitted it as an issue to the issue tracker to get it on the dev team's to do list.
Thanks so much Doug! Looking forward to flying my zeph!
Another question Doug, how long should potentially expect to wait for this fix? No exact quote needed, but days/months etc. I'm not sure where to track the dev progress.
Is this issue going to get lost in the to do list or fixed soon. I'm no expert on the dev/issue process, but I need to know if I can fly the zephyr within the next couple weeks or I am going to return my apm for not functioning as advertised.
Why not just set up your servos normally? Is there some advantage to your setup?
If I understand you right you want the radio calibration to understand that your full range (as sent to the APM) is actually only 70% of what the total range should be?
If I understand right then it isn't really an issue with the software. What you should do is set your radio to normal mode (100% range), calibrate it in APM, then switch your range back to +-35%.
The zephyr is very sensitive to control surface throw. It only needs about +/-35% range to fly great. I never want my elevon servos to rotate outside of that range.
The problem is, the apm gives +/-100% throw in any assisted/auto mode. So for example if I enter stabilize mode the servos will rotate way too far even to the point of crushing the foam body a bit.
I have set radio calibration (read original post) and it reads correctly. The problem is it doesn't use that "learned range" when making decisions. It sends out full pulse width instead.
Doug agreed it's broken software at the moment, I just wanted an ETA when it will be fixed.
I had the same issue. I just changed RC1_MAX=2000, RC1_MIN=1000, RC2_MAX=2000, RC2_MIN=1000. Works much better now. You can play with the values until you get the desired throws.