|
 | | threads
|
| Hi, I'm struggling to get threads working (in a simple motor speed matching program), the code just keeps hanging up. I've isolated the problem to when I restart the threads after killing them if a bumper is hit in the bumper_task() function. The (...) (23 years ago, 14-Jan-02, to lugnet.robotics.rcx.legos)
| |
|  
event
(score: 0.875)
|
|
| | 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)
| |
|
event
(score: 0.875)
|
|
| | Re: threads - bug in the firmware?
|
| Hi again I have now totally stripped down my code to a minimum and I am still having problems with the code hanging up. I can see nowhere where there can be a fault. I am a long way from being an expert, but is it possible there is a bug in the (...) (23 years ago, 16-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.875)
|
|
| | Re: threads - bug in the firmware?
|
| Hi Mike, your problem is not because of an error in legOS. But what you do is that you start your subroutines and then you leave main()! Leaving main means that all your allocated memory is freed. The following will do the job: ---...--- cut here (...) (23 years ago, 17-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.875)
|
|
| |
|
event
(score: 0.874)
|
|
| |
|
event
(score: 0.874)
|
|
| | This week in Robotics:
|
| THIS WEEK IN ROBOTICS: Here is a calendar of events coming up this week - February 2rd - 9th, 2002. Details are on our web site at (URL) you know of an upcoming event of have a robotics club or organization, please drop us a note at (...) (23 years ago, 3-Feb-02, to lugnet.robotics)
| |
|
event
(score: 0.874)
|
|
| | Micromouse Robotic Competition, Could RCX do this?
|
| I recently stumbled across a reference to the Micromouse Robotics competition and thought others in the group might find it interesting. It looks like something that would be [barely] achieveable with a Mindstorms implementation. APEC [Applied Power (...) (23 years ago, 1-Feb-02, to lugnet.robotics)
| |
|
event
(score: 0.873)
|
|
| |
|
event
(score: 0.873)
|
|
| | 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)
| |
|
event
(score: 0.873)
|
|
| |
|
event
(score: 0.873)
|
|
| |
|
event
(score: 0.872)
|
|
| |
|
event
(score: 0.871)
|
|
| |
|
event
(score: 0.871)
|
|
| |
|
event
(score: 0.870)
|
|
| | Re: New Book - Core Lego Mindstorms
|
| I assume with the offfical 1.4 release? I have had several problems with the offical release including stability problems, incompatible code (some wierd 1.2 stuff), slow performance, and hanging event threads (they never return from calling the (...) (23 years ago, 16-Mar-02, to lugnet.robotics)
| |
|
event
(score: 0.870)
|
|
| | Re: Stair Climber 4x4
|
| We (LEGO Robotics Group of Ann Arbor) recently had our Stair Climbing event here in Ann Arbor. The 3 bots that competed all had very similar designs to the item you link to. We competed on a 5 step stair case that had a total rise and total run of (...) (23 years ago, 14-Mar-02, to lugnet.robotics)
| |
|
event
(score: 0.870)
|
|
| |
|
event
(score: 0.868)
|
|
| | Re: RFC: smaller task scheduler
|
| "Stephen M Moraco" <stephen_moraco@agilent.com> wrote in message news:GtKIM4.Gws@lugnet.com... (...) <snip> (...) Sounds good. Now, who would like to provide a second opinion? BTW, as far as intended purpose of the task scheduler... I can see how (...) (23 years ago, 26-Mar-02, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.868)
|
|
| |
|
event
(score: 0.868)
|
