To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcxOpen lugnet.robotics.rcx in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / *875 (-10)
  0.2.0a patch
 
Hello, apparently I introduced a glitch when adding last-minute support for non-patched standard egcs. This and a broken symlink in the archive prevented dllback from compiling on the host. A patched version of legOS is available on (URL) for the (...) (25 years ago, 19-Oct-99, to lugnet.robotics.rcx.legos)
 
  RCX-enhanced egcs
 
Hello, I just posted the final RCX interrupt handling patch for egcs. There is no need for wrappers anymore. Interrupt handlers can be declared like this now: void handler() __attribute__((rcx_interrupt)); void handler() { // do stuff } For a leaf (...) (25 years ago, 19-Oct-99, to lugnet.robotics.rcx.legos)
 
  pbforth questions
 
My 15 year old son is into legos big time. He has asked for the Lego robot package. I developed in Forth many years ago and I am just getting back into it with Forth Inc.'s SwiftForth for Windows. I have enjoyed messing about with it but what I am (...) (25 years ago, 19-Oct-99, to lugnet.robotics.rcx.pbforth)
 
  Sharing variables and using expressions (was Re: NQC 2.0 and some math questions
 
I have discovered a somewhat non-intuitive feature of NQC (in my version, at least, which is pre-2.0) The statement: var = (20 * var) / 21; gets compiled into the following: MUL var, 20 ; var = var * 20 DIV var, 21 ; var = var / 21 rather than the (...) (25 years ago, 19-Oct-99, to lugnet.robotics.rcx.nqc)
 
  RE: RCX Firmware and SP
 
(...) Unfortunately, yes. The current version of pbFORTH allocates a 256 byte stack, but it's JUST above a 256 byte boundary. When you run the test code, everything works, but if your stack depth is around 12 and you run SENSOR_READ, it allocates (...) (25 years ago, 19-Oct-99, to lugnet.robotics.rcx.pbforth)
 
  Re: RCX Firmware and SP
 
(...) [...] Hi Ralph, Could you please explain more about consequences for pbFORTH user? As far as I can see, pbFORTH uses fixed 256-byte stack - does it mean that pbFORTH suffers from this problem too? Thanks Sergey Udovenko (25 years ago, 19-Oct-99, to lugnet.robotics.rcx.pbforth)
 
  Re: Announce: NQCIPC -- simple IPC for Not Quite C programs
 
[forwarding a copy to the .rcx.nqc newsgroup... --Todd] (...) (25 years ago, 19-Oct-99, to lugnet.robotics.rcx.nqc)
 
  RE: AI and even more exiciting stuff
 
Richard, I hope you don't mind me using your quote... <snipped discussion of junior programmer and temp sensor application) (...) Yesss! I am going to tie the moon mission into my panel presentation at Mindfest. Here's a source I used on the Apollo (...) (25 years ago, 18-Oct-99, to lugnet.robotics.rcx.pbforth, lugnet.robotics)
 
  Re: Annoying Journalist's Request
 
To the list: this morning is a break for me, so I'm going to use it to type this out. Hope no one minds that it gets sent to the "annoying journalist" as well. Here at Duke, we are teaching a class with the mindstorms. Recently, we completed a class (...) (25 years ago, 18-Oct-99, to lugnet.robotics, lugnet.robotics.rcx.legos)
 
  RE: AI and even more exiciting stuff
 
(...) OK, time to get out the soapbox. If you are trying to teach AI, and are using floating point math, then you probably have really fast computers with floating point processors that are sometimes quicker than equivalent fixed point calcs...... I (...) (25 years ago, 18-Oct-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)


Next Page:  5 more | 10 more | 20 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR