Print

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

[emil]

Can multiple macros run simultaneously? If
a macro is started, how does it handle
being restarted before finished? Does it
abort and start again? Does it continue and
start another instance of it?
What's behind all the questions is
operation of a Motion Sensor and Palm Pad.
I have my macros locked out so they only
run the first time by using the condition
if a lamp is turned on already.
Unfortunately I'm having a heck of a time
getting consistency of operation. I'll push
the PalmPad and it seems like I get
multiple hits. I monitor the macro
operation on the main screen and see the
correct macro called but then also
the "else" macro almost immediately after.
Help !!!

[poursha]

I starts again.  I tested it.

Rob

[anonymous]

Multiple hits is a problem.
The problems as I have seen it are that
Issues:
1. if it gets hit too fast it will get
confused or interfers with another running
macro.
Windy sunny day with a motion
detector, shadows set off Motion detector

2. Flags can only be tested and set from
macros stored in CM-15a

3. Camera commands only work from macros
stored on PC
4. Nested Macros or calling one macro from
another is not supported by AHP
sometimes can get to work using
phantom modules but is not reliable

To capture with a camera(Video Commands
don't work except on rare occasions) I do
the

following:

a. Stored macro N1 checks if flag is set, if
not then sets flag and runs macor O4 located
in a CM-11a.  This is an attempt to only
have N1 get hit multiple times and not the
macro
that controls the camera recording(N4)

b.  Macro O4 runs Macro N4 stored on the PC
(in AHP) that does the recording of still
captures.
The last command runs Macro O16 (Stored
in cm-11a)

c. Macro O16 runs Macro N16 stored on CM-15a
that resets the flag.

Works most of the time except that AHP still
caused a reboot after a few hours.
and sometimes N1 is hit so many times it
confuses N4 and the flag does not get reset
so at that

point nothing gets recorded.

[emil]

Thanks for the replies guys.

Seems I had multiple problems, the first I
solved by putting 1 sec. delays between the
commands. I'm not familiar how robust the
X10 protocol is but it seems if a command
gets clobbered by another there is no retry
mechanism, my solution was to put some time
between commands as mentioned in other
threads. Hopefully I will learn of a way to
eliminate the delays because I would like
the macro to execute faster. Maybe I just
need to try some cases again and eliminate
some delays, I possibly don't need them
after evey line.

The second multiple hit things I solved with
the smart macro option to qualify the macro
at startup. Since the macros would turn on a
light, I conditioned the macro to run only
if the light was off so it would only run
the first time. This just uses the lamp
condition as a flag like others do.

I would sure like to have some sort of
document describing the limitations and
details of operation so I know what I'm
working with and then can program to fit
within it's constraints.
I think all the ads and marketing hype are
pretty funny but sometimes you just need
some real technical detail!

Emil