 | | Re: Legos 0.2.5 and Win2k
|
|
If you can get in touch with Paolo directly, I believe he said that he had 0.2.5 running under Cygwin 1.0. If you can get his compiler packages for that, the newer Cygwin may help with W2K. And of course you can always go to www.redhat.com for a (...) (24 years ago, 6-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | Legos 0.2.5 and Win2k
|
|
Has anyone had any luck getting legos 0.2.5 to work under Windows 2000, I'm running 0.2.4 quite cheerfully under cygwin b20 , but 0.2.5 refuses to compile...and in the new cygwin legos 0.2.4 refuses...argg if only I wasn't so dumb :) - ciaran (24 years ago, 6-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | VLL in legOS 0.2.6?
|
|
Why not add the VLL stuff to 0.2.6 release? The post of the Ben Jackson is in (URL) (24 years ago, 6-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: bug fixes
|
|
And of course Paolo can take care of stuff too... I haven't heard from him in a while though either, so I have no idea how much time he has... Paolo? Out there? <waves> hi! ;) Luis (...) (24 years ago, 6-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: bug fixes
|
|
(...) Well, if we collect enough patches from folks then feel free to coordinate a release. It isn't like there are tons of bugs or new functionality floating around, but there were clearly a whole lot of niggling small bugs from 0.2.5, so maybe if (...) (24 years ago, 6-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: bug fixes
|
|
I would have no objections to taking over some the responsibilities, especially those related to releasing versions. It's what I do best, anyway. I'm sure there is someone more qualified with the administrator aspects, but if no one else volunteers, (...) (24 years ago, 6-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LEGO remote and LNP (legOS 0.2.4)
|
|
Luis, I can do a quick HOWTO (though it'll only cover Linux) & post this patch. I think it'd be useful, anyway. It applies cleanly to 0.2.5 as well. Regards, ROSCO Luis Villa <liv@duke.edu> wrote in message news:Pine.GSO.4.10.1...uke.edu... (...) (...) (24 years ago, 6-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP and Lego Remote
|
|
Hi Paolo, I know this is a kind of old message, but I was just wondering what's happening in this direction? I'm currently using Chris Arquiza's patch (which works fine against 0.2.5) but wondering whether there's something new & improved around the (...) (24 years ago, 6-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: bug fixes
|
|
Hey, all. I'm sorry I've been neglecting stuff (Stephen and Rossz, that mainly means you guys :| I've had a combination of a crud-load of work and some serious personal troubles to deal with. Unfortunately, I'll be mainly out of the loop until late (...) (24 years ago, 6-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: bug fixes
|
|
(...) Luis Villa is the person to grant access. I haven't seen him around recently. I'm sure he'll get back to you when he can. Rossz (24 years ago, 6-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | bug fixes
|
|
Hi. I have been playing with legOS (the current version in CVS at sourceforge), and have found a few bugs in it. Several of these are filed at the sourceforge site, so I'm wondering what the protocol is for getting these fixed. I can submit patches (...) (24 years ago, 5-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | legOS 0.2.5 available in Debian GNU/Linux distribution
|
|
legOS and the required cross compilers for C/C++ are immediately available for Debian GNU/Linux from the Debian mirrors. For a quick link to the package-description-page (you can download from here too) see: (URL) all means enjoy! If you experience (...) (24 years ago, 4-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | legOS IDE
|
|
Something slightly offtopic: For some time I was searching for a usable IDE edit / compile system I wanted to use for the writing legOS programs. What I found is an editor called cooledit (can be found at cooledit.sourceforge.net). Cooledit has all (...) (24 years ago, 2-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS lcd management and thoughts on velocities
|
|
Hello jochen, (...) Thank you for your precision about your velocity handler For now, unfortunaly my the hard disk does not boot any more, and, fortunatly, my wife gave birth to a girl on wednesday! So I'll test all those nice handlers in a few (...) (24 years ago, 2-Feb-01, to lugnet.robotics.rcx.legos)
|
| |
| | 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..... (...) (24 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 (...) (24 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 (...) (24 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 (...) (24 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 (...) (24 years ago, 26-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: sleep efficientcy
|
|
(...) value (...) There are two issues: 1 do you want to do anything while waiting, 2 how quick do you want to respond to the event. In both cases using an event is better. You can do something else until the event happens (synchronization issuses (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: sleep efficientcy
|
|
(...) value (...) Ross, I can't speak about efficiency - I dont know enogh about embedded programming, but I've had better results using wait_event. I've tried both msleep() and yield() in a loop, and just calling wait_event with a function that (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | sleep efficientcy
|
|
Hi again, i would like to know which is more efficient in code? having a while loop which is checking for a condition to be true and sleeping for an arbitary value while it is not, or using a wait_event statement passing a function pointer to a (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Parallel sensor problem
|
|
(...) That isn't the problem. I reversed the sensor on one RCX, and they both showed it as being constantly pressed, so that must be the wrong polarity. But I also tried moving it from input 2 to 3. Works fine. Same programs, everything, it works in (...) (24 years ago, 24-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.5 and LNP
|
|
(...) after (...) old (...) That's true. I've noticed it. I was speaking of PC implementation. (...) semaphore (...) in a (...) instruction (...) wait (...) of the (...) shouldn't (...) Ok, perfect. I vote for the semaphore implementation. I also (...) (24 years ago, 24-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: C++ OverHead
|
|
Hi, The answer here depends on your coding style. If you are using non-derived concrete classes, with simple member data and the default constructor/destructor, then it costs ~10-20 bytes/class. If you are using non-derived concrete classes, with (...) (24 years ago, 24-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Speed value interpretation?
|
|
In lugnet.robotics.rcx.legos, Rossz Vamos-Wentworth writes: ... (...) hmmm... did your wife figure out what vamos means... you might have to change that one too :-) sorry, but now I don't remember the question about the motor speed (24 years ago, 24-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Speed value interpretation?
|
|
(...) My birth name is actually Ross, but I changed it to Rossz when I married my Hungarian wife. In her language it means 'bad'. :) Rossz (24 years ago, 24-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: C++ OverHead
|
|
(...) Hi, unfortunately I am unable to answer your question, however I am very interested in what you are doing with GA. I recently recieved my RCX and have done GA work in the past as part of my schoolwork. I would love to try using some GAs with (...) (24 years ago, 24-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Parallel sensor problem
|
|
Bernardo Dal Seno <piu1759@cdc8g5.cdc.polimi.it> wrote in message news:87d7dd25ge.fsf@...o.bogus... (...) crane, and (...) RCX 2. (...) like: (...) Thanks. I'll try that. (...) happens (...) connected to (...) Nup. I disconnected the motor, but the (...) (24 years ago, 24-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Parallel sensor problem
|
|
(...) I don't know if this is your problem, but the input ports have polarity (one lead is connected to ground and the other to +5V through a resistor, if I remember correctly). Have you tried to change polarities? (...) Maybe the problem is not in (...) (24 years ago, 23-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.5 and LNP
|
|
(...) On the RCX the LNP handlers are called from an interrupt handler, so after the execution of lnp_*_set_handler() you can safely assume that the old handler will not be called any more. On a PC things are different, there is a problem. I didn't (...) (24 years ago, 23-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: C++ OverHead
|
|
I seem to recall someone doing some testing that showed that C++ programs worked out to take out somewhere around 2 to 3 times the space of comparable C programs. However, I'm sure that varies. Luis (...) ---...--- "Nobody ever said that democracy (...) (24 years ago, 23-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Speed value interpretation?
|
|
(...) As far as I can tell, the speed value really affects power output. This indirectly affects speed, but not in a very happy way. You end up with a wide range of values that give you nearly the same speed, then a very short range that decreases (...) (24 years ago, 23-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | C++ OverHead
|
|
Hi all, a simple question ( I hope) I'm running a small GA on my rcx block , and I'm fairly happy qwith my results so far, it evolves well tot he conditions, however I'd like to try something new <g>... I'm going to try to evolve sub-sumptive (...) (24 years ago, 23-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Parallel sensor problem
|
|
Hi, all. I'm experiencing a strange problem. I'm using two RCXs to control my crane, and I have a single touch sensor connected to input 1 on RCX 1 & input 2 on RCX 2. However, when I run both programs, which both have a wait_event function like: (...) (24 years ago, 23-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Speed value interpretation?
|
|
(...) Greetings! Another Ross!! That's three hangin' around here now!! Well, OK ones a Rossz, but it's close enough! (...) driven (...) have (...) two (...) you (...) hit (...) Well, you could work it out really carefully, but then you've gotta take (...) (24 years ago, 23-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Motor Speed value interpretation?
|
|
Hi all, sorry if this question has been asked before but i was just wondering what the speed values for the motors represent? i have a robot with two motor driven wheels which i would like to be able to make drive in an arc. To do this i have to set (...) (24 years ago, 23-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.5 and LNP
|
|
(...) was like this: (...) you reload (...) PC, as you are (...) thing is to read (...) place of (...) optimize it and (...) what you want (...) attribute. Yes, but I'm not sure what could happen if I change those addresses in the middle of the (...) (24 years ago, 22-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.5 and LNP
|
|
(...) Ok. Checking and testing never hurts :-). (...) It's not for performance, but for correctness. The old code was like this: if(lnp_addressing_ha...ler[port]) { ... lnp_addressing_handl...th-2,src); You first test lnp_integrity_handler and then, (...) (24 years ago, 21-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.5 and LNP
|
|
(...) you may see (...) give access (...) the handlers (...) My only (...) depend on. (...) introduce a (...) this point to (...) I think that we can use safely (CONF_TM || defined CONF_HOST) condition. I'm checking the whole patch and I think that (...) (24 years ago, 21-Jan-01, to lugnet.robotics.rcx.legos)
|
