 | | 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)
|
