Subject:
|
Re: Control Lab Interface response time
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Thu, 5 Feb 2009 18:00:08 GMT
|
Viewed:
|
22419 times
|
| |
|
|
In lugnet.robotics, linmix <linmix@gmail.com> wrote:
> quite appalled by the lag between an input and the corresponding output.
> It took almost a second for a motor to stop or start responding to a
> touch sensor.
Whoah, a full second?! That's pretty useless! :( I'm trying to find software
to program the ControlLab right now, but if this is the case, I might as well
abandon any plans I had on using it. Fine motor control would be completly
impossible.
Did you ever find a result? I realize this post is 2 years old.
-Iain
|
|
Message has 3 Replies:
 | | Re: Control Lab Interface response time
|
| (...) Yes, the response time of the CLI is rather disappointing to say the least. Personally I think the CLI is best suited for controlling things like lights, and motors on someones town layout. For anything that requires precise control use an RCX (...) (15 years ago, 7-Feb-09, to lugnet.robotics)
| | | Re: Control Lab Interface response time
|
| (...) Yes, the response time of the CLI is rather disappointing to say the least. Personally I think the CLI is best suited for controlling things like lights, and motors on someones town layout. For anything that requires precise control use an RCX (...) (15 years ago, 7-Feb-09, to lugnet.robotics)
|
Message is in Reply To:
| | Control Lab Interface response time
|
| I finally got my CLI and did some simple testing today. I realize the CLI isn't going to be quite as fast responding as the RCX what with sending the information back to the PC etc etc, but I was quite appalled by the lag between an input and the (...) (17 years ago, 4-Jun-07, to lugnet.robotics)
|
6 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
|
|
|
|
