| | 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)
|
|
| | RE: The pain of communicating with the RCX
|
|
(...) That's because the SREC upload uses the native upload code in the RCX ROM. It works really well but has to send each byte as a pair with the bits inverted. Also the header and trailer have to be added. The result is that it would be impossible (...) (25 years ago, 10-Mar-00, to lugnet.robotics.rcx.pbforth)
|
|
| | Re: The pain of communicating with the RCX
|
|
On Thu, Mar 09, 2000 at 09:04:26PM +0000, Ralph Hempel wrote: [...On a TCL program to communicate with the RCX...] (...) Uploading srec files has been without problem for me; it's uploading text that's painful. Does your program uses some protocol (...) (25 years ago, 10-Mar-00, to lugnet.robotics.rcx.pbforth)
|
|
| | Re: The pain of communicating with the RCX
|
|
I might be able to help somewhat. I use my PC running FreeBSD to talk to my RCX (RIS 1.5). After much heartache I found that if I used "ecu" as my terminal, it worked. I tried everything just to try them, and ecu worked the best. Ecu is old, but it (...) (25 years ago, 9-Mar-00, to lugnet.robotics.rcx.pbforth)
|
|
| | RE: The pain of communicating with the RCX
|
|
(...) Depends on which side of the fence you are on... (...) Hmmm. This is not good. I have ghad very good success with CRT, but I'm going to try a more general solution with Tcl. (...) I stopped supporting it late last year because it only worked (...) (25 years ago, 9-Mar-00, to lugnet.robotics.rcx.pbforth)
|
|
| | Re: The pain of communicating with the RCX
|
|
(...) Does that count as `tempted by the dark side' or `seen the light'? :) (...) itself. (...) I tried near and far mode, several distances, putting the tower and the RCX under a dark cloth... Everything I could think of except putting 'em where (...) (25 years ago, 9-Mar-00, to lugnet.robotics.rcx.pbforth)
|