Print

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

[PajamaGuy]

3)   Macro Grouping – AHP allows you to “group” units when using standard commands without delays between them.  Basically AHP addresses all of the units and then sends one “action” command so they activate at the same time.  While this is still possible with the LM14a interface, it will activate the “resume dim” feature of the new switches and is therefore not recommended as explained above.  Using the “ON at 99%” extended code command will not allow units to be grouped.

Boiler - Great write-up - THANKS! 

Question - (it's Monday and I've spent all weekend building a new PC - so I'm a tad fuzzy....)
Macro Grouping - I'm not sure I understand what point you're making.  From reading your whole post, it seems to me that using "LM14A" for ALL dimmable lamps is the way to go.  Especially if it's faster execution with less PLC traffic.  But what's the issue with grouping?  Does it work or not?  Should one insert "0" second delays or not? 

Sorry for being thick this morning - I need more coffee....

[Boiler]

Question - (it's Monday and I've spent all weekend building a new PC - so I'm a tad fuzzy....)
Macro Grouping - I'm not sure I understand what point you're making.  From reading your whole post, it seems to me that using "LM14A" for ALL dimmable lamps is the way to go.  Especially if it's faster execution with less PLC traffic.  But what's the issue with grouping?  Does it work or not?  Should one insert "0" second delays or not? 

Sorry for being thick this morning - I need more coffee....

PajamaGuy,

No apologies - please.  I'm still recovering from a emergency rebuild of my Fathers' PC - I understand.

With the "old" ws467/Lm465 interface, grouping was a way to get all of the addressed units to respond at the same time.  It also provided faster execution.  Unfortunately, the extended code protocol only allows you to perform a "preset dim" on one addressed unit at a time.  The communication and lamp response will be faster, but one unit will activate at a time (serial execution).  This will occur regardless of whether or not delays are inserted.

I expanded my macro example a bit to explain more clearly -


In the above example, all of the devices are "new" WS467's.  The first 3 use the standard WS467 interface.  The last 2 use the LM14a extended code interface.  All of them are executed without delays. 

The activity monitor shows the LM14a interfaced units being executed one at a time.  This is a constraint of the protocol.  It is much faster, and your lamps will go directly to the programmed level (no going to 100% then dimming back like the old modules), but they will activate one at a time.

The M11-M13 units show how the "old" interface could group units.  All three units are addressed, then a single bright 100%/Dim 50% commands activate all three units at the same time.

Event    Date/Time                   Action          Data
0    10/06/2008 4:06:33 pm    Transmit    M14 Extended Code 6b 31 (LM14a#1)
1    10/06/2008 4:06:34 pm    Transmit    M15 Extended Code 6b 31 (LM14a#2)
2    10/06/2008 4:06:36 pm    Transmit    M11 (WS467#3)
3    10/06/2008 4:06:36 pm    Transmit    M12 (WS467#1 Standard)
4    10/06/2008 4:06:36 pm    Transmit    M13 (WS467#2 Standard)
5    10/06/2008 4:06:37 pm    Transmit    M On (WS467#3, WS467#1 Standard, WS467#2 Standard)
6    10/06/2008 4:06:37 pm    Transmit    M Dim 50(WS467#3, WS467#1 Standard, WS467#2 Standard)

Please keep in mind that I am in no way a "fan" of the bright/dim sequences.  I don't use them because they tend to give my HCA02 repeater fits.  However, I do recognize that other people do use these commands and wanted to present a "complete" picture of the positives and negatives of the LM14a extended code interface.

There is a method for activating multiple LM14a units (soft start modules) simultaneously and at any desired level - it's called extended code group commands (scenes).  The new soft start units support this feature and it's very "next level".  Tutorial in process...

Boiler

[Dan Lawrence]

Now, all we need is for X10 to rebuild AHP to accept both old and new modules with no fuss/muss.

[dave w]

I can't understand why X10 at least does not do a "bubble gum, bailing wire" fix like a sticker on the new soft start wall switches that says "If using Active Home Pro, identify this module as a LM14". It would eliminate a lot of new user confusion and product returns. Right now their total inaction for almost a year just makes the company look like it is run by morons.

[Dan Lawrence]

I don't think the company is run by morons, but it seems somebody in Las Vegas gets the "Not Paying Attention" Award.  X10 has lost the proverbial boatload of programmers, witness the length of time to upgrade AHP from 3.204 to 3.228.

Your sticker idea is good, but how long would that take?

[Boiler]

I can't understand why X10 at least does not do a "bubble gum, bailing wire" fix like a sticker on the new soft start wall switches that says "If using Active Home Pro, identify this module as a LM14". It would eliminate a lot of new user confusion and product returns. Right now their total inaction for almost a year just makes the company look like it is run by morons.

Bingo - that's the really frustrating part.

OK, so X10 was caught off guard with the new module "enhancements".  I suppose I can understand that.  However, their inaction after the fact is compounding the problem.  As you indicated, a simple sticker would alleviate many of the problems.

If this had been handled differently we would be chanting praises for these new modules with high end features.  As it is, we're in damage control mode trying to subdue the (justified) frustration of new and old users alike.

Such a waste

[Brian H]

At least X10Pro updated their descriptions on their web site to indicate Soft Start versions. One even got a new model number.