 | | More RCX's controled by one tower ?
|
|
Heya all ! Sorry if this was discused before but is it possible to control or program for example two RCX bricks with one tower from one PC so they work indifferently from eachothers in ONE model ? - Thanx ! - Rene (23 years ago, 18-Jan-02, to lugnet.robotics.rcx, lugnet.robotics)
|
| |
| | Re: thread class for legOS
|
|
(...) IRC, every method in C++ has an implicit parameter wich is the object itself; that's why you can't cast it. Try the following (does someone have a nicer solution?): Put runWrapper() outside the class: int runWrapper(int, char **th) { (...) (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | thread class for legOS
|
|
I write a Thread class for LegOs with a simple interface like in Java or CommonC++. I'm using LegOs 0.2.4. Below are my work till yet. The problem is in the Method Start(). The line is marked with !!. The error message is at the end of the file. I (...) (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Routing daemon with tcp/ip for RCX/legOS, Cybermaster/NQC
|
|
"Freddy" <mail-nowak@web.de> schrieb im Newsbeitrag news:GpzyB6.Kpt@lugnet.com... (...) A C++ class to build client application without knowing the LNPoI protocol is available for Windows and Linux now. (URL) (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Several questions
|
|
Dear Mindstormers, For months I didn't find the time to do some work with my Mindstorms equipment. So some things have changed and also new products came onto the market. I have just started work with Mindstorms again and have some (...) (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: threads - bug in the firmware?
|
|
(...) I would strongly suggest changing this to while(1) msleep(bignumber);. Otherwise you're hogging the processor doing nothing important, which could do bad things to any compute-intensive tasks you may have going. It'll also use slightly less (...) (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: threads - bug in the firmware?
|
|
Hi Ross (...) you (...) What are the advantages and disadvantages of this method as opposed to the one I used? mike (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: threads - bug in the firmware?
|
|
(...) Note also since bumper_task() is an infinite loop, and you never use pid1, you could save one thread by doing this: int main(int argc, char *argv[]) { pid2 = execi (&left_task, 0, NULL, PRIO_NORMAL+2, DEFAULT_STACK_SIZE); pid3 = execi (...) (23 years ago, 17-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: threads - bug in the firmware?
|
|
;-) That worked a treat, thanks Michael. (thanks for the other little corrections in the code too). mike (...) Mike, (...) your subroutines and then you leave main()! Leaving main means (...) memory is freed. The following will do the job: (...) (...) (23 years ago, 17-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
