Please login or register.

Login with username, password and session length

Author Topic: Dusk and Dawn-NOT  (Read 3113 times)

martin mtl.

  • Newbie
  • Helpful Post Rating: 0
  • Posts: 8
Dusk and Dawn-NOT
« on: December 12, 2004, 01:24:16 PM »

I am running my CM15A on updated AHP 3.173
for a few days now and am experiencing odd
behavior (not me, the CM15A).  I have seven
WS467 light switches and six AM466
appliance modules and a Leviton
Coupler/repeater.  All modules respond
flawlessly when talking to them manually,
even when I turn off my PC and use my
PalmPadRemote (albeit with limited range,
about 30 feet).  I have nine of the
thirteen modules timed to turn on in the
evening and off late at night and morning.
At first I set up each of them using the
Dusk/Dawn feature (after setting the time
zone to my location) and that worked for
one cycle.  The following day the lights
did not turn on as programmed, nor did they
turn off (after turning them on manually
through AHP)  The time and time zone still
show correctly but the timed on/off
requests refuse to operate. The modules can
all still be controlled manually either
through AHP or RF.  I deleted everything,
purged delayed macros, cleared the
interface memory, unplugged from AC, pulled
the batteries and started over.  Same
result.  I then tried a simple macro timed
to turn on at dusk, then each of the
modules to turn off at set times.  Dusk
came and went and nothing happened, the
cleared activity log stayed empty as well.
I now have them individually set to turn on
and off (without using the Dusk or Dawn
feature) and that works. I have tried with
the PC on or off, same result. Any ideas?
Also, a few times the CM15A would hang
(activity log showing the last command
repeating itself and blocking all traffic)
The only way to stop that was to totally
unplug the CM15A and reconnect.
Logged

holger

  • Full Member
  • ***
  • Helpful Post Rating: 0
  • Posts: 36
Re: Dusk and Dawn-NOT
« Reply #1 on: December 13, 2004, 04:25:51 AM »

I let you know what I found out - not only
with dawn/dusk.
I have done similare to get a clue -> clear
interface, clear delayed timers or unplug
from AC, remove the batteries - all not
solid proofed.
Method I practice now:
I download the S/W, disconnect CM15A, place
it into the original AC outled in the middle
of the house, then I start a macro (trigger
the macro by RF remote) which kicks off  3x
88%dim (with two 5 sec. delays between) to
drive my sunshades to 75% down.
If it doesn't work I download again ->
repeating downloads until my test works.
If this works, all ! timings behave normal.

One symptom I noticed if th CM15A doesn't
work properly:
Activation of a X-10 device via RF Remote
takes longer, i.e. I have to press the
button longer/or more often, until the
appropriate unit reacts.
My suggestion
- the download does not work in the first
case - funny, I get no error message !
- the CM15A S/W must be somehow busy, like a
lock-up, it can hardly recognises/accept RF
inputs.
Holger
Logged
 

X10.com | About X10 | X10 Security Systems | Cameras| Package Deals
© Copyright 2014-2016 X10.com All rights reserved.