 | | I/R Strobe/Omnidirectional sender/receiver
|
|
Greetings all, Looking at some of the new posts like the conductor/piano player has got me to thinking about the multiple RCX interacting scenario. The biggest inefficiency to start with is having to direct the entire RCX toward the other one, have (...) (27 years ago, 20-Aug-99, to lugnet.robotics)
|
| |
 | | Re: Droid Dev. Kit, reprise
|
|
(...) They'll probably do what LEGO wants them to do. LEGO appears to be fairly inflexible and uncreative and will probably stick to their normal policy. LEGO's normal policy seems to be to tell the store it has been discontinued and allow the store (...) (27 years ago, 20-Aug-99, to lugnet.robotics)
|
| |
 | | Re: r/c servos
|
|
(...) 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 (...) (27 years ago, 20-Aug-99, to lugnet.robotics)
|
| |
 | | Re: r/c servos
|
|
(...) I can't understand this. Can you correct your grammar so it is clear what you're saying the average servo needs? - Robert Munafo (URL) LEGO: TC+++(8480) SW++ #+ S-- LS++ Hsp M+ A@ LM++ YB64m IC13 (27 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 (...) (27 years ago, 20-Aug-99, to lugnet.robotics)
|