 | | Re: New Group?
|
|
(...) Well, sometimes there's only one way to find out -- build it and see if they come. If we create a group/list for it and it turns out DOA then we can either delete it or ignore it. If there's a user-base for GBP, and you've got (...) (24 years ago, 26-Mar-01, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
Thanks for the info on the electric datalink. It's a clever idea that I never would have thought of myself. It seems to me that you could cut down on your transmission time if you changed the shape of your pulse train. The pauses between bits don't (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: The sound of train
|
|
I guess not - I don't even know what it is. All I have seen of this is some schematics of the electronic circuit for it. And that was 1 years ago I think Sonnich Zhengrong Zang <mikezang@iname.com> wrote in message news:3ABEA0D8.2F4462...ame.com... (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
I am not positive about this, but some of the jitter may be due to the mode in which the motor outputs work. They are PWM at 125 Hz, so I am wondering if, when the byte code to change an output setting is executed, the new state setting is placed (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
Hi Bernd, When you need it really fast, you sholud use legOS instead of NQC. A program written with NQC uses the LEGO firmware, which is a ByteCode Interpreter. This pogram is interpreted Byte after Byte from firmaware. The firmware executes the (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.nqc)
|
