 | | Re: r/c servos
|
|
(...) Let's say a 0.7 ms pulse results in a rotation of 0 degrees. Let's say a 2.0 ms pulse results in a rotation of 180 degrees. If all you had were 0.7 ms pulses and 2.0 ms pulses, you'd be able to choose either 0 degrees or 180 degrees, resulting (...) (27 years ago, 20-Aug-99, to lugnet.robotics)
|
| |
 | | RE: r/c servos and firmware
|
|
(...) Exactly. See (URL) examples. These servos have a little disc or cross on top with holes at the edges. The servos can turn the disc only 45 degrees in each direction. They are used for moving flaps or rudders on model airplanes. You bend a 90 (...) (27 years ago, 20-Aug-99, to lugnet.robotics)
|
| |
 | | RE: r/c servos and firmware
|
|
(...) Whew! I'm glad I got that much right :-) (...) We could check OC1B and if it's "close" just turn off the motor...as far as the long timer goes, OC1A should always force the output off...on the other hand, the OC1B could be set NO GREATER than (...) (27 years ago, 21-Aug-99, to lugnet.robotics)
|
| |
 | | Re: r/c servos and firmware
|
|
(...) In (...) make (...) least (...) Hello, New mindstorm user...been lurking for a while. WRT to servo motion -- it is fairly easy to modify standard servos for continuous motion. $ would put this motor about the same cost as lego so not sure of (...) (27 years ago, 21-Aug-99, to lugnet.robotics)
|
| |
 | | Re: r/c servos and firmware
|
|
(...) Thinking about this more, I do not know what I was thinking earlier. Since you are in an ISR, you know can count the number of cycles in the instructions between reading the FRT and enabling the OCIB interrupt, and you can estimate "close" (...) (27 years ago, 21-Aug-99, to lugnet.robotics)
|