|
![](/news/x.gif) | | 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 (...) (19 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | ![](/news/x.gif) | | 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 (...) (19 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | ![](/news/x.gif) | | 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 (...) (19 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | ![](/news/x.gif) | | 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 (...) (19 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | ![](/news/x.gif) | | 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 (...) (19 years ago, 30-Nov-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| |