| |
In lugnet.robotics.rcx.pbforth, Ralph Hempel wrote:
> Hmmm
>
> The blip and LCD clearing, while useful for debugging may be messing things up.
>
> The characters are coming in way faster than the blip time, so you may not be reading
> the buffer fast enough.
>
> I would put code at the end of getHeader that displayed the current
> headerState VALUE on the display in the right most digit (program #)
> and the decimal value of the character received on the main 5 digit display...
>
> I'll play with it a bit this weekend.
>
> Ralph
Ralph, one more question. Are there conditions where the word EKEY would wait
for input (like KEY)? It seems to happen in my program.
Thanks
|
|
Message has 1 Reply:
 | | RE: IR problems
|
| (...) EKEY always waits for input. Use EKEY? to see if anything is available... Looking at the source, I see that there is a possiblity that in the time between checking for a character with EKEY? and actually reading it with EKEY, that an error can (...) (20 years ago, 30-Jan-04, to lugnet.robotics.rcx.pbforth)
|
Message is in Reply To:
| | RE: IR problems
|
| Hmmm The blip and LCD clearing, while useful for debugging may be messing things up. The characters are coming in way faster than the blip time, so you may not be reading the buffer fast enough. I would put code at the end of getHeader that (...) (20 years ago, 24-Jan-04, 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
|
|
|
|
