How does an M1 associate serial interfaces to thermostats?

[gcimmino]

I hope this isn't a stupid question. I have another thread where I'm still working on getting an Omnistat 2000 to work.

I originally had an XSP as XSP address #1, hooked to an RCS thermostat (thermostat 1).
I moved that XSP to XSP address #2 to accommodate adding a new XSP (now XSP address 1) to support an Omnistat ('stat address 1 on XSP #1).

So my question is: The RCS was "thermostat 1" in RP. I assumed that the Oministat would be "thermostat 2". Is that true? Did the M1 "add the new XSP" in order, or did it re-associate based on the XSP address order? In which case the RCS is now thermostat 2 in RP and the Omni is now 1.

Or am I just confused? :wacko:

Thanks

 

[gcimmino]

More info:

The Omnistat is "unit #1", hooked to XSP #1.
The RCS is "unit #1", hooked to XSP #2.

Should I re-address the RCS to start at "network address 2"?

In other words, is the M1 thermostat # in RP the network or unit address of the device regardless of which XSP it is connected to? If so, that's my problem..

 

[gcimmino]

I changed the RCS to become unit #2 and all is working. So it looks like thermostats have to have globally unique addresses.

Since it was #1, I had to modify existing rules to point to the different number.

 

[Spanky]

Each thermostat must have a unique address because the M1 addresses them globally.