|
|
 | | Re: communication between NXT and RCX!?
|
| (...) The NXT has a new sensor control bus. That allows many ways to interact almost anything you want. From Hear-say i have heared that HiTechnics is building an NXT - IR converter in the size of a NXT sensor.. Daniel Wittenaar Brickbash Robotics (20 years ago, 5-Mar-06, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | Power down time
|
| In The administrator section you can set the power down time - the time that the RCX will stay on, unattended. The range is 0-255 with 0 meaning always on, and the rest in minutes. No matter what time I choose, I can't make this work all the time. (...) (20 years ago, 16-Feb-06, to lugnet.robotics.rcx.robolab)
| | | | | communication between NXT and RCX!?
|
| Since the NXT does not have IR capability, it will not be communicate with the RCX brick. If there is no such plan from LEGO to build in the new NXT such capability, I am afraid they are going to put RCX brick in an obsolete track!? O, no! ---...--- (...) (20 years ago, 9-Jan-06, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | The NXT generation version
|
| from the lego press release... ...The heart of the new system is the NXT brick, an autonomous 32-bit LEGO microprocessor that can be programmed using a PC, or for the first time in the retail offering, a Mac. After building their robots, users (...) (20 years ago, 5-Jan-06, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | The NXT generation version
|
| Approved: emabrey@storming-robots.com from the lego press release... ...The heart of the new system is the NXT brick, an autonomous 32-bit LEGO microprocessor that can be programmed using a PC, or for the first time in the retail offering, a Mac. (...) (20 years ago, 5-Jan-06, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | the new MINDSTORMS NXT
|
| Hi everyone, Wonder if anyone knows much about the NXT. Exciting addition, but I am concerned with the software compatibility with the future Robolab 3.0. From what I understand, beta Robolab 3.0 only is underway for Mac platform. How about the (...) (20 years ago, 5-Jan-06, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.robolab)
| | | | | Re: avoid messaging
|
| (...) I'd agree that a physical block is the easiest, although there is a software solution. The RCX can not recieve a command while it's transmitting - so if you saturate the transmitter with things to do, it will not be able to "look" for any (...) (20 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | RE: avoid messaging
|
| Yes, I indeed have an attachment which will act like blockage, but not a full one though. Sounds like this is the fastest and easiest to do. I fully understand the opcodes concept, as I myself wrote compile code before. However, these kids age only (...) (20 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | Re: avoid messaging
|
| (...) If you have an event waiting for a message, I doubt it will have much impact on the speed of the rest of the program. However, this will not catch the messages you're looking for. You can't use the "mail" function to receive op-code, such as (...) (20 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | avoid messaging
|
| Hi In order to avoid unwanted interruption, such as remote shutdown, from other RCX during execution time, I wonder if the only thing can be done to safe-guard my RCX will be having an independent task dedicated to receive message (mail). This, of (...) (20 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
|
|
