 | | Re: multiplexor and legOS
|
|
(...) Sort of. Try Sourceforge ((URL) is on the "Patches" page (just click on the "Submit New" link). Great Job!! I am looking forward to be able to use the multiplexer finally! I've successfully added the "priority interrupt" patch to legOS 0.2.5 (...) (23 years ago, 10-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RFC: Creation of Version 0.2.6
|
|
(...) That was not the cause for my RFC. You do a wonderful job! And legOS does it as well. No real overwhelming cause for doing a new release. (...) Well, not really. I wold favour other solutions first: - if you can go on with legOS-maintainance - (...) (23 years ago, 10-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | linux USB driver.
|
|
For anyone who want's it, I have a linux USB driver for the lego IR tower. If anyone is interested, the tar ball of driver and pathces to nqc and legOS can be found at: (URL) am hoping to reconsile my driver with the version that was being worked (...) (23 years ago, 10-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
I'm happy to report that after writing the multiplexor driver at the kernel level it's working! I'll post a patch soon once I've got it cleaned up a little bit. It looks like the problem was with the legOS power/read cycle in ds_handler. Once I took (...) (23 years ago, 10-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RFC: Creation of Version 0.2.6
|
|
It appears that the time has come for 0.2.6; it has been more than 18 months now since 0.2.5. I still lurk here, but my work with Free Software has consumed my time- even when I'm not paid, I'm pretty much a slave to bugzilla.gnome.org and (...) (23 years ago, 9-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | RFC: Creation of Version 0.2.6
|
|
I think it would be a very good idea to incorporate the prio-patch to legOS. But there seem to be a lot of patches and enhancements for 0.2.5. Personally, I use the remote control patch from Zhenrong Zang. And there is the TCP/IP system... Any more (...) (23 years ago, 9-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Priority Interrupt Patch and legOS-0.2.5
|
|
We are gathered here to witness the union of priointerrupt-patch.diff and legOS-0.2.5. If anyone has just cause why these two should not be wed may they speak now or forever hold their peace. Robert Templeton (23 years ago, 8-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
Still no luck in getting the mux working properly. I tried making use of the code for turning sensors on and off but later realized that the ds_handler code would still be turning the sensor off as part of its normal operation. I think I'm going to (...) (23 years ago, 7-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Real time operating system resources
|
|
Now that my interest has been piqued by the multiplexer problem (and sensing problem in general), what would some of you hardened embedded/real-time system veterans recommend for reading on the subject. Two books that I've found at Amazon.com are (...) (23 years ago, 6-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
(...) I'm just checking this thing out. You can look at: (URL) more information. Unfortunately, I got the .ps description file but not the source code patch file. A mail asking for it is on it's way ;) Mike (23 years ago, 5-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
(...) Actually, something like this has been documented and done by Pedersen, Christensen, Rasmussen ("Prioritized Interrupts in LegOS"). They actually document the problem of sensor misses related to task management, significantly reducing the (...) (23 years ago, 5-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
(...) Most people's legOS kernels will be compiled so msleep uses wait_event. I haven't looked at the code, but my understanding of how wait_event works is that whenever that thread becomes eligible to execute, your even function is called. (...) (23 years ago, 5-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
Try the following code fragments. [Change to fixed spacing font so that it reads easily.] You should be able to find what you need. "Mark Falco" <> wrote in message news:Gr1MBL.Dop@lugnet.com... (...) <<..snip..>> (...) These are code fragment for (...) (23 years ago, 5-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
Ok, my last port didn't make much sense let me try that again. for an active sensor ds_handler will periodically power the sensor off to read the value. The standard firmware does this to but at a different interval. I'm wondering if this is part of (...) (23 years ago, 5-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
Since I'm now fairly sure that i've got the timing taken care of I'm wondering if the power cycling that ds_handler does is somehow causing the problem? I thought I might take control of this stuff in my test code. I assume if I set the sensor for (...) (23 years ago, 5-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
(...) It looks like the semaphore task_sm should prevent another task from being scheduled if I hold it for the length of the train. I've now tried this as well as incresing the timeslice to 100ms. It looks better but still is not consistent. Since (...) (23 years ago, 5-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
(...) Not bad. But as you say, still vulnerable to the task switching problem. (...) Instead of resorting to that, maybe there is a way to freeze task switching during critical operations. When I owned and programmed the AmigaOS (don't laugh :), (...) (23 years ago, 5-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
#include <sys/time.h> void systime_set_timeslice (unsigned char slice); include/sys/time.h:43-45: #ifdef CONF_TM #define TM_DEFAULT_SLICE 20 file://!< default multitasking timeslice #endif hope that helps, Albert "Michael J Ash" (...) (23 years ago, 4-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
(...) I agree about the cause for the msleep granularity, I'd seen the same stuff in tm and assumed that would cause the problem. Sorry my last note was a little unclear, I tried msleep and delay but am now using my own function which seems to (...) (23 years ago, 4-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
(...) I don't know about this 20ms granularity and how delay() is going to be any better. Here's the code for each function: //! delay execution allowing other tasks to run. /*! \param msec sleep duration in milliseconds \return number of (...) (23 years ago, 4-Feb-02, to lugnet.robotics.rcx.legos)
|
