 | | 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)
|
| |
| | 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)
|
