Open GoogleCodeExporter opened 8 years ago
Please provide more information about what situations you see this behavior as
well as why you think it is not desireable.
Original comment by dewei...@gmail.com
on 26 Dec 2011 at 8:54
Much lower and much higher pulse widths, if applied to the servos, are likely
to damage them.
I am doing a detailed testing on the Arduplane and have observed many bugs in
Arduplane 2.26 and even in 2.27alpha. Please let me know if I should create
separate issue for each bug ?
I will provide more details soon.
Regards
Rana
Original comment by narpat...@gmail.com
on 26 Dec 2011 at 10:57
I get this when elevon mode is enabled:
1. The elevon servos will be driven outside the travel limits you programmed if
you put the stick in the corner (or require extreme amounts of roll and pitch
correction from the autopilot. This is normal and your setup show allow for it.
2. The rudder functions don't work when in elevon mode. If anything other than
MANUAL mode is selected when starting the APM it will drive the rudder servo at
900 us PWM.
Are these the cases you're concerned with?
Original comment by philcole...@gmail.com
on 29 Dec 2011 at 3:59
@Narpat007
No, you do not need to open separate issues.
Please provide details here
@Phil
You are correct - rudder is not supported with elevons at this time.
Original comment by dewei...@gmail.com
on 31 Dec 2011 at 11:13
I believe the bigger issue here is aligning the pwm range to his servo range.
This is the part that is custom on each of our setups; and cant be set at a
default for everyone!
This is why we do radio calibration. at every oppertunity!
Servo side is always as accurate as the pwm output... its the radio side that
lacks exactness.
Radio Trims help take out human error of servo linkage adjustments etc.
So for example in both planes and quads, the motors attempt to reach a given
rpm given a commanded pwm; which is based on esc calibration to radio travel
limits of a mechanical gimbal...
Something which I feel turns exact science into ballpark math.!?$:)
Original comment by Draconis...@gmail.com
on 13 Jan 2012 at 12:02
Original issue reported on code.google.com by
narpat...@gmail.com
on 26 Dec 2011 at 10:01