|
 | | lnp communication question
|
| Hi! When using lnp_integrity_write(&data, length), what is the length argument used for? The data can only be one byte long if I understand it correctly. Can I use the length argument to send an additional byte of information? Is there anyway I can (...) (24 years ago, 14-May-00, to lugnet.robotics.rcx.legos)
| |
|  
long
(score: 0.239)
|
|
| | Re: Standard extension suggestions
|
| (...) It is hard for me to tell. It is not hard for me but I am a programmer with many years under his belt. However forth seems idealy suited for someone getting started. It is a very interactive environment which encourages experimentation. Let me (...) (24 years ago, 8-May-00, to lugnet.robotics.rcx.pbforth)
| |
|
long
(score: 0.238)
|
|
| | 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)
| |
|
long
(score: 0.238)
|
|
| |
|
long
(score: 0.238)
|
|
| | 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)
| |
|
long
(score: 0.238)
|
|
| | Re: lnptest gives collision errors. Sigh...
|
| (...) I guess there is no hope. I found a long thread here with someone else who had a collision problem . I applied the patch to transmitter.c mentioned in that thread with the same result. I downloaded lnpd.static from arthurdent. Same result. I (...) (24 years ago, 27-Apr-00, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 0.237)
|
|
| |
|
long
(score: 0.236)
|
|
| | Re: Thought on pbForth
|
| Ralph Hempel writes: > > I've been doing embedded realtime software for > > over 20 years. > > Sounds like you've got lots of expreince with different > paradigms, which is one of the most important aspects > of being a good designer.... My (...) (24 years ago, 20-Apr-00, to lugnet.robotics.rcx.pbforth)
| |
|
long
(score: 0.236)
|
|
| | Re: Thought on pbForth
|
| I am new to this group so please forgive this reply to an old thread. I've been doing embedded realtime software for over 20 years. A small amount of that has been using FORTH. The question is what does FORTH add to robotics software development? To (...) (24 years ago, 19-Apr-00, to lugnet.robotics.rcx.pbforth)
| |
|
long
(score: 0.235)
|
|
| | Lego Laser
|
| Using pointers (pun) from a previous post, I have been building a laser for my robots. I used a miniature laser pointer from Sam Goody which was only $10. The hardest part so far was chopping up the pointer to get out the guts. It turned into a (...) (25 years ago, 11-Apr-00, to lugnet.robotics.rcx)
| |
|
long
(score: 0.234)
|
|
| | Re: NQC and RIS2.0 Firmware
|
| (...) I found the problem... When verifying the checksum, the ROM scans [8000, cc00). Since it zeros out this area initially, this would indeed reflect the checksum of the firmware, provided it is less than 4400 bytes long (in hex). NQC sums the (...) (25 years ago, 2-Apr-00, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 0.233)
|
|
| | Re: NQC and RIS2.0 Firmware
|
| (...) I've been looking at that for most of today. The 2489 is basically the last packet to go to the RCX, and the error is a "checksum error" coming back from the RCX. As far as I can tell, nqc breaks with any firmware file bigger than 20K (...) (25 years ago, 2-Apr-00, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 0.233)
|
|
| | Re: NQC on Linux dilema...
|
| (...) OK, here it goes: (I am in root) Output_Start: Downloading program: Tx: 55 ff 00 10 ef 10 ef Rx: 55 ff 00 10 ef 10 10 ef 55 Tx: 55 ff 00 10 ef 10 ef Rx: ff 00 ef 10 ef 10 ff ae ed 00 10 ef 10 ef 55 ff 00 ef 10 ef 10 Tx: 55 ff 00 50 af 50 af (...) (25 years ago, 1-Apr-00, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 0.233)
|
|
| | Re: NQC on Linux dilema...
|
| (...) Ok, here it is: It just sits there, after sending about 5 lines of hex code to the RCX with that -v option. it will not send any more code after that, no matter how long you wait. I have not such thing as a PSerial_unix.cpp file does not (...) (25 years ago, 1-Apr-00, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 0.233)
|
|
| | Re: printing on more than one page
|
| The icons in Robolab have the program logic flow from left to right, with modifiers below each icon. This basic structure typically creates programs that are very wide, but not very long. If Robolab were changed so the icons would have program flow (...) (25 years ago, 27-Mar-00, to lugnet.robotics.rcx.robolab)
| |
|
long
(score: 0.233)
|
|
| | When the OS makes the difference
|
| Yesterday, Sunday 26th March, we had our 4th Italian Legofest. This time our traditional robotic contest was about line following, and 10 peopled compared their ideas, their knowledge and their ability running their robots for maximum speed on a 7m (...) (25 years ago, 27-Mar-00, to lugnet.robotics, lugnet.robotics.rcx.legos) !
| |
|
long
(score: 0.233)
|
|
| | Re: Battery life question
|
| (...) I measured the RCX consumes about 33mA in ROM or Lego Firmware, around 26.5mA under LegOS (due to the sleep instruction in the idle task), and it will use 0.034mA when turned off. No matter how long you sleep in your task, the RCX will consume (...) (25 years ago, 26-Mar-00, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 0.233)
|
|
| |
|
long
(score: 0.232)
|
|
| |
|
long
(score: 0.232)
|
|
| | NQC/RcxCC
|
| Thanks to everyone who suggested that I use NQC for programming, I now have a copy of RcxCC installed, and programming in it is easier than in the lego graphic interface (as long as you remember the ;'s) The coal unloader program is done (it took (...) (25 years ago, 18-Mar-00, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 0.231)
|
