|
|
 | | 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)
| | | | | using rotation sensor
|
| Most of you are aware of the speed of the robot often causes parity in distance via the feedback of rotation sensors because of inertia. In our experiment, even with a robot with moderate speed. The parity seems to often occur right at the beginning (...) (20 years ago, 30-Nov-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | RE: different light readings...
|
| Hi David, I am sorry that I did not clarify my question. Thank you very much for taking the time out to help though! I fully understand that variations that light sensor produces, and I do make calibration the first thing to do before I run my bots. (...) (20 years ago, 15-Nov-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
| | | | | Re: different light readings...
|
| (...) Different light sensors will produce different readings. The range of readings you get will also vary between different light sensors (for example, between the same white surface, and the same black surface, one light sensor might have a (...) (20 years ago, 15-Nov-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
| | | | | different light readings...
|
| Hi, I have these 2 different light sensors. One reads "41" vs another reads "34" on the same area. I have troubleshoot it by switching ports, different RCX brick. The reading different stays the same. Is this reasonable because they might have a (...) (20 years ago, 14-Nov-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
| | | | | Robolab Motor Settings - ATTN. Dick Swan
|
| Hello Dick, I am working with a professor at the University of Central Florida and we would like to use the Robolab software for several of our robotics classes. The one issue we see in doing that is that the motor settings in the software only (...) (20 years ago, 13-Nov-05, to lugnet.robotics.rcx.robolab)
|
|
