 | | Re: speed control help
|
|
lroska wrote: <snip> (...) <snip> (...) <snip> (...) <snip> The easy solution is to avoid using a formula that assumes anything about the motor speed curve (except of course that reducing the motor value reduces the speed). Try using a feedback (...) (27 years ago, 23-Jun-99, to lugnet.robotics.handyboard)
|
| |
 | | Re: speed control help
|
|
It sounds like you are running open loop. If you use the wheel encoders as feedback devices to close the loop, then you can use the motor control function in your program as a variable to adjust motor control current via PWM to match the command (...) (27 years ago, 23-Jun-99, to lugnet.robotics.handyboard)
|
| |
 | | New Challenge
|
|
Hello all.... I've been watching this group for a long time and while the discussions about RCX programming and LegOS is fine and good, what about some good old fashioned building challenges? Something that's challenging, yet actually can be (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
|
| |
 | | Re: signals / legOS internals
|
|
(...) Why signals?!? Unix-style asynchronous signals is the last feature I would ever want to implement or use. Brain-dead and very dangerous "feature". As you write; "The problem is that a signal can happen at any time". You shouldn't pass this (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: signals / legOS internals
|
|
(...) An asynchronous signal models a hardware interrupt. There are times when that is the appropriate interface. There are times when other interfaces are less error prone and are easier to write correctly. Frequently using only synchronous (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|