delay between command and action with Powerlink USB using wish 2.1.1

[Alex Shcherbatyuk]

I just installed the wish driver 2.1.1 and everything works fine but there
is about 5 seconds delay between the time I hit enter for echo command and
the time the light actually reacts. I tried both echo and nbecho with
identical results.

I don't think I experienced this delay using the windows software that came
with the PowerLink USB controller. Is this normal for this driver ? If not,
does anybody know a way to make this work better ?

Thanks,
-alex




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

[Scott Hiles]

This is normal for the driver.  You can adjust the queuing delay using some
of the parameters but by default I have them set to be very conservative to
work on noisy lines.  If you tweak down the delay between transmissions, you
will find that there is some balance between consistency of operation and
speed.  If you make it to fast, your system will be erratic with some
working and some not.

Scott

----- Original Message -----
From: "Alex Shcherbatyuk" <amerphy@...>
To: <wish-info@...>
Sent: Thursday, March 09, 2006 10:23 AM
Subject: [wish-info] delay between command and action with Powerlink USB
using wish 2.1.1

>I just installed the wish driver 2.1.1 and everything works fine but there
>is about 5 seconds delay between the time I hit enter for echo command and
>the time the light actually reacts. I tried both echo and nbecho with
>identical results.
>
> I don't think I experienced this delay using the windows software that
> came with the PowerLink USB controller. Is this normal for this driver ?
> If not, does anybody know a way to make this work better ?
>
> Thanks,
> -alex
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> wish-info mailing list
> wish-info@...
> https://lists.sourceforge.net/lists/listinfo/wish-info
>

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

[Alex Shcherbatyuk]

Thank you for prompt response Scott,

As I understand plusbd has two parameters related to timing:

"delay" - by default set to 0. It seems that it is meant to add additional
delay in case things don't work.

"timeout" - appear to control how long the driver will wait for the device
(I am not sure if this only applies to initial connection or to each
transaction with the device). This one is set to 1000 (msec) by default and
I tried to set it as low as 200 - driver cannot connect and 300 - driver
connects to the device most of the time. Setting this parameter lower than
1000 did not seem to decrease the delay between command and execution.

The x10logd timestamp indicates that there is a 2 second delay between
sending the address and the preset dim command.

Are there any other options I haven't tried, driver option ?

I really want to speed things up a bit if possible, I understand that
protocol can do about 1 command per second but what I am seeing with the
current parameters is a lot slower. I hope I am missing something.

-alexs


From:  "wsh" <wsh@...>
To:  "Alex Shcherbatyuk"
<amerphy@...>,<wish-info@...>
Subject:  Re: [wish-info] delay between command and action with Powerlink
USB using wish 2.1.1
Date:  Thu, 9 Mar 2006 10:34:25 -0500

This is normal for the driver.  You can adjust the queuing delay using some
of the parameters but by default I have them set to be very conservative to
work on noisy lines.  If you tweak down the delay between transmissions, you
will find that there is some balance between consistency of operation and
speed.  If you make it to fast, your system will be erratic with some
working and some not.

Scott

----- Original Message ----- From: "Alex Shcherbatyuk" <amerphy@...>
To: <wish-info@...>
Sent: Thursday, March 09, 2006 10:23 AM
Subject: [wish-info] delay between command and action with Powerlink USB
using wish 2.1.1

>I just installed the wish driver 2.1.1 and everything works fine but there
>is about 5 seconds delay between the time I hit enter for echo command and
>the time the light actually reacts. I tried both echo and nbecho with
>identical results.
>
>I don't think I experienced this delay using the windows software that came
>with the PowerLink USB controller. Is this normal for this driver ? If not,
>does anybody know a way to make this work better ?
>
>Thanks,
>-alex
>

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info