Is 3rd time a charm? we'll see... CM15A RF range

[andyd]

I don't think the USB recognition problem is
a hardware fault.  I have seen this problem
and it always appeared to be a consequence
of a CM15a lockup.  Since I cured the
lockups I have not seen the USB problem.

BTW I've now been running the same load for
12 days with no timer shift, no failed
macros, and no lockups.  Computer is not
connected and CM15a is not my rf receiver.
I need to add some more controls to my build
so this test run will probably end on the
weekend.

I hope X10 does some testing in a noisy
power line environment.  I'm convinced many
of the CM15a problems are caused by power
line noise.  I accept that noisy power lines
and poor phase coupling may stop any X10
system working properly but they should not
cause controller program crashes. - Any
response X10 pro?

Andy

[X10 Pro]

Andy: I agree that powerline noise shouldn't
cause the interface to crash or stop working,
and if that's causing problems it would be
good to know. What source of noise did you
identify and isolate?

[britt]

AndyD,

You mentioned curing the lockups.  How did
you do that?

Thanks!

[andyd]

My noise source was the power supply of the
Dell laptop used to interface with the
CM15a.  Info is on this forum somewhere.

Lockups were eliminated by using a filter on
the Dell PSU and by installing a phase
bridge.

Andy

[mark n]

I have still not received the promised
email or phone call from tech support. 3
days and counting on that one...

As requested by X-10 Pro's post, I plugged
the CM15 USB cable back into the computer
and opened up AHP (3.175). Selected
Hardware config and when the window opened,
time popped up correct, but battery time
remaining was 0. I am positive that I reset
it before I pulled the unit last time...
and for sure there have been no long power
outages. I reset battery time and hit save.
Then, I noticed that all the macros that
have delays in them had begun to run, right
where they had stalled several days ago. In
fact, I had several macros all executing at
once, and the timing intervals appeared to
be correct. Hmmm... sure sounds like the
clock simply stopped, and querying the unit
over the USB link started it again!

I added a couple of new modules and some
additional macros for test purposes and
then downloaded and saved to the CM15.
Unplugged it from the computer and moved it
back to it's home outlet out in the hall.
Started up the monitor routine on the
libretto and we'll see how long it lasts
this time.

One odd thing: at the instant I plugged in
the USB cable, the activity monitor in the
AHP software reported activity on
address "P-16" , but my powerline monitor
saw nothing. Don't know if that is
meaningful or not...

[X10 Pro]

Mark: Thanks for the additional information.
This is in the same family as a few other
problems we are currently looking at in
depth. Can you send your AHP data file to
ahpsupport@x10.com? We might want to run your
exact configuration here.

[mark n]

Will do... Still running this morning,
clock is accurate, all timers executing.

Seems like the fact that the battery time
remaining gets reset to 0 when the unit
goes sproing ought to be a clue...

[britt]

I have noticed the same thing.  So far, three
days and still running....