Print

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

[****W]

I am having a problem with my delay times
in macros on AHP 3.172.  For some of my
macros I have delays between events in the
macro.

It seems that the first time delay is
accurate and each sucessive delay increases
exponentially.  Has anyone else had a
problem with this?

I am not using conditions on these
particular marcros, just a simple trigger.

[Burdy]

Yes, I think I'm seeing something similar,
although I am using conditionals.  I have a
macro that sets a flag bit as the final step
after a 1 minute delay, and noticed it
never got set until many minutes after it
should have. Repeating the macro, it never
got set at all-- I assumed it had died,
although the AHP wasn't locked up and was
executing other macros (without delays) OK.
Something funny seems to be going on (also
using 3.172).

[jdelapen]

I have exactly the same situation.  I think
the problem resides in the fact that AHP
3.172 is adding the accumulated times
instead of the individual delay times in
macros (delay times are shown inside a box
in the macros view and accumulated times
are shown in each step to the left of
the “macro chain”).  This is the cause for
erratic behavior and also explains why the
delays grow exponentially.  The difference
between the information you can see in the
GUI and the one that is loaded to the
interface can be found in the
ahpeeprom_w.txt file, which shows the
information that has been loaded to the
eeprom.

If this is the case, I believe it should be
fairly easy to come up with a fix from X10
programmers very soon (at least that is
what I hope…)

[jdelapen]

I have exactly the same situation.  I think
the problem resides in the fact that AHP
3.172 is adding the accumulated times
instead of the individual delay times in
macros (delay times are shown inside a box
in the macros view and accumulated times
are shown in each step to the left of
the “macro chain”).  This is the cause for
erratic behavior and also explains why the
delays grow exponentially.  The difference
between the information you can see in the
GUI and the one that is loaded to the
interface can be found in the
ahpeeprom_w.txt file, which shows the
information that has been loaded to the
eeprom.

If this is the case, I believe it should be
fairly easy to come up with a fix from X10
programmers very soon (at least that is
what I hope…)

[Burdy]

I can't find the ahpeeprom_w.txt file
anywhere on either of my machines (Win98 &
Win98SE); does this file only appear on
machines using XP??

[jdelapen]

Burdy,

I don’t know where is located that file on
Win98 because I use WinXP.  In XP the file
is located here:
C:/Documents and Settings/All
Users/Application Data/Active Home
Professional

Hope this helps…

[Burdy]

Thanks.  I don't have that directory (though
there is a C:\Windows\All Users\Application
Data\X10 Settings directory, and a
C:\Program Files\Common Files\X10\Common,
but the file isn't there).  I can't find it
anywhre on the machine.  Must be a Win98 vs.
XP thing.

[X10 Pro]

I didn't think we changed anything related to
macro delays, but it sounds like something is
wrong. We'll take a look and hopefully have
something soon.

[holger]

AHP Team,
please read my direct e-mails to AHP
support from 5th Dec2004 + the attachements.
Macro timers are suddenly shortend with
Vers. 3.172 to less than one hour !
They were previosly correct 4:10 ~> 240 Min
in the/my AHPXXXX.txt file < 3.172
Holger

[holger]

AHP Team,
please read my direct e-mails to AHP
support from 5th Dec2004 + the attachements.
Macro timers are suddenly shortend with
Vers. 3.172 to less than one hour !
They were previosly correct 4:10 ~> 240 Min
in the/my AHPXXXX.txt file < 3.172
Holger

[holger]

AHP Team,
please read my direct e-mails to AHP
support from 5th Dec2004 + the attachements.
Macro timers are suddenly shortend with
Vers. 3.172 to less than one hour !
They were previosly correct 4:10 ~> 240 Min
in the/my AHPXXXX.txt file < 3.172
Holger

[X10 Pro]

Holger: I saw your e-mail, and you should
have a response. We've fixed one problem
related to the delay, and are looking at the
other one you reported.