| |
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 over half an hour with many words added, the flashlight disrupts any
further communication.
Are there any words that echo what is received from the IR port on the RCX? It
would make sense to get more feedback from pbForth to isolate where the problem
is entering the system.
David
In lugnet.robotics.rcx.pbforth, Ralph Hempel writes:
> > 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.
>
> Thanks...
>
> > 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 • words,
> > it doesn't appear to be the GUI that is experiencing the problem. It will
> > continue to send messages after the RCX has been rebooted.
>
> > It seems that it may be due to handling communication errors that the • problem
> > comes up. I can recreate the problem exactly every time by pointing a
> > flashlight at the RCX. The first time the problem happened was in the late
> > afternoon when I was sitting next to a bright window. Once the • communications
> > are interrupted, the RCX will not respond again. There should be a way to
> > handle this type of error and regain the ability to communicate.
>
> 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
> char anyways
>
> The GUI might well be the culprit. What happens if you shut down the
> GUI and restart it? Does pbForth respond then.
>
> Also, when you point the flashlight at the RCX, is is just sitting
> after uploading firmware, or have you added any words to the dictionary?
>
> Cheers, Ralph
|
|
Message has 1 Reply:
 | | 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)
|
Message is in Reply To:
| | RE: Apparent 'time-out'
|
| (...) 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)
|
7 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
