Subject:
|
ROBOLAB Questions
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Fri, 23 Sep 2005 22:55:14 GMT
|
Viewed:
|
1027 times
|
| |
|
|
Why does ROBOLAB not turn the motors off after a "wait for..." direction? Almost
every program that I have written with ROBOLAB has had issues with motors not
turning off when they were supposed to. As an example: I have a program that
drives one motor forward until a rotation sensor gets to a certain value. Then,
that motor is supposed to turn off, and another motor is supposed to turn on
until a touch sensor is pressed. However, the first motor does not turn off.
Rather, it continues to turn while the other is doing its assigned task. Another
thing is that this doesn't always happen. Sometimes, ROBOLAB turns off the
motors exactly when it is supposed to. Anyone have ideas or a fix for this? I
mean, sure, I could put a "stop motors" command after every "wait for..."
command, but if I had to do that, I might as well go back to RCX Code! I can
email code samples if needed.
As a sidebar, where can I get version 2.5.4? I have 2.5.1, but that doesn't work
with ULTIMATE ROBOLAB. And, is there a way to convert RCX Code into ROBOLAB
*.vi's? I have hundreds of RCX Code programs, but I want to rid myself of RIS.
Andrew Meyer
|
|
Message has 1 Reply:
 | | Re: ROBOLAB Questions
|
| Andrew, To the best of my knowledge the wait commands never turn off any motors. To do so would require that you could attach a motor modifier to the command. It would also limit the commands usefulness. If you really want a wait for distance (...) (19 years ago, 29-Sep-05, to lugnet.robotics)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
