Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[happyras]

Until very recently my interface has worked
very well.  My previous issue with
repeating commands initated from an RF
remote has returned.  CM15A upgrade was
received some time ago which "fixed" this.
Now its back.  Commands from the PC work
without a hitch.  Macros from the CM15A
work fine, but if you use any of the remote
RF command devices, the CM15A will repeat
the same command until the device is pulled
out of the AC outlet.  I am running without
batteries to make the reset simple.  During
this lock up, the CM15A can still recognize
other commands, and they log, however no
commands are actually ever received at any
of the controlled modules.  For example, an
RF command to turn on a module is received
and repeated by the CM15A, but the actual
device module never sees the command to
turn on.  When reset, by removing power,
the CM15A returns to normal and executes
line commands from the PC fine.  Any RF
command will initiate the repeating.  I
might be better off going back to 3.187.
How do I revert back to this version?  Does
this give you any clue on what memory area
you are walking on in the newer versions?
Let me know how to proceed.  Anyone else
having this concern?

Thanks

[ebsflight]

Yes, I am having a like problem
The system appears to lockup in a loop mode
where it thinks it is receiving a stream of
x10 commands. When you open the "Activity
Monitor" it is clicking away reporting
receiving the same x10 command every cycle.
During this time the system will not respond
to any command initiated from the active home
SW. This is how I figured out something was
not working. I haven't figured out what
triggers the problem.

I have tried disconnecting the module with
the address that is being reported by the
"Activity Monitor" but it still keeps
reporting the received command and will click
away reporting the same received command. The
record is over 8000 events in this mode. I
let it run several time to see if it would
clear its self.

The only thing I have found which stops the
problem is unplugging the CM15A from the
power receptacle. When I plug the CM15A back
into the power the system starts working
normal. It usually runs for some time as it
should before locking up again in the receive
loop mode.

Is this a SW problem or a fault in the CM15A
interface?

[happyras]

This problem was corrected in version 3.186
or so after a beta debug program was
offered to me.  Using 3.187 since, this did
not reocurr until I upgraded to 3.198.
I have found a interesting issue.  If I
choose to monitor a house code (C) I rarely
use, instead of the predominant code (A),
then this issue seems to be very
infrequent.  The activity monitor is still
showing all events, however macros executed
by RF remote on code A do not work, only
direct calls to individual devices on A
seem to still work on RF.
This problem resumed after uninstalling
3.199 and going back to 3.187.  Something
is carrying over from the new version, even
after uninstalling it.  Still, I would like
some help from X10 on this, but they are
likely buried in other concerns.  This
could be a root cause of other issues (my
guess).  Your are correct that unplugging
the CM15A from 110volts will kill the so
called "signal storm".  I am not 100%
certain, but using a Leviton coupler
repeater in your panel could be an
associated issue.  I am just very
disappointed that this issue has returned
to my system after being resolved 6 months
ago or more.

X10 can you comment???

[happyras]

I just ordered a new CM15a, offered with all
three add in programs, and I also added the
5yr replacement guarantee.  Chris advised me
that they had upgraded the CM15a hardware
since my purchase in Nov 2004, even though I
know I got a replacement in the spring of
2005.  I thought it worth a try.  I am
currently running great on 3.187, without
signal storms, and monitoring a house code
which has no modules, C.  When I monitored
A, most used code, my RF commands would
start a signal storm under 3.198.  I hope to
be able to update the new interface with
3.199 and use the Conditional Macros,
Iwitness, and Myhouse features.

Am I only dreaming, I will definately wake
up before the 30 day's is reached if this
proves no better.

[bruce]

I had the same signal storm issue.  I
resolved it by disabling the offending
transceived housecodes in the CM15A under
tools\hardware configuration.  If you do
this, be sure to update the interface from
the hardware configuration window.  I
wasn't about to give up the good coverage I
had with my existing transceiver modules.