Print

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

[bkenobi]

I was curious if there is anything written in the standard that indicates how X10 modules should operate when different house codes are used in the same area.  Specifically, if you were to send the following commands, what should theoretically happen:

Code: [Select]

A1
AON
B1
BON
AOFF
I'm curious if modules simply ignore anything that isn't from their own set HC or would they "reset" and require a HC/UC command be sent prior to the command?  I can test this with my own modules, but I was hoping there might be an official statement in the spec since that's what every module should be designed for even if mine work differently.

My guess (which is all I can do without an official spec) is that modules set to HC A will ignore anything from other HC's.  This would be especially important if more than one system was set up in a shared electrical zone.  If one person were to use HC A, then someone else could use HC B without any impact, correct?

Note:  I think I asked this or a variation of this question about a year ago, but I can't find that thread for some reason (too many to sort through I guess).

[dhouston]

See ADDRESS/FUNCTION atop p2 of...
http://davehouston.org/X10%20xtdcode.pdf

[bkenobi]

Excellent, that's what I needed.  That makes sense except that it doesn't explicitly state that an address on a different house code will or will not "unaddress" the previously "addressed" modules.  Since it's a different HC, I could see modules simply ignoring all other communication and only listening for it's HC.  But, I could see it potentially being implemented where any HC could "unaddress" as well.  In that respect, the spec seems a little ambiguous (to me anyway).

[dhouston]

I see no ambiguity in, "It becomes 'unaddressed' by the first 'address' message after a
command...".

[bkenobi]

Fair enough.  Thanks!