Print

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

[Burdy]

Along  with the "An error has occurred while
communicating..." message, the activity log
entry showed:

Receive B2    (B2: Lighting Macro)
Receive B Off (B2: Lighting Macro)
Macro B All Units Off
Macro D All Units Off
Macro RF  DPause
Macro RF  O1On
Macro RF  JRecord
Macro RF  JRecord
Macro RF  B All Off
Macro RF  JRecord
Macro RF  M5On
Macro RF  A1Off
... and many more similar entries.  The
first few entries look correct (the trigger
was RF B2, and the 'B all off' and 'D all
off' macro was properly triggered.

I only have housecodes A through D defined.
I haven't defined any macros using Pause,
Record, or other similar AV terms (I've also
seen macro entries containing VolumnUp
CabAux and other terminology like that as
well). I also don't have any M,J, or O unit
codes defined.

The timer file hadn't been running more than
a minute or so before the event producing
the eror message and this log was triggered.

[andyd]

No, but I do see RF commands for house code
A and the CM15a rf codes are all disabled
and the only other RF receiver is set to
house code H.

Are you using the fancy remote that controls
tv and vcr as well as X10.  I'm at work so
don't have the model number.

[Burdy]

No, I don't have any X10 tv or A/V remote.
That's why its strange to see those
references in the log.

It looks like the memory is getting
corrupted, whether in the CM15A or AHP is
the question.

[X10 Pro]

Burdy: I think this goes along with the error
messages you've seen. When events run from
the interface, AHP matches the data to the
memory locations it has read from the CM15A.
When you see this, something isn't matching
up correctly.

[andyd]

I found out what caused the "spurious" code
A commands in my activity log.  I had put
batteries in my hawkeye motion sensor but
had not used it for anything.  It was
sitting on the table sending the default A1
on/off commands exactly as it was designed
to do.

Not a problem with the activity log although
I did learn that it reports all received RF
codes even if none are selected to be
transceived.

Andy D

[andyd]

I found out what caused the "spurious" code
A commands in my activity log.  I had put
batteries in my hawkeye motion sensor but
had not used it for anything.  It was
sitting on the table sending the default A1
on/off commands exactly as it was designed
to do.

Not a problem with the activity log although
I did learn that it reports all received RF
codes even if none are selected to be
transceived.

Andy D

[andyd]

I found out what caused the "spurious" code
A commands in my activity log.  I had put
batteries in my hawkeye motion sensor but
had not used it for anything.  It was
sitting on the table sending the default A1
on/off commands exactly as it was designed
to do.

Not a problem with the activity log although
I did learn that it reports all received RF
codes even if none are selected to be
transceived.

Andy D

[outland]

My X10 system occasionally receives
interference from any strong local UHF
signals.  It will misinterpret the
interference and cause erratic behavior of
some devices (lights turning on or off).
Along with this, eroneous commands appear in
the activity log.  I have been able to
duplicate this behavior with a FRS walkie-
talkie held near by.

[outland]

My X10 system occasionally receives
interference from any strong local UHF
signals.  It will misinterpret the
interference and cause erratic behavior of
some devices (lights turning on or off).
Along with this, eroneous commands appear in
the activity log.  I have been able to
duplicate this behavior with a FRS walkie-
talkie held near by.

[andyd]

Sorry about the multiple postings.  The
forum reported an error and the post didn't
appear to have been sent.

[donald mcmow]

Andy: That is the problem with FCC
approvals of products (any products). Their
requirments are: the product must not
interfere with other devices and must
accept outside interferance even if it
causes undesirable operation. The only
thing you can do is try to re-orient the
interface so as to minimize the outside
interferance. X10 only needs to provide
minimal RF shielding to get product
approval and unfortunately anything that is
close to the interface and transmits will
cause problems. This goes for any
electrical devices and until ALL electrical
engineers provide enhanced shielding for
their devices we have to live with it.