 | | 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)
|
| |
| | Re: multiplexor and legOS
|
|
(...) Thanks, I'd suspected that msleep might not be very accurate but never considered that it's true granularity could be so large. I did a quick test with my current configuration and when I asked msleep to sleep for 12ms it slept for 20. This (...) (23 years ago, 4-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: true tcp/ip on the RCX
|
|
(...) The C64 server survived the "Slashdot attack" without problems, even though it served tenths of thousands of pages over a period of only a few hours. Since it is configured to allow only 10 simultaneous connections, it could more or less serve (...) (23 years ago, 4-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
(...) Don't ask me for a cite, but I seem to remember something about msleep only having 20ms granularity. If that's the case, your msleep(10) is either not sleeping at all or is sleeping 20ms, either one of which could cause problems. I'd suggest (...) (23 years ago, 4-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
well anyone who looked at the code I attached may have notcied that I had one of the msleeps commented out. Oops, with this now uncommented I at least see the second and third light sensors pulse on, but only for an extremely short time. Suring the (...) (23 years ago, 3-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | multiplexor and legOS
|
|
Does anyone have expierence using the active multiplexor sold by www.mindsensors.com with legOS? If you are not farmiluar with this multiplexor it is really cool as it lets you multiplex three active sensors on one port. You tell the mux which "sub" (...) (23 years ago, 2-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: "Local Positioning System" for lego-vehicles with mice
|
|
Hi, if you are interested : sources now available (URL) (23 years ago, 2-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | LNP + USB under windows
|
|
Hi, has anybody experience in communicating with the RCX over USB (Windows)? So far I managed to get legOS working with the USB-patch from Jin Sato; then I tried to use winLNP, but it didn't work (the light in the tower is not blinking) Now I'm (...) (23 years ago, 1-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: true tcp/ip on the RCX
|
|
Ok, the website is up at: (URL) Christ (23 years ago, 2-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: true tcp/ip on the RCX
|
|
Cool stuff, congrats on the Slashdot recognition. Hope the "Slashdot Effect" didn't totally cripple your server. Wondering if you or Olaf could make the LegOS code available for all to see, just wondering how it was all done for educational purposes (...) (23 years ago, 1-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: true tcp/ip on the RCX
|
|
(...) [...] (...) A few days ago, Olaf sent me his legOS TCP/IP code which I have been running a few days, so I probably have the world's second TCP/IP-enabled Lego brick in my office :-) ! I was also able to squeeze in a simple web server, a few (...) (23 years ago, 1-Feb-02, to lugnet.robotics.rcx.legos)
|
