| |
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 course, might be quite time consuming to the RCX.
I wonder if there is anyone out there using the same hacking method and
observe any negative impact to the actual working task. Or, the negative
impact may be negligible. Or, perhaps there is better and smarter way to do
this.
Thanks for your input in advance!
----------------------------------------------------------------------------
--------
Best Regards,
Elizabeth Mabrey
--
MIME ATTACHMENTS DISCARDED:
1. Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Length: 2241
|
|
Message has 1 Reply:
 | | 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)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
