 | | 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)
|
| |
| | Re: sending variables betwen rcx's?
|
|
Hi Adam, if I understand your problem correctly, you want to transmit a sensor value from one RCX to another RCX which will work with that value. Now, if the 2 RCXs can "see" each other than simply use the Message statement. If not, you should take (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Electrical Data Link between 2 RCXs
|
|
It's me again with the subject "electrical datalink between 2 RCXs" (I posted some articles a couple of weeks ago). This subject may seem trivial but in fact it is not. Dealing with it, I discovered some "unpleasanties" in the general execution of (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | New Version of MacNQC
|
|
Hello, I have just released the final version of MacNQC 2.2. This release incorporates the latest (2.2 r2) version of the NQC compiler. Find and replace were added. An Auto indent mode in the editor was added. New RCX test and control panels were (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQCEdit
|
|
Dear two, I like your program very much. I have three suggestions: 1. Give a progress indication when downloading or uploading, if possible. 2. Identify unsaved changes by an asterisk behind the filename in the titlebar. 3. Allow to copy from the (...) (24 years ago, 23-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Event monitoring
|
|
(...) You can generate a message internally with InternalMessage(X); but X must be a constant (can't be a variable). I'm not sure if this will trigger the message event - I haven't tried it myself. If it does trigger an event, you could use the (...) (24 years ago, 15-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Event monitoring
|
|
Hi all, I have just switched to NQC 2.3 b1 (from 2.2) to implement the new features of the RCX 2.0. I have used event monitoring to clean up my if/else statements that control outputs. This works fine with all legal event sources, but I use allot of (...) (24 years ago, 14-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: sending variables betwen rcx's?
|
|
Hey, wow. did'nt know some of that. (...) (24 years ago, 13-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: sending variables betwen rcx's?
|
|
My advice would be to try and solve the problem using the regular message facilities (SendMessage(), ClearMessage(), Message()). If you have more than 255 values to convey between the RCX's, then you can try chaining multiple messages together (with (...) (24 years ago, 13-Mar-01, to lugnet.robotics.rcx.nqc)
|
