Print

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

[joe s.]

Roger, Concurrent range reduction in TM751
and CM15a does suggest an outside RF noise
source (I'm sure you thought about that).
Are you living near powerlines or is your
bedroom located next to the hospital's MRI
ward (only partly kidding).  What external
Rf sources do you imagine might be near (+/-
300mhz)?  New Plasma TV, etc?

[roger1818]

Joe:  The problem suddenly occurred just
before 1:00am this morning (I had just sent
an RF bright command on B13 which is
transceived by my TM751).  I did a couple
quick tests and then went to bed.  In the
morning the problem still existed so I
unplugged the CM15a and removed the
batteries.  When I plugged it back in,
everything started working normally again.
This makes me think that the CM15a somehow
started generating the noise.

[joe s.]

geez - thx for even spotting this...I meant
it to land in reply to your thread...must
be those drugs I took as a child...

I have noticed many people in the "bugs"
forum discussing COLD BOOT for their CM15a,
and more than one has related a reference
to how their RF coverage improved
afterward...maybe it's connected in some
mysterious way.

[Brian H]

Have not used my scope yet, but with a Logic
Probe. There is a constant unsquelched noise
[hash] on the Receivers Data Output to the
controller chip. I have another modular RF
receiver and it also has this constant hash
on the data output. Have no idea if the
controller is getting over run by checking
for good data. Have not looked at my WGL
V572A but would guess it also has hash on
the data output when no RF is being
received. As it also uses a modular type
receiver.

[SteffenH]

I had a simular problem this weekend, The
Cm15 was in a constant receive condition
getting bogus commands that I traced back
to my CM19A which seems to be causing the
condition. Once I pulled the usb connection
on the CM19A the bogus commands stopped.
However after this the RF range seemed to
be very limited at best, I needed to hold
the palmpad remote right next to the CM15
to get it to recognize anything. I tried
clearing the interface and reloading the
macros and timers but this did nothing. I
then completely unplugged the CM15 pulled
the batteries and USB cable, let it sit for
about an hour while I did other things,
came back plugged everything in again
downloaded configuration and macros.
Magically everything was working again had
plenty of RF range, have one motion sensor
about 20 feet away. I think that something
must have locked up that only a cold
restart fixed.

[roger1818]

Joe:  LOL.  I figured it was meant as a
reply.  I forgot to answer one of your
questions.  I live in a reasonably new
residential neighborhood.  There aren’t any
transmission lines, hospitals, or any
commercial buildings within about a
kilometer (far more for the hospital).  I
also haven’t purchased any new electronics
recently (pretty much everything was off
anyway) so unless one of my neighbours is
doing some late night RF experiments (I do
live in a techie neighbourhood) I doubt if
the noise is from an external source.

I haven’t seen the problem since, but I
will report if it happens again.

[X10 Pro]

I think it's odd to all of a sudden have
several repors of RF range problems that can
be fixed by resetting the interface. I'm
going to see if we changed something in RF
config operation in the interface without my
knowing.

[roger1818]

X10 Pro:  One change that was made to the
RF portion of code was:

- Fixed RF-only modules (TM751, UX21A,
etc.) not being encoded using RF commands
for timers and macros stored in the
interface.

Maybe this fix is causing the CM15a to get
into a mode where it broadcasts RF
garbage.  Just a guess.