 | | 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)
|
| |
| | Re: TachoSpeed.nqc
|
|
(...) The problem is almost certainly that your program only runs for about 2 tenths of a second. If you want the program to run forward continuously and execute a special behavior if at some point during the execution of the program the TachoSpeed (...) (18 years ago, 11-Mar-07, to lugnet.robotics)
|
| |
| | Re: NXT Turkey MOC
|
|
Really nice! I recently built the original bug from the descriptions in the "10 Cool Lego Mindstorms RIS 2 Projects' book but the program files that come with it are all lsc files. I'm having a hard enough time learning NQC to try to make sense of (...) (18 years ago, 10-Mar-07, to lugnet.robotics)
|
| |
| | TachoSpeed.nqc
|
|
I'm trying to write a simple routine that uses the TachoSpeed value to see if my Cybermaster has run into something. I'm trying this on tiled floor, by making the bot with tank threads run into the wall, but only very occasionally does it actually (...) (18 years ago, 10-Mar-07, to lugnet.robotics)
|
