X10 Community Forum

🖥️ActiveHome Pro => ActiveHome Pro General => Topic started by: tom j on June 02, 2006, 11:14:40 AM

Title: Timers Slow To Execute
Post by: tom j on June 02, 2006, 11:14:40 AM
Hi just setup my Active Home Pro USB interface and I really love the graphics very attractive, some of the nicest I've seen! I do have a few questions about the setup though. One thing I've noticed is that the timers I created lag the time they are suppose execute. For example I set up a timer to turn on a light at 9pm and at 9 o'clock it actually didn't trigger the light until almost 9:01 something like 9 o'clock and 45 seconds, this was the only timer I had scheduled at this time so why the delay? Anyone else notice this? The interface and computer have or appear to have the exact time although I can't see the seconds on the interface. The old Active Home used to have a synchronize command but I can't find it if it has one in the Pro version. I'm also trying to get a response to why the security option is grayed out if you choose the dust/dawn option I'm sure you could use security in combination with dust/dawn in the old Active Home version. Thanks

Tcj
Title: Re: Timers Slow To Execute
Post by: tom j on June 02, 2006, 09:18:46 PM
Now I've noticed one of my timer is  5 minutes late. For example I have a timer for 9pm and is not executed until 9:05  >:( would this more then likely a hardware or software problem. Thanks

Tcj
Title: Re: Timers Slow To Execute
Post by: Charles Sullivan on June 02, 2006, 09:38:55 PM
When AHP sets the CM15A clock it always sets it to the whole minute, disregarding the seconds.  E.g., if the actual time is
8:30:45 the clock will be set to 8:30:00.  So your downloaded timers can execute as much as 59 seconds late.

After downloading your timers, if you wait until your PC clock just rolls over to the next minute and then click Tools > Hardware configuration, then click Cancel, you can set the CM15A clock to within a second or two of the actual PC time.

I can't account for your timer running 5 minutes late.
Title: Re: Timers Slow To Execute
Post by: tom j on June 03, 2006, 01:45:50 PM
When AHP sets the CM15A clock it always sets it to the whole minute, disregarding the seconds.  E.g., if the actual time is
8:30:45 the clock will be set to 8:30:00.  So your downloaded timers can execute as much as 59 seconds late.

After downloading your timers, if you wait until your PC clock just rolls over to the next minute and then click Tools > Hardware configuration, then click Cancel, you can set the CM15A clock to within a second or two of the actual PC time.

I can't account for your timer running 5 minutes late.

Thank You!!!!!!!!!!!!!!!!!!! I couldn't even get that explanation from support you know what they need is a synchronize with computer feature like on the old Activehome. Say most of my timers execute within a few seconds but seems like I saw one that was 5 minutes late, will check it tonight. Also maybe you could answer this question why can't you use the security option with the dust/dawn feature. You've been a tremendous help!

Tcj
Title: Re: Timers Slow To Execute
Post by: Charles Sullivan on June 03, 2006, 03:38:26 PM
The first few releases of AHP set the CM15A clock to the second.  This was changed to the current behavior in later releases, I suspect because it worked around some bug in at least the early CM15A firmware.  (X10Pro has stated there will be no going back to the earlier behavior.)

I don't remember if the earlier releases of AHP allowed you to select the Security mode for Dawn/Dusk timers.  If so and it's been changed, it would possibly be for a similar reason.  You may have noticed however that the maximum offset from Dawn/Dusk in a timer is limited to only 1 hour in AHP.  An additional time variation in Security mode could push the total offset past 1 hour and be incompatible with whatever scheme is used in the CM15A firmware for dealing with offsets.  But this is just a guess on my part.
Title: Re: Timers Slow To Execute
Post by: tom j on June 03, 2006, 08:16:48 PM
The first few releases of AHP set the CM15A clock to the second.  This was changed to the current behavior in later releases, I suspect because it worked around some bug in at least the early CM15A firmware.  (X10Pro has stated there will be no going back to the earlier behavior.)

I don't remember if the earlier releases of AHP allowed you to select the Security mode for Dawn/Dusk timers.  If so and it's been changed, it would possibly be for a similar reason.  You may have noticed however that the maximum offset from Dawn/Dusk in a timer is limited to only 1 hour in AHP.  An additional time variation in Security mode could push the total offset past 1 hour and be incompatible with whatever scheme is used in the CM15A firmware for dealing with offsets.  But this is just a guess on my part.

So they never offered any reason for not sequencing it to the second? Say please check back I want to tell you how everything came out. Say let me make sure I got it right just open up the hardware configurator and I've now noticed at the bottom of the AHP that the time is displayed in minutes and seconds is this my computers time or the time of the interface? What I did though because I wasen't sure is to bring up my "time & properties" display and when the time reached xx:59 I click on cancel right? Really can't think you enough. Really surprising that support isn't up on this stuff.

Tcj
Title: Re: Timers Slow To Execute
Post by: tom j on June 03, 2006, 09:20:26 PM
Hi update well somethings wrong all my timers are exactly three minutes late for example I had one for 9:05 didn't kick in until 9:08. All of them are three minutes and a few seconds off. What do you think is the problem and do yours execute within a few seconds of the programed time. Really like this thing but with x10 there's always something!!!! I'm not a brasher I've spent more money with them then I'm willing to tell my wife, but it's things like this that make their stuff so frustrating. Thanks

Tcj
Title: Re: Timers Slow To Execute
Post by: Dan Lawrence on June 03, 2006, 10:06:04 PM
My timers execuite when they are supposed to. For example, most of my house lights have timers that turn them off at 1:00 AM every day. At 1:00 AM, every light but 2 (on later timers) the house goes dark. This timer is on modules on three housecodes and always executes properly.

Check all your timers, the time setting is very easy to wind up with the wrong time by accident.  Before you close the timer setup, make sure all the on/off, dusk/dawn settings are what you intend before saving them and uploading to the interface.
Title: Re: Timers Slow To Execute
Post by: Charles Sullivan on June 03, 2006, 11:05:01 PM
tomj,
I have been assuming that you are downloading your schedule to the CM15A memory by clicking on Tools > Download timers and macros.  Let me know if that's not the situation.  If so, what I've already said and say below may not be accurate.

Downlaoded timers should execute within a second or two of the programmed time _if_ you have synchronized the CM15A clock as I described.  The clock you see flashing the seconds in the bar at the bottom of the AHP window is the computer time and should match exactly what you see in the Windows clock properties window.

Click on Tools in the AHP menu bar, then wait until the seconds roll over to :00 before clicking on the Hardware configuration menu item.  If you click fast enough when the system clock shows :59 you'll probably be 59 seconds off.

Verify that you haven't programmed a delay of 3 minutes in your timers.  Then try this: Re-synchronize the clock just a few minutes before the first timer of the day is programmed to execute.  (Do not re-download your schedule.)  Then record the times when the first and subsequent timers actually execute.  If the first timer is pretty close but subsequent timers are off by minutes, then I would suspect a defective clock in the CM15A.

Title: Re: Timers Slow To Execute
Post by: tom j on June 04, 2006, 02:36:07 AM
tomj,
I have been assuming that you are downloading your schedule to the CM15A memory by clicking on Tools > Download timers and macros.  Let me know if that's not the situation.  If so, what I've already said and say below may not be accurate.

Downlaoded timers should execute within a second or two of the programmed time _if_ you have synchronized the CM15A clock as I described.  The clock you see flashing the seconds in the bar at the bottom of the AHP window is the computer time and should match exactly what you see in the Windows clock properties window.

Click on Tools in the AHP menu bar, then wait until the seconds roll over to :00 before clicking on the Hardware configuration menu item.  If you click fast enough when the system clock shows :59 you'll probably be 59 seconds off.

Verify that you haven't programmed a delay of 3 minutes in your timers.  Then try this: Re-synchronize the clock just a few minutes before the first timer of the day is programmed to execute.  (Do not re-download your schedule.)  Then record the times when the first and subsequent timers actually execute.  If the first timer is pretty close but subsequent timers are off by minutes, then I would suspect a defective clock in the CM15A.



Well I really can't figure this one. I didn't touch anything and now instead of three minutes they are all just 45 seconds off, go figure? Let me check all my timers just have 5 right now just to see if they are all off by 45 seconds the last three were, so I'll have to wait until this evening to check the other two, if I find some are off by minutes I'll try what you suggested. I actually bought two of these interfaces one was defective and causing a tremendous amount of interference so much so that my DS7000 alarm system woundn't arm! so when I get the new one I can check to see if there any diffence there to. Thanks so much for the help and thanks Dan for your help as well.

Tcj
Title: Re: Timers Slow To Execute
Post by: tom j on June 04, 2006, 03:06:40 AM
My timers execuite when they are supposed to. For example, most of my house lights have timers that turn them off at 1:00 AM every day. At 1:00 AM, every light but 2 (on later timers) the house goes dark. This timer is on modules on three housecodes and always executes properly.

Check all your timers, the time setting is very easy to wind up with the wrong time by accident.  Before you close the timer setup, make sure all the on/off, dusk/dawn settings are what you intend before saving them and uploading to the interface.

Are they perfectly synchronized with your computers clock or off by up to a minute? For example are your 1:00 am timers executed exactly at 1:00 am? Thanks

Tcj
Title: Re: Timers Slow To Execute
Post by: Dan Lawrence on June 04, 2006, 01:34:44 PM
Yes, every day of the week.

When 1:00 AM arrives, all the house lights on 3 housecodes turn off.
Title: Re: Timers Slow To Execute
Post by: tom j on June 04, 2006, 10:18:05 PM
Yes, every day of the week.

When 1:00 AM arrives, all the house lights on 3 housecodes turn off.

Hi Dan did you have to do anything special? like what I'm trying to do or did it just synchronize automatically. Thanks

Tcj
Title: Re: Timers Slow To Execute
Post by: tom j on June 04, 2006, 10:26:19 PM
Say Charles seems like there's a problem as of tonight my on timers are all off by three minutes my off timers are off by 45 seconds. So do you think this is a hardware problem?  Packing up that other unit tonight hope to have it back in a week or so when I do and I download the timers that should tell me something. I'm using ma new notebook to download everything so I know that's not the problem. Thanks

Tcj
Title: Re: Timers Slow To Execute
Post by: steven r on June 04, 2006, 10:46:52 PM
...well somethings wrong all my timers are exactly three minutes late for example ...
Is the time difference constant or does it change over time.
After you sync, is your computer time the same as the AHP time? Do they both match the correct time?
What operating system do you have? I know Windows XP does an internet time set every week and can be synced manually also. There are 3rd party sync programs for your computer also.
Title: Re: Timers Slow To Execute
Post by: Charles Sullivan on June 05, 2006, 12:09:04 AM
tomj,
Assuming you haven't screwed up royally somewhere, it would on the surface appear you have a defective CM15A.  But before carving that conclusion into stone, try reprogramming your schedule completely from scratch, taking particular care not to make any mistakes.  Here's my experience:

I purchased my CM15A shortly after it was introduced, and set right out to replicate the fairly long schedule I had been using on my old CM11A.  As I was relatively unfamiliar with AHP I made a bunch of omissions and mistakes and hastened to correct them - rearranged and re-addressed modules and macros, deleted and re-created macros and timers, etc.  The resulting schedule looked correct on the PC but was a disaster when downloaded - lights turned on and off at all the wrong times or not at all, modules at addresses that never appeared in the schedule turned on or off, etc.

I started over from scratch and carefully reprogrammed my schedule.  By this time I was more familiar with AHP and less prone to make mistakes.  Then the schedule worked pretty much the way it was intended to work (at least up to a point).  This was with the very first  release of AHP.  Whatever bugs were responsible for my original disaster have hopefully been corrected in the more recent releases, but who knows.

Title: Re: Timers Slow To Execute
Post by: Charles Sullivan on June 05, 2006, 10:35:50 PM
tomj,
Assuming you haven't screwed up royally somewhere, it would on the surface appear you have a defective CM15A.  But before carving that conclusion into stone, try reprogramming your schedule completely from scratch, taking particular care not to make any mistakes.  Here's my experience:

I purchased my CM15A shortly after it was introduced, and set right out to replicate the fairly long schedule I had been using on my old CM11A.  As I was relatively unfamiliar with AHP I made a bunch of omissions and mistakes and hastened to correct them - rearranged and re-addressed modules and macros, deleted and re-created macros and timers, etc.  The resulting schedule looked correct on the PC but was a disaster when downloaded - lights turned on and off at all the wrong times or not at all, modules at addresses that never appeared in the schedule turned on or off, etc.

I started over from scratch and carefully reprogrammed my schedule.  By this time I was more familiar with AHP and less prone to make mistakes.  Then the schedule worked pretty much the way it was intended to work (at least up to a point).  This was with the very first  release of AHP.  Whatever bugs were responsible for my original disaster have hopefully been corrected in the more recent releases, but who knows.
Title: Re: Timers Slow To Execute
Post by: tom j on June 05, 2006, 11:21:13 PM
tomj,
Assuming you haven't screwed up royally somewhere, it would on the surface appear you have a defective CM15A.  But before carving that conclusion into stone, try reprogramming your schedule completely from scratch, taking particular care not to make any mistakes.  Here's my experience:

I purchased my CM15A shortly after it was introduced, and set right out to replicate the fairly long schedule I had been using on my old CM11A.  As I was relatively unfamiliar with AHP I made a bunch of omissions and mistakes and hastened to correct them - rearranged and re-addressed modules and macros, deleted and re-created macros and timers, etc.  The resulting schedule looked correct on the PC but was a disaster when downloaded - lights turned on and off at all the wrong times or not at all, modules at addresses that never appeared in the schedule turned on or off, etc.

I started over from scratch and carefully reprogrammed my schedule.  By this time I was more familiar with AHP and less prone to make mistakes.  Then the schedule worked pretty much the way it was intended to work (at least up to a point).  This was with the very first  release of AHP.  Whatever bugs were responsible for my original disaster have hopefully been corrected in the more recent releases, but who knows.


Well I've give it a try but to me it pretty straightforward really don't see anything that complicated in complying a timer, for example my 9pm timer I just clicked on at dust off at 2:am 7 days a week and it always three minutes late, just like clockwork on at 9:03. I mean come on this isn't rocket science. Think I'll erase everything and try re-downloading everything again. If that doesn't work guess I could redo everything while I'm waiting for that new Activehome hope to get the defective one out of here tomorrow.  I'm lactually eaning toward the possibility that's it's defective but we'll see. Thanks

Tcj
Title: Re: Timers Slow To Execute
Post by: steven r on June 06, 2006, 01:23:25 AM
Quote
...it always three minutes late, just like clockwork on at 9:03....
Still trying to understand this... You're saying if you set a timer to come on at 9:00 it comes on at 9:03? What time does AHP say it when it comes on 9:00 or 9:03. What time is recorded in the module history? What time does the computer say? Is the computer time the same as AHP after a sync? How often do you sync? Try syncing a few minutes before an on time. Also try waiting longer between syncs. If the CM15A is running slow, this time difference should vary. Also have you tried testing with it set to run from the computer instead of the CM15A?
Title: Re: Timers Slow To Execute
Post by: tom j on June 06, 2006, 11:32:14 PM
Quote
...it always three minutes late, just like clockwork on at 9:03....
Still trying to understand this... You're saying if you set a timer to come on at 9:00 it comes on at 9:03? What time does AHP say it when it comes on 9:00 or 9:03. What time is recorded in the module history? What time does the computer say? Is the computer time the same as AHP after a sync? How often do you sync? Try syncing a few minutes before an on time. Also try waiting longer between syncs. If the CM15A is running slow, this time difference should vary. Also have you tried testing with it set to run from the computer instead of the CM15A?

Hi Yep my timer is programed for dusk which is actually 9:07 now and it actually came on tonight at exactly 9:10 the module history said 9:10 also the thing that really appears strange is that the interface time appears t be correct what I did was check the interface time right before and after it changes from one minute to the next. for example while watching the computers time at the bottom of the Activehome Professional software screen right at XX:58 I'll click Hardware configuration and the time will be correct and the repeat the some thing the next time at XX:01 or 02 and the interface time appears to be correct if it was the interface time that being three minutes slow after checking it right after XX:00 it should have been 3 minutes off. So I can't figure what's going on x10 support suggested downloading the update but I already have the latest version of the software 3.203. So I really don't know what's going on here. As far as syncing I thought it was suppose to sync automatically? Say are your timers perfectly synced for example does if you had a 4pm timer would it occure right at 4pm  or 4 minutes and 25 seconds for example. Thanks!

Tcj
Title: Re: Timers Slow To Execute
Post by: tom j on June 06, 2006, 11:37:06 PM
Say Steve forgot to ask you what version of the software are you using and did you run the update. Thanks again
Title: Re: Timers Slow To Execute
Post by: steven r on June 07, 2006, 01:04:31 AM
...my timer is programed for dusk which is actually 9:07 now and it actually came on tonight at exactly 9:10...
Is it only the dusk timer that is off? Are the regular timers off also?
What time does AHP say the dusk is under hardware configuration?
Title: Re: Timers Slow To Execute
Post by: tom j on June 07, 2006, 08:23:59 PM
Hi Great Question! will check tonight my first timers start around 9:00pm

Tcj

Title: Re: Timers Slow To Execute
Post by: steven r on June 07, 2006, 08:29:10 PM
Hi Great Question! will check tonight my first timers start around 9:00pm...
Also let me know what time does AHP says the dusk is under hardware configuration?
Title: Re: Timers Slow To Execute
Post by: tom j on June 07, 2006, 11:59:12 PM
Hi Great Question! will check tonight my first timers start around 9:00pm...
Also let me know what time does AHP says the dusk is under hardware configuration?


Another good question will do. One thing though all my on timers are only off a minute now. I didn't change anything so go figure  :-  ???  Just downloaded the update as support suggested they said something about updating the DLL's (dynamic link libraries) I'll see if that makes any difference and report back. Thanks

Tcj
Title: Re: Timers Slow To Execute
Post by: steven r on June 08, 2006, 12:22:50 AM
Another good question will do. One thing though all my on timers are only off a minute now. I didn't change anything so go figure...
That's within the "acceptable sync error". Murphy maybe just playing with your head. Anyway keep those fingers and toes crossed.
Title: Re: Timers Slow To Execute
Post by: tom j on June 10, 2006, 12:36:35 AM
Another good question will do. One thing though all my on timers are only off a minute now. I didn't change anything so go figure...
That's within the "acceptable sync error". Murphy maybe just playing with your head. Anyway keep those fingers and toes crossed.


Well one minute maybe I could live with but now it's back to three minutes for the on times. Off times appear to be OK within a minute. Tech Support has issued a RMA, probably wait until I get that new one to see what happens, Playing with my head uh??  :- Thanks

Tcj
Title: Re: Timers Slow To Execute
Post by: steven r on June 10, 2006, 12:44:50 AM
...Tech Support has issued a RMA...
Let us know how the new unit works.
Title: Re: Timers Slow To Execute
Post by: tom j on June 11, 2006, 12:12:33 AM
...Tech Support has issued a RMA...
Let us know how the new unit works.

Yep I sure will thanks to all for your help, well at least I learned a lot. I initially thought this thing was suppose to be synced to the second like the older version but you guys set me straight. Say Steve are you up on those smart macros got a quick question for ya.

Tcj
Title: Re: Timers Slow To Execute
Post by: steven r on June 11, 2006, 12:17:42 AM
...Say Steve are you up on those smart macros got a quick question for ya....
If I'm not, someone here is likely to be able to answer your question so fire away.
Title: Re: Timers Slow To Execute
Post by: tom j on June 11, 2006, 12:34:33 AM
...Say Steve are you up on those smart macros got a quick question for ya....
If I'm not, someone here is likely to be able to answer your question so fire away.

Well I want to set up a smart macro that will turn my porch lights up from 45 % to 100% for 5 minutes and then return them back to 45%  if it receives a on signal from my B1 motion detector hidden on the porch, and I want this to only occur only at night. Think I know how to basically set that part up but I sometimes like to sit on the porch with my dog this time of year and would like to be able to cut this marco on and off with my slime line wall switch so what do I need a flag? just not sure how to set it up though. Thanks!

Tcj
Title: Re: Timers Slow To Execute
Post by: steven r on June 11, 2006, 11:42:50 AM
...Say Steve are you up on those smart macros got a quick question for ya....
If I'm not, someone here is likely to be able to answer your question so fire away.

Well I want to set up a smart macro that will turn my porch lights up from 45 % to 100% for 5 minutes and then return them back to 45%  if it receives a on signal from my B1 motion detector hidden on the porch, and I want this to only occur only at night. Think I know how to basically set that part up but I sometimes like to sit on the porch with my dog this time of year and would like to be able to cut this marco on and off with my slime line wall switch so what do I need a flag? just not sure how to set it up though. Thanks!

Tcj
I kinda have a similar thing set up for my front porch without the override. A flag would be the best way to override the macro. It might be a bit before I can post an example as I'm a bit busy right now. I still working on the placement of my sensor. (I can't screw it in place and it's fallen once.) Maybe someone else can help else can help till then.