 | | Re: TachoSpeed.nqc
|
|
(...) You assumed correctly. Without the wait the if statement is always executed immediately. I see what you mean: by taking the wait out of the start of the loop the sensors are checked more frequently. That doesn't solve the riddle though, (...) (18 years ago, 12-Mar-07, to lugnet.robotics)
|
| |
| | NXT now has atan2 function block
|
|
Download atan2 (and atan, sin, cos, sqrt blocks) at www.convict.lu/Jeune...sIntro.htm for NXT-G. Please report any bugs. (18 years ago, 12-Mar-07, to lugnet.robotics)
|
| |
| | Re: TachoSpeed.nqc
|
|
(...) I don't really understand what you mean when you say "the brick doesn't do anything". Can you be more specific? (...) They will both be executed in sequence if at the time the second if statement reads the TachoSpeed setting on OUT_L it (...) (18 years ago, 12-Mar-07, to lugnet.robotics)
|
| |
| | Re: TachoSpeed.nqc
|
|
Doesn't this make more sense. (...) The way it was written you hardly ever checked the TachoSpeed because most of the time was spent in the Wait(20). I assume the Wait is in there to allow the robot to get up to speed before you start checking for a (...) (18 years ago, 12-Mar-07, to lugnet.robotics)
|
| |
| | Re: TachoSpeed.nqc
|
|
(...) I 've done just that, but the problem I describe persists: When the TachoSpeed reported by watching the brick is around 57, the brick doesn't do anything if the response value is set to 62. It does at 66 or 67 but that also makes it impossible (...) (18 years ago, 12-Mar-07, to lugnet.robotics)
|
