| | Checksum download of text to RCX
|
|
I wrote a simple addition to pbforth that allows it to receive text with a checksum across every line. Every line is ACK/NAK-ed and if necessary resent. Timeouts are not implemented. Now, the main word looks like this: : PBX-RECEIVE ( -- ) BEGIN (...) (25 years ago, 2-Apr-00, to lugnet.robotics.rcx.pbforth)
|
|
| | RE: Turning power off?
|
|
(...) It's probably bad luck. Two weeks running is about normal if you're doing lots of IR downloads. The IRED takes quite a bit of current when transmitting. The POWER_OFF does shut things down....I really do forget if RCX_SHUTDOWN is necessary. (...) (25 years ago, 12-Mar-00, to lugnet.robotics.rcx.pbforth)
|
|
| | Turning power off?
|
|
To my dismay, I discovered this morning that the batteries of the RCX were empty. And it's sunday :-( It is possible that I forgot to turn it off, yesterday evening. But aside from this, I use the sequence LCD_CLEAR LCD_REFRESH POWER_OFF to turn the (...) (25 years ago, 12-Mar-00, to lugnet.robotics.rcx.pbforth)
|
|
| | RE: The pain of communicating with the RCX
|
|
(...) Yup. Remember that the Forth interpreter can't deal with text in special packets. It may be an improvement by limiting the time between characters. I think that ascii-xfr may dump chars without enough time between them... (...) If you use the (...) (25 years ago, 10-Mar-00, to lugnet.robotics.rcx.pbforth)
|
|
| | Re: The pain of communicating with the RCX
|
|
(...) huh? Do you mean it just writes text to the RCX without any synchronization or checksums? Then how is it going to be an improvement over a plain ascii upload using e.g. ascii-xfr? (...) But then you can't use those constants (i.e the words, (...) (25 years ago, 10-Mar-00, to lugnet.robotics.rcx.pbforth)
|