Control Lab Interface response time

[linmix]

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 corresponding output.
It took almost a second for a motor to stop or start responding to a
touch sensor.

I'm starting to get the hang of RoboLab, but  would I get better results
with another software?

I can see this lag could become quite problematic if I want any
precision in a setup controlled by the CLI. Can anyone give me any hints
as to how to minimize this problem?  

Thanks in advance,
linmix

[Iain Hendry]

In lugnet.robotics, linmix <linmix@...> 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

[Dan Berladyn]

In lugnet.robotics, Iain Hendry wrote:

> In lugnet.robotics, linmix <linmix@...> 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

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 or a NXT.

You can try using the ActiveX Control found here on this webpage (it hasn't
worked for me under Vista, but XP should be ok).  Or you can hunt down the
original CLI software but that only works with Windows98.  The best thing to use
is Robolab or to code something yourself in a C language.

Dan

[Dan Berladyn]

In lugnet.robotics, Iain Hendry wrote:

> In lugnet.robotics, linmix <linmix@...> 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

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 or a NXT.

You can try using the ActiveX Control found here on this webpage
http://dan.berladyn.net/LEGO/LEGOocx.html (it hasn't worked for me under Vista,
but XP should be ok).  Or you can hunt down the original CLI software but that
only works with Windows98.  The best thing to use is Robolab or to code
something yourself in a C language.

Dan

[Anders Isaksson]

Iain Hendry wrote:

> In lugnet.robotics, linmix <linmix@...> 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

I have a Delphi program for communicating with the old Dacta interface 70909
here:
http://web.telia.com/~u16122508/dacta/

Maybe that can be used for Control Lab too?

--
Anders Isaksson, Sweden
BlockCAD:  http://web.telia.com/~u16122508/proglego.htm
Gallery:   http://web.telia.com/~u16122508/gallery/index.htm

[zapher]

CAN THIS BE CHECKED WITH DIFFERENT HARDWARE?  PERHAPS THERE IS A LOOSE CONNECTION OR BAD CHIP< SORRY FOR THE CAPS>

linmix wrote:

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 corresponding output.
It took almost a second for a motor to stop or start responding to a
touch sensor.

I'm starting to get the hang of RoboLab, but  would I get better results
with another software?

I can see this lag could become quite problematic if I want any
precision in a setup controlled by the CLI. Can anyone give me any hints
as to how to minimize this problem?  

Thanks in advance,
linmix