[wish-info] Time delay when executing blocking commands. Almost no delay when executing non-blocking commands

[Boyan Biandov]

Hi,

I am seeing an interesting behavior using CM11A:

I see a time delay when executing blocking commands but almost no delay
when executing non-blocking commands. This is not the classic "duh,
that's why they are called non-blocking".

Let me be more specific on this behavior:

When I use echo which is a blocking command, the command blocks for
about 10 seconds, after which time I get the prompt back. The actual
task (light turning ON or OFF) is not carried out until the 9th second,
which is about one second from when I get my prompt back. So there is
about 8 second delay when I neither get the prompt back nor the x10
command is sent out.

Conversely when I use nbecho I get the prompt back right away and the
x10 command is carried out almost instantaneously.

What gives?

~Boyan

[WSH]

You are correct that there is an artificial delay in blocking commands to
the transceiver. There is a parameter you can pass called /delay that will
allow you to adjust this time.

The reason it is there is because I couldn't figure out how to tell the
transceiver to wait for a clear line before transmitting so I always add a
specific delay before the start of any command to allow time for the line to
go quiet. This is very poor design as it relies on having only one active
transceiver in the home. The delay allows for intelligent devices to
respond to queries without the next command jumping in.

Note that this is not a problem with the PowreLink Serial but is for both
the PowerLink USB and the CM11A.

Scott

----- Original Message -----
From: "Boyan Biandov" <***@seiu1021.org>
To: <wish-***@lists.sourceforge.net>
Sent: Tuesday, January 29, 2008 2:15 PM
Subject: [wish-info] Time delay when executing blocking commands. Almost
nodelay when executing non-blocking commands

Post by Boyan Biandov
Hi,
I see a time delay when executing blocking commands but almost no delay
when executing non-blocking commands. This is not the classic "duh,
that's why they are called non-blocking".
When I use echo which is a blocking command, the command blocks for
about 10 seconds, after which time I get the prompt back. The actual
task (light turning ON or OFF) is not carried out until the 9th second,
which is about one second from when I get my prompt back. So there is
about 8 second delay when I neither get the prompt back nor the x10
command is sent out.
Conversely when I use nbecho I get the prompt back right away and the
x10 command is carried out almost instantaneously.
What gives?
~Boyan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
wish-info mailing list
https://lists.sourceforge.net/lists/listinfo/wish-info