Subject:
|
Re: NXT Program: How to avoid stop-and-go?
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Fri, 21 Dec 2007 12:50:03 GMT
|
Viewed:
|
5028 times
|
| |
|
|
In lugnet.robotics, bigboss97 <bigboss97.geo@yahoo.com> wrote:
> But if the Move block is unlimited will the next block
> (Wait) be processed?
Yes. Move (unlimited) Starts the motors and *leaves them running* while
progressing on to the next block in a sequence. The motor state will then remain
unchanged until some other block (like a later Move or Motor block) changes it.
Try it an see. This can actually be used for some slightly faster multi-sequence
control of the motors if you do it right:
http://www.brickshelf.com/cgi-bin/gallery.cgi?i=2065175
There are a couple of blocks that will do things "behind the scene" for you
while the sequence of blocks continues to execute. The Sound block (playing a
tone or a .rso file) is like this as well; you can click a checkbox in the
configuration pane to get the NXT to "not wait for completion" in this case.
--
Brian Davis
|
|
Message has 1 Reply:
Message is in Reply To:
 | | Re: NXT Program: How to avoid stop-and-go?
|
| But if the Move block is unlimited will the next block (Wait) be processed? and when it goes to Wait block isn't that mean Move block is done and it will stay in the Wait block for ever, because the vehicle is not moving? (...) (17 years ago, 21-Dec-07, to lugnet.robotics)
|
10 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
