Print

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

[omar]

Hello, just wondering when we should be
expecting the next update and what are the
changes on it.

[X10 Pro]

Mark: The next update should be this week, if
all goes well. It will include fixes to the
Activity Monitor problems, several fixes for
iWitness, some new advanced PLC commands for
Macros, and a few other things.

[donald mcmow]

Can you give us an idea as to what the new
macro commands are? And maybe some ideas on
how to use them.

[roger1818]

X10 Pro:  Sounds Awesome!  I am looking
forward to it.

[X10 Pro]

You'll use the new macro commands in a
fashion similar to the RF commands. They're
generic commands for addressing, extended
codes, and preset dim. Their main purpose is
to make it easier for you to work with some
of the modules that we don't make -- ones
that need different command sets or structures.

[SteveRF]

X10 Pro,
So we don't get too far off the thread title,
I am looking forward to the next release.
Maybe it will fix my status reporting error.
Glad your crew is adding some new PLC
commands for macro's.  We all like new
features that will give us more versatility
withour CM15a's.  Thanks !
SteveRF

[peabrain]

X10Pro, The week is almost up, how's the
outlook for the upgrade release this week?

[X10 Pro]

Well, it's not quite ready, so it's going to
have to be next week.

[peabrain]

Thanks for the update, Looking forward next
week then.

[arf1410]

Ok back to the "next update," I'm curious
what sort of FIXES people think are still
needed.  I don't want to know additional
features you would like to see, but for the
sake of my question, what sort of CURRENT
features / functions do you think still need
to be fixed via a software update?

[richard the 1st]

One feature of X10 that needs thorough
attention is the Activity Monitor.
The latest version has all CM15A actions as
Macro entered. If anything this is an area
that needs some serious work.

[roger1818]

One bug that has been around since I
started using AHP at 3.175 is with a macro
of mine which does the following:

C ALL_OFF
C5 ABSOLUTE 100%
B11
B12
B13
B ON
Delay 20 min
C ALL_OFF
B11 OFF

If I change the second step to either:

C5 ABSOLUTE 70%
or
C5 DIM 30%
(the exact percentages don’t matter)

I end up getting a C ALL_LIGHTS_ON after
dimming C5 and before turning on B11,
12&13.  This macro has been changed a few
times since the beginning (different unit
codes on B and I used to turn individual
lights off on C instead of the ALL_OFFs,
but I have always seen the same behavior.
I saw the same behavior with both my
original and diagnostic units.  This is
more of an annoyance than anything since it
does work properly with C5 ABSOLUTE 100%
but I should be able to dim C5 in the macro
if I want to.

For what it is worth, C5 is a wall switch
module.

[donald mcmow]

Roger: Have you tryed ptting a delay (0
seconds) in your macro. This would cause
commands to individually processed rather
than grouped to-gether. I wonder if there
is a command priority in a grouping (ie:
On/Off commands executed before Dims) no
matter what the macro order is.

[roger1818]

Donald:  No I haven’t tried putting in a
zero second delay.  It is an interesting
idea and I will give that a try.  If that
doesn’t work, I will try a 1 second delay
instead.  My gut feeling is that it is
related to the transition from Dimming on C
and addressing units on B.

[Charles Sullivan]

Roger H:
Regarding your "demon" macro:
Are you downloading to the CM15A EEPROM or
running from the PC?  Timer or Triggered?