|
 | | Re: Remote control under linux
|
| (...) Nice work! Glad to see a native Linux version of this. Quickly scanning your source code (no Linux machine to run it on today!) I notice that you send RCX opcodes in order to emulate the effect of each button on the remote. This is an (...) (21 years ago, 23-May-03, to lugnet.robotics.rcx)
| |
|  
long
(score: 0.383)
|
|
| |
|
long
(score: 0.383)
|
|
| | Re: permissions
|
| (...) Thanks! But rather than do things for a single user I opted for: chmod 666 ttyS0 If I'm not mistaken, this will give every user access to Serial port 0 (comm 1). Since my system only uses comm 1 for the lego tower this seems like a safe thing (...) (23 years ago, 15-May-01, to lugnet.robotics.rcx.legos)
| |
|
tower
(score: 0.382)
|
|
| | Re: Sensor Commands and legOS 0.2.3
|
| (...) TOUCH_1 is a macro defined in dsensor.h starting form version 0.2.4. If you don't want to upgrade, here is the code: #define TOUCH(a) ((unsigned int)(a) < 0x8000) #define TOUCH_1 TOUCH(SENSOR_1) #define TOUCH_2 TOUCH(SENSOR_2) #define TOUCH_3 (...) (23 years ago, 24-Apr-01, to lugnet.robotics.rcx.legos)
| |
|
range
(score: 0.381)
|
|
| | Re: remote control and rcx
|
| (...) The RCX will not respond to the remote until you succeed in downloading the firmware. The built-in romware does not listen to the remote. The remote can be used with many RCXes at once, since it is a one-way protocol with no response messages. (...) (21 years ago, 8-May-03, to lugnet.robotics.rcx)
| |
|
long
(score: 0.381)
|
|
| | More LNP Issues
|
| Thanks to Rainer for helping me with the stupid compiler bug :) Now that the PC side of LNP is working, I'm having troubles with the RCX side... I've modified the LNP sample provided on the WinLNP page as follows (with the includes trimmed): #define (...) (23 years ago, 22-Apr-01, to lugnet.robotics.rcx.legos)
| |
|
range
(score: 0.381)
|
|
| | Re: TIME STAMP for a LNP distributed robot
|
| Hi, The sys_time variable is the basic timekeeper for BrickOS. It is a 32-bit integer that is incremented every millisecond by the kernel. In older versions of the kernel you could access the variable directly, however, in 0.2.6.10 and later you (...) (21 years ago, 7-May-03, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 0.381)
|
|
| |
|
long
(score: 0.381)
|
|
| |
|
long
(score: 0.380)
|
|
| | Re: Electrical Data Link between 2 RCXs
|
| It's me again with some improvements for an "Electrical Data Link between 2 RCX". In the current version I changed the default condition of the link to "high" (in the transmitter: OFF(OUT_B)) so that the receiver has a 1 at its sensor input. So, you (...) (23 years ago, 17-Apr-01, to lugnet.robotics.rcx.nqc)
| |
|
range
(score: 0.380)
|
|
| | Re: Revisions to RcxCC
|
| hi John, Great idea, (for RCXcc is a very good application, even my children can write programs with it) I just had the same idea, but my time is limited. I've need some more ideas, here are some of mine ideas (and bugs), I wanted to implement: - (...) (24 years ago, 4-Apr-01, to lugnet.robotics.rcx.nqc)
| |
|
ir
(score: 0.379)
|
|
| | 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)
| |
|
ir
(score: 0.379)
|
|
| | Re: Yet another Q: IR messages
|
| (...) Hi Tobias I'm not very familiar with NQC events, but if you want to use a blocking function for receiving your message, use parts of the code i posted before. int local_message = 0; int global_message = 0; task main() { //do what you like (...) (24 years ago, 31-Mar-01, to lugnet.robotics.rcx.nqc)
| |
|
ir
(score: 0.379)
|
|
| | Re: Yet another Q: IR messages
|
| If I am understanding what you want correclty (I have never used the RCX-code) only NQC then try this. Assume: RCX2 is sending message # 15 to RCX1. RCX1 is in a waiting state until it gets the message RCX code: . . . While (Message() != 15){ ++i; } (...) (24 years ago, 31-Mar-01, to lugnet.robotics.rcx.nqc)
| |
|
ir
(score: 0.379)
|
|
| |
|
ir
(score: 0.379)
|
|
| | WS3D RCX Challenge #6 Results
|
| Last Saturday was the Workshop 3D RCX Challenge #6. As usual, the competition took place in the Pacific Science Center in Seattle. This time the events were Single RIS Line Tracking, Unlimited Line Tracking, Lightweight Sumo, Walking Sumo, and Puck (...) (21 years ago, 15-Apr-03, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.events, lugnet.org.us.smart)
| |
|
long
(score: 0.379)
|
|
| | 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)
| |
|
ir
(score: 0.379)
|
|
| | 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)
| |
|
ir
(score: 0.379)
|
|
| | Re: Running IR in the background
|
| Hannes, Did you ever get any help with your question (below)? I'm trying to use the IR port on RCX along with light sensor (passive) as collision detection device. Having the same problems you're having. Clayton (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 0.379)
|
|
| | Re: Running IR in the background
|
| (...) Congratulations! Could you post your source code here, to compare with the solution that we previously submitted to an almost identical question? We use an active light sensor reading in one taks, with a different task bangin zeroes using (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 0.378)
|
