Dave W
You are right, as some of the problems are
user related.
When I was testing the CM15a I was only
controlling 1 light( stairs) using 2
motion detectors( 1 on top and 1 at the
bottom) I else used flags
including ,dusk/down and timer , the macros
where fully tested with the CM15a connected
to the computer. The macros were working
fine with no problems connected to the
computer(and yes they were set to run from
the interface); with the CM15a
disconnected, if I triggered the motion
detectors within 5 seconds of each other it
would stop working(the clock was lost), of
course the moment the CM15a is plugged back
to the PC it work again(magically the clock
is reset).
I did numerous test using another computer
connected to an CM11a used for monitor
only, I concluded that if the controller
got busy (RF + timer) some how it would
clobber is software clock.
In my book if a user programmed macro can
make the CM15a fail, it’s not a user fault
but a device design flaw.
I am not a novice X10 user either, some of
my lamp module are brown with a “BSR” label
original purchased from a company called
Heat Kit ( ps I am only 29…).
In our shop we have dedicated people just
testing and abusing the device we make,
user error can not cause the instrument to
malfunction, it’s not acceptable.