Subject:
|
Re: r/c servos
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Fri, 20 Aug 1999 20:28:54 GMT
|
Viewed:
|
618 times
|
| |
|
|
In lugnet.robotics, lego-robotics@crynwr.com (John Barnes) writes:
> [...] If it's s/w, then the rep. rate could be dramatically reduced
> and finer timing resolution used to drive the servo position input.
If all you need to do is generate a pulse of a certain length, why can't you do
something like this?
Sleep(1); // synchronize with the centisecond timer
Fwd(OUT_A, 7);
Sleep(1); // 1/100 of a second
Off(OUT_A);
Sleep(2); // 2/100 of a second
// and repeat...
- Robert Munafo http://www.mrob.com
LEGO: TC+++(8480) SW++ #+ S-- LS++ Hsp M+ A@ LM++ YB64m IC13
|
|
Message has 1 Reply:
 | | 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)
|
Message is in Reply To:
| | r/c servos
|
| In response to the question about RC servos, I noted, while probing the signals on the I/O ports with a scope, that the motor power settings result in varying duty cycle square waves from 1:7 through 7:1 and finally full on as the parameter value (...) (25 years ago, 20-Aug-99, to lugnet.robotics)
|
5 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
