Subject:
|
Re: NXT Program: How to avoid stop-and-go?
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Fri, 21 Dec 2007 02:54:45 GMT
|
Original-From:
|
bigboss97 <bigboss97.geo@yahoo.comNOMORESPAM>
|
Viewed:
|
4983 times
|
| |
|
|
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?
Brian Davis-3 wrote:
>
>
> Try a Move block set to "unlimited": that will turn the motors on and let
> them
> run. Then have a Wait block to wait for the US sensor to report an object,
> or
> something similar inside a Loop. When an object (like a wall) is detected,
> the
> next block is a Move block set to turn or back up.
>
> --
> Brian Davis
>
>
--
View this message in context: http://www.nabble.com/NXT-Program%3A-How-to-avoid-stop-and-go--tp14446433p14449451.html
Sent from the LEGO Robotics mailing list archive at Nabble.com.
|
|
Message has 1 Reply:
 | | Re: NXT Program: How to avoid stop-and-go?
|
| (...) 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 (...) (17 years ago, 21-Dec-07, to lugnet.robotics)
|
Message is in Reply To:
| | Re: NXT Program: How to avoid stop-and-go?
|
| (...) Try a Move block set to "unlimited": that will turn the motors on and let them run. Then have a Wait block to wait for the US sensor to report an object, or something similar inside a Loop. When an object (like a wall) is detected, the next (...) (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
|
|
|
|
