To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.roboticsOpen lugnet.robotics in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / *28744 (-10)
  Re: problem with floating point numbers (legOS 0.2.5)
 
(...) Actually, the problem seems to come with gcc 2.96 (recent installation of Red Hat 7.1). My program runs without any problem on an other PC with gcc 2.95. I have forced the system to use egcs, re-built everything, and now it works fine. (25 years ago, 29-May-01, to lugnet.robotics.rcx.legos)
 
  RE: Custom Firmware, IR Problems, and Dead RCXs
 
(...) <snip> (...) <snipped more> Well, no. The RCX receiver is a standard IR unit tuned to the carrier frequency. when I look a the signal on my scope, I get a nice square-shaped wave that is the same as the data byte (with start and stop bits) (...) (25 years ago, 29-May-01, to lugnet.robotics)
 
  RE: Custom Firmware, IR Problems, and Dead RCXs (long)
 
(...) The use of alternative firmware such as pbForth, legOS and leJOS usually requires frequent upload/download cycles, and may use long communications periods. (...) I agree on this point, but that will affect the low power range more as well. (...) (25 years ago, 29-May-01, to lugnet.robotics)
 
  Library
 
I have written a tiny messaging package for lejos. What I'm having trouble with is where to put it and it's class files so that I can use it in my lejos programs just like one of the lejos classes/packages. Currently I have to place a copy of my (...) (25 years ago, 29-May-01, to lugnet.robotics.rcx)
 
  Re: lnp rcx hostaddress [and a summer legOS release?]
 
I'm very open, to feedback to tell me why I'm nuts and/or to help in making sure I don't break anything important to current legOS users. I certainly won't change anything serious without announcing and discussing it here. Luis (...) (25 years ago, 29-May-01, to lugnet.robotics.rcx.legos)
 
  RE: Custom Firmware, IR Problems, and Dead RCXs
 
(...) Ummm, that doesn't make sense. You know where the midpoint is by knowing the baud rate, and hence the bit width. The only time you need to sample at the beginning of the bit time is to look for a start bit. This is all very basic asynchronous (...) (25 years ago, 29-May-01, to lugnet.robotics)
 
  Re: download .s19 problem
 
the target of your code is probably the zero page of RAM, where the downloader bootstrap routine lives. so as your code is being downloaded, you're over-writing the hc11-ram-based dl comms code and the host side ultimately fails. fred (...) (25 years ago, 29-May-01, to lugnet.robotics.handyboard)
 
  Re: Custom Firmware, IR Problems, and Dead RCXs
 
(...) Actually, it's the computer itself that determines the duty cycle. This does mean that you could change the duty cycle, but you should be aware that it would be at the expense of noise immunity and would require a higher sampling rate from the (...) (25 years ago, 29-May-01, to lugnet.robotics)
 
  Re: Custom Firmware, IR Problems, and Dead RCXs (long)
 
(...) For what it's worth, it's not actually that bad. I don't know the specs on the NPN transistor, but I suspect 1.14A would kill it almost instantaneously. One important factor you've left out of this equation is the 9V battery itself. We often (...) (25 years ago, 29-May-01, to lugnet.robotics)
 
  Re: Custom Firmware, IR Problems, and Dead RCXs (long)
 
I'm hard pressed to understand why one would need to continually transmit from either the RCX or the tower? Data logging comes to mind, but there aren't many cases where there is a need for this. Listening can, of course, be done continously. The (...) (25 years ago, 29-May-01, to lugnet.robotics)

Next Page:  5 more | 10 more | 20 more
Redisplay Messages:  All | Compact

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