Subject:
|
Re: TachoSpeed.nqc
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Sun, 11 Mar 2007 23:21:34 GMT
|
Viewed:
|
3712 times
|
| |
|
|
In lugnet.robotics, linmix <linmix@gmail.com> wrote:
> Has anyone had the same problem and maybe a solution?
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 of either the left or right motor drops below a certain threshold
then you want the main body of your program to be an infinite while loop which
frequently examines the tachometer speed of the motors and reacts accordingly.
Just wrap your existing code in a while (true) { } loop.
John Hansen
|
|
Message has 1 Reply:
 | | 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)
|
Message is in Reply To:
| | 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)
|
13 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
|
|
|
|
