 | | Re: NXT Program: How to avoid stop-and-go? (US-Sensor in angle)
|
|
(...) At a glancing angle (not approaching the wall "head on" at 90°, but at an angle) very little sound energy will be reflected back towards the sensor. If there isn't enough energy reflected back for the sensor to "hear" the echo, it won't detect (...) (18 years ago, 22-Dec-07, to lugnet.robotics)
|
| |
| | Re: NXT Program: How to avoid stop-and-go? (US-Sensor in angle)
|
|
Brian, It works fantastic. Thanks. Now I've put 2 US Wait blocks. The 1st one to slow down for < 30cm and the 2nd one to turn for < 20cm. This works pretty well when the vehicle runs ~90 degree toward the wall. But when the angle is flat it only (...) (18 years ago, 22-Dec-07, to lugnet.robotics)
|
| |
| | Re: mindscript (NBC NXC)
|
|
(...) If you are running on a Windows platform then you can start with Bricx Command Center (BricxCC). It is an integrated development environment (IDE) that supports Not eXactly C (NXC) and NeXT Byte Codes (NBC) for the NXT brick running either the (...) (18 years ago, 21-Dec-07, to lugnet.robotics)
|
| |
| | 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 (...) (18 years ago, 21-Dec-07, to lugnet.robotics)
|
| |
| | 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? (...) (18 years ago, 21-Dec-07, to lugnet.robotics)
|
