Print

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

[billy]

I beleive what your seeing is the macro
being fired by: RF signal received by the
TM751, the TM751 sends the command PLC,
CM15A sees the PLC command and fires the
macro.  This is also the cause of the delay,
TM751 converts the RF to PLC, CM15A receives
and has to process.  Ever notice the delay
in motion sensor response when using the
TM751 instead of direct RF to the CM15A?

Just my $.02

[martin]

Billy: I know what you mean but in my
experiment I didn’t use any TM751.

So PalmPad set on House Code M, RF picked up
by CM15A only.

M1 On = Turns lamp module M1 On
M2 On = Triggers Macro called “Test” which
turns lamp module M1 On

After pressing M1 On, slight delay, lamp
module M1 turns On.
After pressing M2 On, no noticeable delay,
lamp module M1 turns On.

[anonymous]

Martin,
What is your Monitored HC and transceived HC
(s) set at?
I'll try the same test tonight and see if I
get the same results.

[martin]

Create a new simple AHP configuration with
the following:

Hardware Configuration; Monitored House Code
M and Transceived House Code M.
Add new Lamp module M1.
Create “Test” macro with trigger M2 On that
will turn lamp module M1 On.

Test M1 On & M2 On with PalmPad.

I’m pretty sure the slight delay is due to
the transceived House Code validation that
macros don’t have to go  through.

[martin]

Ok, I don’t get it. Just cleared my
interface and downloaded my test
configuration and now there is no noticeable
delay when I try both!
Is it because my regular configuration has
64 macros (80% memory left)?

[billy]

Martin,
It may be that the CM15A has to parse
through it' list macros to find the ones
that trigger with the input. I wonder if the
macros defined 1st would trigger faster than
say the 63rd macro you have defined?
Interesting!