 | | Re: Two motors at the same time... It is possible?
|
|
(...) Hi Johan, While you're dealing with very practical questions here, I thought I'd throw a paper into the mix: (URL) was presented in the ACM conference on Programming Language Design and Implementation (PLDI) in 2005. It's a nice paper (...) (18 years ago, 19-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Two motors at the same time... It is possible?
|
|
John, (...) It worked just as I expected. The two motors now are rotating the same time. Thanks to your example, now I am giving some time to understand this setOutput call, and reading all the documentation (it is quite easier with pratical (...) (18 years ago, 19-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Two motors at the same time... It is possible?
|
|
(...) Or maybe just wrap the calls inside a mutex, so at least the behaviour is defined, if not optimum. Many of the NBC/NXC macros do exactly that, maybe all of them should? ROSCO (18 years ago, 19-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Two motors at the same time... It is possible?
|
|
(...) I understand his confusion. Not allowing separate threads to call the same subroutine is certainly unexpected. The concept of "thread" conventionally involves separate stacks for local variables (and a shared global state -- unlike separate (...) (18 years ago, 19-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Two motors at the same time... It is possible?
|
|
(...) It is possible. The NXC API doesn't currently wrap this capability in a really simple function. (...) The RotateMotor API function calls a subroutine written in NBC that does not return until the tachometer limit target has been reached. (...) (18 years ago, 19-Feb-07, to lugnet.robotics.nxt)
|
