Print

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

[don]

Please put back the capability to set the
CM15 clock to seconds and not just minutes.
Even an option to do this would be great.

[roger1818]

I would also like the ability to manually
override the current time to test timers.
I know I could change the clock on my PC,
but it would be better if I didn't have to
do that.

[donald mcmow]

Roger: Just reset your timer to a minute or
two before the computer/AHP time. You get
the same result - the event happens without
having to reset the computers clock and
updating the interface.

Don: The seconds could be were the problems
occured with the interface locking up at
apparent random times. This maybe why X10
chose to eliminate them. Also there is an
inherent time delay while the interface
transmits the powerline control signal out
which makes for problems with getting the
timing down for an event. Besides which
does up to 59 seconds really make a
difference in the sceme of things. We are
not worried about when the lights turn on
as much as that they do turn on, RIGHT.

[don]

Donald McMow:  While you are right that the
exact time for a light to come on may not
always be needed, I found that it comes
handy.  Since it used to work and since the
CM15 still keeps track of the seconds, I
still would like it to happen at the time I
asked it to come on not 59 seconds before
or after the set time.

[roger1818]

Don:  If you need the time set accurately,
you can easily get it quite close (within a
couple seconds) by waiting for the time to
roll over to the next minute and then open
up the Hardware Configuration window.  The
action of opening that window will set the
clock.  You can then close the window by
clicking Cancel.  You can verify the time
by generating a Status Report.  The time is
displayed twice in the report, once without
seconds and once with.  I hope this helps.

[Dave R]

Roger, I have tried U’r technique numerous
times and find it doesn’t work reliably.  My
seconds are more likely to be set 30 to 59
late as they are to be dead on to 1 or 2 sec.
off.  Somewhere in some post(s) in some
thread(s), some users have indicated that
keeping the CM15A connected to the computer
keeps the interface clock on time due to the
computer’s clock syncing the CM15A’s clock on
some unspecified interval.  If this is the
case, this intermittent syncing will only
occasionally result in the CM15A keeping
accurate time.

X-10 Pro, in Bug Reports, “AHP interface
time” (3/1/05, 6:45 pm) and “Timers not
starting on time” 2/6/05, 9:49 pm), several
posters have expressed an interest in this.
Some have speculated or asked about the
purpose of this change.  Can U shed some
light on the necessity for this?