Print

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

[marineau]

Hi,

I have 1 SS13A in kitchen, and another SS13A in bedroom. I setted this switch to B2,B3,B4 for a kitchen and B5,B6,B7 for bedroom.
I use a TM751 to get a RF signal !

I explain my problem:
1 - I press on B2 button in kitchen at 01:00:00
2 - My wife press on B5 button in bedrrom at 01:00:01 
3 - I press on DIM button in kitchen at 01:00:02 for dim light setted to B2 !
A problem is that a B5 DIM instead a B2

Why does a DIM function use a code in bedroom instead a kitchen!

Does my Tm751 is fail if it use a last button pressed in a house ?

Thanks

[Puck]

marineau: This is normal operation. (FWIW) The dim/brighten buttons only send un-addressed dim/brighten commands. The last module to be addressed will respond to the dim/brighten command. That's why you can't make your SS13A's dim/brighten commands specific to that room.

[Brian H]

So true; as I have seen it myself.
Last address sent is the module or modules; if you have more on the same address; that react to the dim or brighten command.
Also since last X10 module addressed if turned off and then a dim is sent. Goto full bright and then dim. That means if you turn Off a module and someone then pushed the dim button. The modules just turned off; would go on and start dimming; if they are a dimming type.

[TakeTheActive]

...The last module(s) to be addressed will respond to the dim/brighten command...

...Last address sent is the module or modules; if you have more on the same address; that react to the dim or brighten command...

To (attempt to) clarify what Puck and Brian H are saying, take a look at the:

• Activity Monitor: AHP / CM15A
  .
• Communications Log: AH / CM11A
  

[/color][/b]
I believe that Puck meant to say modules and Brian H meant to say DIFFERENT addresses (i.e. HouseCode / UnitCode combination).

For example, if you (somehow) send (*EASY* via the old BSR/SEARS/STANLEY Wired Controllers ):

• A1 A2 A3 A4 DIM *OR*
  .
• A1 B2 C3 D4 DIM
  

[/color][/b]
 - they would *ALL* DIM simultaneously! [*PROVIDED* that AH/AHP agree that they are all the *SAME* module "type" (not model, but 'internal' "type").]

EXPERIMENT and then review the Monitor / Log entries.

Clear as MUD, eh?

[steven r]

...
1 - I press on B2 button in kitchen at 01:00:00
2 - My wife press on B5 button in bedroom at 01:00:01 
3 - I press on DIM button in kitchen at 01:00:02 for dim light setted to B2 !
...

As others have mentioned, a dim command dims the last code addressed.
How often does this situation happen to you in real life?   

[marineau]

...
1 - I press on B2 button in kitchen at 01:00:00
2 - My wife press on B5 button in bedroom at 01:00:01 
3 - I press on DIM button in kitchen at 01:00:02 for dim light setted to B2 !
...

As others have mentioned, a dim command dims the last code addressed.
How often does this situation happen to you in real life?   

I noticed this problem in my many Macro... But in a real life, this problem is each night, because near on my bed, I have a mini controller, and if I press a DIM, it don't work for my lamp because I have two Motion Sensor in my bedroom set to on another address to run a Macro... Now that I know this, I will react consequently ...
Thanks you to all for infos !!!

[Charles Sullivan]

For example, if you (somehow) send (*EASY* via the old BSR/SEARS/STANLEY Wired Controllers ):

• A1 A2 A3 A4 DIM *OR*
  .
• A1 B2 C3 D4 DIM
  

[/color][/b]
 - they would *ALL* DIM simultaneously! [*PROVIDED* that AH/AHP agree that they are all the *SAME* module "type" (not model, but 'internal' "type").]

I agree with your statement about "A1 A2 A3 A4 DIM"  dimming simultaneously, but how can that be true for "A1 B2 C3 D4 DIM" ?
Wouldn't there have to be a separate DIM command for each housecode?

[steven r]

...it don't work for my lamp because I have two Motion Sensor in my bedroom set to on another address to run a Macro...

This is one of the reasons I keep my motion sensors on a different HC than the lights they control and let the macros work out things.
e.g. The motion sensor at the front porch is on HC "I" while the front light is on HC "C". This also allows me to vary how the light responds. Most of the time I have the light brighten to 100% for about 5 minutes. On Halloween, however, I have the light dim and the fog machine run when the kids approach.

[dave w]

I agree with your statement about "A1 A2 A3 A4 DIM"  dimming simultaneously, but how can that be true for "A1 B2 C3 D4 DIM" ?
Wouldn't there have to be a separate DIM command for each housecode?

No, and you can verify this with a Maxi controller. When address only are sent (house code/unit code - i.e. A1, B2, C3, etc), those modules on those addresses are essentially told "obey the NEXT function(s) code(s) you see". They stay in that mode until they "see" another (different from their own) HCUC which puts them back in the "ignore" mode.

[Charles Sullivan]

I agree with your statement about "A1 A2 A3 A4 DIM"  dimming simultaneously, but how can that be true for "A1 B2 C3 D4 DIM" ?
Wouldn't there have to be a separate DIM command for each housecode?

No, and you can verify this with a Maxi controller. When address only are sent (house code/unit code - i.e. A1, B2, C3, etc), those modules on those addresses are essentially told "obey the NEXT function(s) code(s) you see". They stay in that mode until they "see" another (different from their own) HCUC which puts them back in the "ignore" mode.

If that were to be true, there would be no need for a function to be associated with a specific Housecode.

Here's what I'm seeing with an X-10  MaxiController and two X-10 LM465 Lamp Modules set to A1 and B2 with incandescent lamps attached.
First, make sure that everything is Off and un-addressed:
Transmit:
    A  AllUnitsOff
    B  AllUnitsOff
Now transmit:
   A1
   B2
   B  On
Results: Lamp B2 turns On; Lamp A1 remains Off.
Transmit:
   A  On
Result: Lamp A1 turns  On; Lamp B2 remains On.
Transmit:
   A  Off
Result: Lamp A1 turns Off; Lamp B2 remains On
Transmit:
   B  Off
Result: Lamp B2 turns Off.

Here are the addressing rules for ordinary X-10 modules like the LM465:
1. A module becomes addressed when it receives a Housecode|Unitcode matching its own.
2. An addressed module responds to (supported) functions on its own Housecode and remains addressed until it becomes un-addressed.
3. A module becomes un-addressed either when it receives a different Unitcode on its own Housecode following any function on that same Housecode -- or -- when it receives the AllUnitsOff function on that same Housecode.

Note: The addressing rules for modules which support the old-style Preset Dim 1 and Preset Dim 2 functions, like Smarthome's 'Linc modules, are different and more complex.

[dave w]

Charles
Yup you are absolutly correct. A complete brain f_rt on my part. You can not address across house codes and expect a function to work, since function code includes the house code.

Thats what happens when I try and do two things at once (in this case; chewing food and thinking).

  Thanks!