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 / *2580 (-20)
  Re: Very strange problems
 
(...) Redundancy is good :) (...) Good. It's generally solid, but can cause some issues from time to time. <snip lots of monkey talk :) > (...) Distance of movement or consistency (i.e. always forward) or both for fitness? Sounds really cool. Good (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Re: Very strange problems
 
(...) We have not done anything to ensure that whatever is transmitted is received correctly (i.e. without errors). What we have done is a build a system which will work even if one (or several) of the RCXs are temporarily blocked for some reason. (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Re: Very strange problems
 
(...) Argh. I was getting emulegos (which I was pretty familiar with) and legosim (which I though was C, not Java) confused. I'm afraid neither of them would be too easy to port to 0.2.x :( (...) Please make sure to share this with us! IR continues (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Re: Very strange problems
 
(...) I was afraid so. (...) We haven't reached the GA part yet. Right now the idea is to work out a communication protocol and then send a information back and fourth. And since the RCXs locked up we thought that there must be something wrong in (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Re: Very strange problems
 
(...) IIRC, it is 0.1.7, which used a completely different setup for the IR communication. (...) Unfortunately, no. (...) You mean, unmodified? No, I don't think. I've seen lots of code that worked, and then got "simplified" and then stopped (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Re: Very strange problems
 
(...) It seems that emulegos should be able to handle IR. However, it does not use the lnp-functions that I use, so I presume it is designed to work with an earlier version of legOS. Were earlier versions of legOS (I use version 0.2.3) less likely (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Re: Very strange problems
 
(...) I will hopefully clean up and release some of it by Wednesday. (...) I'm not sure- I don't think so, though. Someone else here may be able to answer that much better than I can. Luis ---...--- "Going to California with an aching in my heart. (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Re: Very strange problems
 
(...) Is this neural network code made public? I have emulegos, but I havn't much more than started it up. Do you know if it can handle IR-communication between several RCXs? Tobias (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Re: Very strange problems
 
(...) Yes. We ran into similar problems when writing neural network code. Persist- you can write really cool stuff on legOS- we did. Also, emulegos (which is still around somewhere, though I'm not sure if anyone has ported it to 0.2.x) would (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Re: Very strange problems
 
(...) That is really bad news. Since we are writing a genetic programming system with six RCXs involved that communicate with each other, the programs tend to get pretty long. Often things fail. Right now I have the problem that if I save a program (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Re: Very strange problems
 
(...) As far as I can tell, legOS has some really strange bugs. I've learned to take it for granted that some programs (without warning) will just crash and lock up the machine. This is unfortunate, but I've never found a pattern to them so there is (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Re: lnp communication question
 
(...) lnp does a checksum and throws away bad data. I think it is a 1 byte checksum so 1 out of 256 errors gets through anyway. There is no retry so timeout and retry has to be handled by some higher level code. (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  Very strange problems
 
Hi! I am experiencing some very strange problems when programming my RCX. Sometimes (too often) the RCX just locks up when I run my program and I have to remove the batteries and reload the firmware. I have now found that very small changes in my (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
 
  RE: Help with Terminal Emulator
 
(...) I have run into this too, Jerry. A few especially bothersome noise sources include video cameras, security systems, and remote controls. You might consider covering the RCX and tower with a box or towel... I'm glad the terminal emulator works (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.pbforth)
 
  Re: Help with Terminal Emulator
 
I think my problem is bounce back noise. I doubled checked the port settings, started with a fresh set of batteries, made sure I had a clear buffer, but what made the difference is where I am doing my programming. I'm working off of a laptop, and (...) (24 years ago, 20-May-00, to lugnet.robotics.rcx.pbforth)
 
  arbitrary motor code
 
Did anyone ever write the wrapper to allow motor_dir(motor_label x, MotorDirection dir) or some such? There was a variant of it way, way back (0.1.5?) but I don't see anything like it in the current CVS code. Anyone? Anyone? -Luis ---...--- "Going (...) (24 years ago, 20-May-00, to lugnet.robotics.rcx.legos)
 
  Re: lnp communication question
 
(...) Ok, this brings up more questions :). I have never had any problems with errors when sending messages. Sometimes the message is not recieved but when it is, I have never seen any errors in the transmission. Am I missing your point? Second, (...) (24 years ago, 20-May-00, to lugnet.robotics.rcx.legos)
 
  Re: IR communication PC <-> brick with NQC
 
(...) The RCX uses a special packet protocol which involes a lot of binary (non-ASCII) bytes, so controlling it with Hyperterminal won't work very well. Your best bet is to either write your own code to send the packets of the serial port or just (...) (24 years ago, 20-May-00, to lugnet.robotics.rcx.nqc)
 
  Re: Is there a compatible h8 assembler for forth words?
 
(...) A good rule. I just know I'm going to need fast so I am planning ahead. Somehow I'm usually at the bleeding edge of trying to squeeze everything possible out of limited hardware. I originally learned my Forth on a 68000 (Mac Forth on the (...) (24 years ago, 20-May-00, to lugnet.robotics.rcx.pbforth)
 
  RE: Is there a compatible h8 assembler for forth words?
 
(...) No there is not. That being said, it's pretty easy to write one...if you have the time. I fiddled around with it a bit and then gave up since the GNU tools worked pretty quick. It was strictly a time/value exchange. From bitter experience, (...) (24 years ago, 19-May-00, to 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