 | | Re: Apparent 'time-out' —David Rojas
|
| | | The GUI version is 2.1.0. The pbForth version (COLD) is 2.1.2. I am using the USB tower with RIS 2.0. Once the RCX stops responding, if I pull out a battery and re-upload the firmware, the RCX will respond again to the same GUI session. In other (...) (23 years ago, 9-May-02, to lugnet.robotics.rcx.pbforth)
|
| | | |
| | | | | RE: Apparent 'time-out' —Ralph Hempel
|
| | | | (...) Thanks... (...) When the RCX is sitting idle, the pbForth interpreter is spinning and looking for characters from the IR. I doubt that sunlight (or flashlight) would be interpreted as valid chars, and the error handling should just discard the (...) (23 years ago, 9-May-02, to lugnet.robotics.rcx.pbforth)
|
| | | | |
| | | | | | Re: Apparent 'time-out' —David Rojas
|
| | | | 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: Apparent 'time-out' —Ralph Hempel
|
| | | | (...) 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' —David Rojas
|
| | | | (...) 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)
|
| | | | |
