 | | 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 (...) (25 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 (...) (25 years ago, 20-Aug-99, to lugnet.robotics)
|
| |
| | Re: LEGO section starting on Compuserve
|
|
(...) They have access to the Web if they *want* it, but there are a variety of reasons many don't venture outside CIS. Some background: Many CIS members joined long before the Web and proliferation of local ISP's exploded onto the scene. The (...) (25 years ago, 20-Aug-99, to lugnet.general)
|
| |
| | 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) (25 years ago, 20-Aug-99, to lugnet.robotics)
|
| |
| | Re: r/c servos
|
|
(...) The answer is pretty simple, actually. In order to control a servo, you need to use pulses whose lengths are on the order of 1-2 ms. The more steps you get in that range, the more servo positions you can use. NQC can't produce pulses as short (...) (25 years ago, 20-Aug-99, to lugnet.robotics)
|
