 | | a correction! to r/c servo
|
|
Sorry about that! The resulting 0.03 mS pulse width increments would result in 5 degree increments in the position of the servo shaft. How about that? JB -- Did you check the web site first?: (URL) (27 years ago, 20-Aug-99, to lugnet.robotics)
|
| |
 | | Re: r/c servos
|
|
(...) I think what John was trying to say was that pulse widths between 0.7 ms and 2.0 ms give servo rotations between 0 and 180 degrees. With 45 steps in that range, you can control the servo in 5 degree increments. Seems to me he was approximating (...) (27 years ago, 20-Aug-99, to lugnet.robotics)
|
| |
 | | Re: r/c servos
|
|
okay.. how about this.. avg servo needs.. 60hz pulses.. 1.0ms pulse width = end point 1.5ms pulse width = middle of rotation 2.0ms pulse width = other end point that is the form of the data to the servo. so you need to out put pulses 60 times a (...) (27 years ago, 20-Aug-99, to lugnet.robotics)
|
| |
 | | Re: r/c servos
|
|
(...) That doesn't make sense either. If a single step of 2.0 ms causes 180 degrees of rotation, then how does 45 steps allow you to control it 5 degrees at a time? (...) Are you saying that the servo actually operates in steps of one degree each? (...) (27 years ago, 20-Aug-99, to lugnet.robotics)
|
| |
 | | RE: r/c servos and firmware
|
|
Ok, Here's my 2 cents on servos...read to the bottom if you are interested in helping to develop the code for this. The servo takes a 60Hz (approx) pulse width signal between 1 and 2 msec The pulses are fed into a little circuit that generates an (...) (27 years ago, 20-Aug-99, to lugnet.robotics)
|