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