 | | How much RAM is left?
|
|
(...) I believe that. 32k of RAM is a luxury for forth. That's another thing people don't generally understand about forth, they way it effectively compresses runtime software. I've heard of ram reductions of a factor of 5-10 for forth when compared (...) (24 years ago, 5-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Has anyone used lnpd succesfully?
|
|
(...) Of course, but also currently not very available. But i still would like to fix this problem, or at least find the reason. Sporadically, i'm working or better say thinking about an enhanced version of lnpd, but i think this doesn't make much (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Which terminal on Linux? plus random thoughts.
|
|
(...) Umm, I mean cover the tower and the RCX with a box.... :-) (...) No, Ernst's idea has a preamble byte for the transfer, and then the RCX grabs all of the chars and sums them. If the sum is wrong, then it NAKs the packet and the host sends it (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Which terminal on Linux? plus random thoughts.
|
|
(...) I missed that. What do you mean by simply covered. (...) No surprise there. I implemented XMODEM a long time ago on a spectrometer. I don't remember the details but obviously it stayed with me. Besides all protocols tend to look the same at (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Which terminal on Linux? plus random thoughts.
|
|
(...) I have beta quality Tcl code that sends an SRECORD firmware imge up to the RCX (fast or slow) and has basic terminal capabilities. It also strips comments and whitespace out of files as they are uploaded to reduce the time. I'd like to put a (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Which terminal on Linux? plus random thoughts.
|
|
I'm interested in other people's experience with various terminal emulators on Linux. I've been using minicom with indifferent results, probably because it doesn't support delays between lines which possibly overruns pbforth's serial input. minicom (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: make error in Linux build for LegOS 0.2.4
|
|
(...) This was one of the first things that I tried but it complained about other tools it couldn't find. It's been a while but I think it had pass1 in the name. Nothing in my bin directory seemed to match. Frankly I stopped working on it since I (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: make error in Linux build for LegOS 0.2.4
|
|
Steve morris <smorris@nexen.com> wrote in message news:390EC1B5.416273...xen.com... (...) c++.cpp. The (...) I must have an (...) the cross tools. (...) Try changing the references from <h8...>g++ to <h8...>gpp. Rossz (24 years ago, 4-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Alternatives for NQC Event Support
|
|
(...) I'm sorry its been taking so long. I was right in the middle of an overhaul to the NQC code generation classes when RCX 2.0 firmware was posted. This meant I had to finish the re-design before moving onto the simpler matter of an RCX 2.0 API. (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.nqc)
|
| |
| | RE: sensor questions plus
|
|
(...) The ROM stuff is documented in Kekoa Proudfoot's internals document, see (URL) for all the details. The RCX interface words in pbForth call into the ROM... (...) It actually *processes* the results of a sensor read by the OCIA interrupt (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.pbforth)
|
