Print

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

[Walt2]

In trying to do some sort of workarounds with my 2-Way modules, I have tried to code up
macros using the Advanced Functions' "Extended Code" step. 

However, it seems that once the macros get to the "Extended Code" step, they stop
executing.  I mean, any steps after the "Extended Code" step are never executed.

Has anyone else noticed this ? ? ? ?

[Charles Sullivan]

In trying to do some sort of workarounds with my 2-Way modules, I have tried to code up
macros using the Advanced Functions' "Extended Code" step. 

However, it seems that once the macros get to the "Extended Code" step, they stop
executing.  I mean, any steps after the "Extended Code" step are never executed.

Has anyone else noticed this ? ? ? ?

Is that also the case if the macro with the Extended Code command is downloaded to the CM15A memory?
Or just if executed from AHP?  Or both?

[Walt2]

This is downloaded to the CM15A.

After stumbling upon this, I did a simple test macro that did nothing but send an Extended Code step, followed by a simple Appliance 'on' step (a different unit code).  The Appliance module never turned 'on', nor did the Activity Monitor show that such a code was even sent.

Oh, the Activity Monitor did show the macro being executed and that the Extended Code was sent.

[Charles Sullivan]

This is downloaded to the CM15A.

After stumbling upon this, I did a simple test macro that did nothing but send an Extended Code step, followed by a simple Appliance 'on' step (a different unit code).  The Appliance module never turned 'on', nor did the Activity Monitor show that such a code was even sent.

Oh, the Activity Monitor did show the macro being executed and that the Extended Code was sent.

I'm assuming you triggered the macro by sending a signal from an external source, not just clicking the "run macro" on the icon, right?

Try putting a delay of zero seconds after the Extended Code command in the macro.  This has helped with other commands, e.g., RF commands, which terminated after the first command.

(I'd try this but my Windows system is on the fritz right now.)

[Dan Lawrence]

Sounds like it's time for the old Backup and Reformat Game.   

[Walt2]

Try putting a delay of zero seconds after the Extended Code command in the macro.  This has helped with other commands, e.g., RF commands, which terminated after the first command.

Sorry for the delay in getting back here.

I tried that, and it kind of worked.  However, I now have the reverse problem.  The macro with the Extended Code, plus delays, now doesn't exit.  It appears to "run" into the macro which follows it.   It was easy for me to tell which macro, due to its unique sequencing of modules.  I never had a macro do that before (fail to exit).  It was quite weird!

[Charles Sullivan]

Try putting a delay of zero seconds after the Extended Code command in the macro.  This has helped with other commands, e.g., RF commands, which terminated after the first command.

Sorry for the delay in getting back here.

I tried that, and it kind of worked.  However, I now have the reverse problem.  The macro with the Extended Code, plus delays, now doesn't exit.  It appears to "run" into the macro which follows it.   It was easy for me to tell which macro, due to its unique sequencing of modules.  I never had a macro do that before (fail to exit).  It was quite weird!

Another AHP bug?  Good grief! 

Try putting a zero delay after the last code in the macro, and if that doesn't help, another zero delay before the first code in the 'run-into' macro.

BTW, I've had a bunch of weird things happen when I made a bunch of changes and/or initial errors in the programmed schedule.  When I reprogrammed it starting from scratch and taking special care to get things exactly right the first time, the weirdness went away.
This was with an early release of AHP and the bug may (or may not) have been fixed by now.

If you're technically inclined, an annotated copy of the downloaded EEPROM image is saved by AHP as the file
c:\Documents and Settings\All Users\Application Data\Active Home Professional\ahpeeprom_w.txt
There may be something obviously different in the problem macros versus well-behaved macros.