 | | 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)
|
| |
| | Re: LegOS 0.2.5 and LNP
|
|
(...) I cleaned up my code (found one bug!), the patch follows. As you may see now there are two semaphore, because two are the resources to give access to: the LNP buffer and the IR port. I modified the calling of the handlers to avoid race (...) (24 years ago, 20-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: undefined reference to `___ucmpsi2'
|
|
(...) With regards to this, it appears that Markus left out two necessary functions in lib/mint. Specifically, cmpsi2 and ucmpsi2. These are a part of librcx but apparently they were omitted from LegOS when Markus included support for the other (...) (24 years ago, 19-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: undefined reference to `___ucmpsi2'
|
|
(...) Another choice may be a cast in the switch statement, like this: static wakeup_t light_found(wakeup_t sens_num) { switch ((unsigned int)sens_num) { case 2: return (LIGHT(SENSOR_2) > THRESHOLD); break; case 3: return (LIGHT(SENSOR_3) > (...) (24 years ago, 18-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.5 and LNP
|
|
(...) Ok, I clean up the code and send you a patch. (...) This one is not yet ready. As soon as I do it you'll know. bye Bernardo (24 years ago, 18-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: util/dll-src makefile patch
|
|
(...) current cvs (...) lnp.c under (...) windows. The other (...) They works. :-) Bye, Paolo. --- I'm an optimist, but I don't think it helps. (24 years ago, 18-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: undefined reference to `___ucmpsi2'
|
|
Hi, The problem is that wakeup_t is an unsigned long, and in order to save space, the switch statement is optimized to call a library comparator, ucmpsi2. Since the argument to ds_scale is an unsigned int, the argument to LIGHT should also be an (...) (24 years ago, 18-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | undefined reference to `___ucmpsi2'
|
|
I get this error when linking if I have the following in my source code in a wait_event function: #define THRESHOLD (unsigned short)50 static wakeup_t light_found(wakeup_t sens_num) { switch (sens_num) { case 2: return (LIGHT(SENSOR_2) > THRESHOLD); (...) (24 years ago, 18-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: pass by refrence or value?
|
|
Did you care to declare your global variable as volatile? this (normaly) prevent the compiler to optimize memory access and force it to read the actual value of the variable each time it need it ( instead of localy storing it in a register wich will (...) (24 years ago, 18-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | c++ changes
|
|
After some prompting, I have made the method names in the c++ classes uniform in case. Unfortunately, the changes are not backward compatible. Please let me know of any problems you discover. If I don't hear of any problems, I'll check in the (...) (24 years ago, 18-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | util/dll-src makefile patch
|
|
Hi, Here is a set of patches for util/dll-src/Makefile against the current cvs version. The first patch avoids the need of a symbolic link to lnp.c under unix. Can somebody please let me know if it works under windows. The other patches are for (...) (24 years ago, 18-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | pass by refrence or value?
|
|
Hi all, i have a slight problem with legosv0.2.5 . The program code on the rcx is set up so that there is serverall callback methods which get called when a message comes in on the particular port for that object or class. These callback methods set (...) (24 years ago, 18-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.5 and LNP
|
|
(...) Btw. README is (...) Ooops... :-) Changed to 0.2.5 version inside. (...) transport (...) packets of (...) mainly as way for (...) collisions, lost (...) which works as (...) write code to (...) To cut time (...) code that (...) directives (...) (24 years ago, 17-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | LegOS 0.2.5 and LNP
|
|
Yesterday I downloaded legOS 0.2.5 and peeked at the code. Btw. README is not up to date. For last two month I was working with a friend of mine on a transport protocol implemented on top of LNP for the transmission of packets of unlimited size and (...) (24 years ago, 17-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | legOS lcd management and thoughts on velocities
|
|
Hello! I' am french, from Paris ( a way to say: excuse my english... or feel free to correct it!). Few weeks ago I download legOS (v2.5), and I made my first step with it. First all I wish to thank all people involved in this project. This OS is (...) (24 years ago, 16-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LEGO remote and LNP (legOS 0.2.4)
|
|
(...) My patch changes both, dll and the legOS kernel, to operate with odd parity. Did you both, reinstall the new kernel and use the new dll afterwards? You should also change the lnp daemon to odd parity if you are using it, I don't use it. (...) (...) (24 years ago, 15-Jan-01, to lugnet.robotics.rcx.legos)
|
