 | | bug fixes
|
|
Hi. I have been playing with legOS (the current version in CVS at sourceforge), and have found a few bugs in it. Several of these are filed at the sourceforge site, so I'm wondering what the protocol is for getting these fixed. I can submit patches (...) (24 years ago, 5-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | legOS 0.2.5 available in Debian GNU/Linux distribution
|
|
legOS and the required cross compilers for C/C++ are immediately available for Debian GNU/Linux from the Debian mirrors. For a quick link to the package-description-page (you can download from here too) see: (URL) all means enjoy! If you experience (...) (24 years ago, 4-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | legOS IDE
|
|
Something slightly offtopic: For some time I was searching for a usable IDE edit / compile system I wanted to use for the writing legOS programs. What I found is an editor called cooledit (can be found at cooledit.sourceforge.net). Cooledit has all (...) (24 years ago, 2-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS lcd management and thoughts on velocities
|
|
Hello jochen, (...) Thank you for your precision about your velocity handler For now, unfortunaly my the hard disk does not boot any more, and, fortunatly, my wife gave birth to a girl on wednesday! So I'll test all those nice handlers in a few (...) (24 years ago, 2-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | lnp..again :)
|
|
hi everybody. im trying to figgure out how to display everything that is sent with the LNP protocol from one rcx to another. That is, im not only interested in the data im sending, but also the adressing overhead and whatever else is sent..... (...) (24 years ago, 1-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | LNP checksum optimizations
|
|
In a previous post I said that some optimizations can be made in LNP. Now I have the patch ready and uploaded it on sourceforge. Sadly I made it against a custom version of the kernel, so it may need a manual intervention to apply (fuzzyness (...) (24 years ago, 31-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS lcd management and thoughts on velocities
|
|
(...) The timeout is really "expected time till next rotation tick + 50 %". And the velocity will not drop to 0, because my code assumes, a new rotation could happen any moment. If you check for speed < 7 ticks/sec (or 142 msec/tick) you should get (...) (24 years ago, 29-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS lcd management and thoughts on velocities
|
|
Thank you Jochen for your answer. If I well understand the ds_rotation_handler code, the timeout is set to 1 second. So the velocity may drop to zero 1 second after wheels really stop. In the specific case of my robot (I call it R2D1), this will be (...) (24 years ago, 27-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS lcd management and thoughts on velocities
|
|
(...) Yes, I have written that support. First you have to enable it, by removing the comments from the line in legOS/boot/config.h. Then recompile the kernel and all apps. After you have programmed the rotation sensor in the usual way you can read (...) (24 years ago, 26-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: sleep efficientcy
|
|
(...) value (...) There are two issues: 1 do you want to do anything while waiting, 2 how quick do you want to respond to the event. In both cases using an event is better. You can do something else until the event happens (synchronization issuses (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.legos)
|
