|
|
 | | Re: Apparent 'time-out'
|
| (...) Yes, the flashlight consistently makes the RCX go "dead". (...) No rush. PATIENT: "Doctor, it really hurts when I move my arm like this." DOCTOR: "Then don't move your arm like that." (...) I look forward to the article. I am currently working (...) (23 years ago, 9-May-02, to lugnet.robotics.rcx.pbforth)
| | | | | Re: ___cmpsi2
|
| (...) How did *that* happen?!!?!? Just curious. Somebody should point a finger, just for yuks. -Kekoa (23 years ago, 9-May-02, to lugnet.robotics.rcx.legos)
| | | | | RE: Apparent 'time-out'
|
| (...) OK, so if the RCX is in the "dead" state, shutting down the GUI and restarting the GUI makes no difference. And you can always clobber the RCX running pbForth by shining a light at it? I'll see what I can do on this end to reproduce the (...) (23 years ago, 9-May-02, to lugnet.robotics.rcx.pbforth)
| | | | | Re: Apparent 'time-out'
|
| Shutting down the GUI and starting it back up has no effect, pbForth continues to respond correctly. Adding words to the dictionary doesn't seem to make any difference either. Whether having just uploaded the firmware or having the RCX active for (...) (23 years ago, 9-May-02, to lugnet.robotics.rcx.pbforth)
| | | | | Re: semaphores
|
| a short example: #include <semaphore.h> // for semaphore opperations // global buffer, used to store incoming messages. // the buffer is checked by the application waiting for the message. struct inn_msg{ char *msg; sem_t lock; }; //create a (...) (23 years ago, 9-May-02, to lugnet.robotics.rcx.legos)
|
|
