I'm trying to control my pan/tilt gimbal with a joystick through the mission planner.
Having a bit of an issue, as the servos immediately go into motion when APM is powered. I have the two servos plugged into channels 5&6, and those outputs mapped to two axes of my joystick. I get no response from the servos when the joystick is moved.
The servos are continuous rotation, to get a better sensor field. Could this be an issue?
Permalink Reply by Joseph on April 1, 2012 at 6:53am Did you have any luck getting this working. I am have the same issue with this.
I have not gotten any new info as of now.
Thanks
Joe
Permalink Reply by OG on April 1, 2012 at 7:22am i have a similar setup on power up my gamble moves on its own & settles in flight so yes this is normal . the servos should be plugged into the APM output not in to the receiver ?
Permalink Reply by Joseph on April 1, 2012 at 9:28pm I got mine working today but the continuous servos are impossible to trim to stop them from moving all the time. I had to swap them out with a 180 and a 90 deg. servo. I ill get more info out to you tomorrow on my parameters.
Permalink Reply by Shyam Balasubramanian on November 3, 2012 at 7:41pm Dear All,
I am using continuous rotation servo for 'Yaw' control of my camera gimbal. I am using it for stabilization around a setpoint/ target angle, using PID's.
If I give a target of say 60 degrees, the servo should adjust its speed in such a way as to make it to 60 degrees (in a circle of 360 degrees).
The AHRS system gives a DCM Yaw output from [-180 to 180], i.e. 0 to +180 degrees and sudden transition to -179 and goes to 0 in the reverse direction.
The problem I am facing is this transition around the boundary from +180 to -179. If my target angle is say 170 degrees, once it nears 170 degrees the servo speed reduces and when it reaches 170, the velocity becomes zero to a standstill. Having the same 'Target angle' if the orientation of board is such that yaw output is 180 and then a slight change in orientation cause a sudden change to -179 (This is a difference of almost 180 - (-179) ~= 360). The servo speed reverses from relatively slow to fast, due to this vast difference to compensate.
Is there a workaround? or a method to compensate for this problem? This is not there in the code. Any help is appreciated...
Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.1286 members
87 members
39 members
24 members
5 members
© 2013 Created by Chris Anderson.
Powered by
