 | | Re: Yet another Q: IR messages
|
|
Thanks for the information so far. Is there any NQC command similar to the RCX-code "wait until message"-block? --Tobias (24 years ago, 30-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | "Speed" of control statments
|
|
I have been currently working on a control program that necessitates the highest reaction time possible. Does anyone what the fastest control statements would be using NQC (making the outputs react to sensor values as fast as possible)? i.e. Which (...) (24 years ago, 30-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Yet another Q: IR messages
|
|
To send a message use the following: SendMessage(<variable> or <number>); The variable must be of integer type between 1 - 255 The number must be between 1 - 255 To read a message from the IR port do <variable> = Message(); This will put whatever (...) (24 years ago, 29-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Yet another Q: IR messages
|
|
Hi Tobias, this could look something like this for example : int global_message; // place to store and read messages for every task task main() { start Read_Messages; // start Receive_Message Task while(true) { switch (global_message) { case 1 : (...) (24 years ago, 29-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Yet another Q: IR messages
|
|
I can't figure out how to use the IR commands. I've tried, read a bit in the documentation, but still have no clue. I'd like to know how to: a) Send a message (and decide what message it should be) and b) learn how to recieve messages Thanks in (...) (24 years ago, 29-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | RE: Electrical Data Link between 2 RCXs
|
|
(...) Hi :) (...) Heheh, my feelings exactly before "bumping" into LUGnet community almost a year and a half ago ;) Ok, now, about the way I use Timer() and will try to use FastTimer() or counter loop if proven more effective. I have no need to get (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.nqc, lugnet.robotics)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
Hi Dean, thanks for your interesting idea for a reduction of transmission time. I will deal with that as soon as possible. Your questions: (...) Version 2.0 (...) No. Do you think that is faster? (...) No, just the transmission program. (...) Good (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
Hi Marco, it is always interesting how many other people in the world do have the same problems or are dealing with the same subject. Sometimes I had the feeling that I dealt with "exotic" problems but then I realized that other "Mindstormers" had (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.nqc, lugnet.robotics)
|
| |
| | RE: Electrical Data Link between 2 RCXs
|
|
Hi Bernd :) I see we're working in the same subject here :) *great* If you care to browse lugnet.robotics old thread "VLL *input* for RCX/CyberMaster (in NQC) ?" or the newer one, starting with "CM-RCX" (the subject had some variations) Your (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.nqc, lugnet.robotics)
|
| |
| | 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: 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)
|
