 | | 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..... (...) (25 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 (...) (25 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 (...) (25 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 (...) (25 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 (...) (25 years ago, 26-Jan-01, to lugnet.robotics.rcx.legos)
|
