8.4.1. Central Static Controller (CSC)¶
The Central Static Controller Role Type is intended for always powered devices which are capable of operating as a central controller. The CSC will be the central device for most network communications and other devices will rely on it for unsolicited information via the lifeline association to the CSC (which is also the SIS). This will enable the user to receive key information without having to perform major network configuration tasks.
The CSC is typically a router, central gateway or some sort of central communication panel.
8.4.1.1. CSC Protocol Requirements¶
\requirement{RT:01.11.0001.1}{0}
The CSC MUST respect requirements described in Section 8.2.
\requirement{RT:01.11.0002.1}{0}
The CSC MUST support the Static Update Controller (SUC) and SUC node ID Server (SIS) functions.
\requirement{RT:01.11.0003.1}{0}
The CSC MUST be mains powered and MAY have a battery back-up.
\requirement{RT:01.11.0004.1}{0}
The CSC MUST set the listening flag to 1 in its NIF.
\requirement{RT:01.11.0005.1}{0}
The CSC MUST support and control the S0 and S2 Command Classes.
\requirement{RT:01.11.0006.2}{0}
The CSC MUST support the following network roles:
SIS
Secondary controller (if Learn Mode is supported)
Inclusion controller (if Learn Mode is supported)
8.4.1.1.1. If first node in the network¶
\requirement{RT:01.11.0007.3}{0}
If the CSC is the first node in the network, it MUST set itself the SIS role and MUST support the following network functions:
Include new nodes (“Add mode”)
Exclude nodes
Remove failing nodes
\requirement{RT:01.13.0001.2}{0}
Additionally, it MAY support the following network function:
Replace failing nodes
Learn Mode
\requirement{RT:01.11.0008.1}{0}
It MUST NOT be possible to activate Learn Mode if the CSC is the SIS and other nodes are included in the network.
8.4.1.2. CSC setup¶
8.4.1.2.1. Inclusion process¶
\requirement{RT:01.12.0001.1}{0}
It is RECOMMENDED to use soft buttons for activating learn mode and add mode on a CSC Role Type.
8.4.1.2.2. Lifeline configuration¶
When including a node,
\requirement{RT:01.11.0009.1}{0}
if the CSC is the SIS: it MUST set itself as the Association group ID 1 (Lifeline) destination.
\requirement{RT:01.13.0003.1}{0}
if the CSC is not the SIS: it MAY set the SIS’ NodeID as the Association group ID 1 (Lifeline) destination.
\requirement{RT:01.11.0016.1}{0}
The CSC MUST assign a return route for the SIS after setting the lifeline of End Node Role Types.
Details and requirements about establishing the Lifeline are provided in Association Group Information (AGI) Command Class, version 1-3 and Multi Channel Association Command Class, version 2-5.
8.4.1.2.3. CSC including a SSC, PC, RPC or NAEN¶
Battery considerations
If the CSC is the SIS and the included node is of Role Type RPC:
\requirement{RT:01.11.000A.1}{0}
The CSC MUST configure the Wake Up Interval Set Command destination NodeID to its NodeID.
\requirement{RT:01.11.000B.1}{0}
The CSC MUST send a Wake Up No More Information Command when the CSC has no more command to transmit.
8.4.1.2.4. CSC including a PEN, LSEN, RSEN or WOEEN¶
Battery considerations
\requirement{RT:01.11.000D.1}{0}
If the CSC is the SIS and the included node is of Role Type PEN, RSEN or WOEEN, the CSC MUST:
configure the Wake Up Interval Set Command destination NodeID to its NodeID.
send a Wake Up No More Information Command when the CSC has no more command to transmit.
If the CSC is the SIS and the included node is of Role Type PEN:
\requirement{RT:01.11.000E.1}{4}
If the node advertises Wake-Up Capabilities (Wake-Up Command Class, version 2 or newer), the Wake Up Interval Set Command Seconds field MUST be within the allowed range
\requirement{RT:01.12.0002.1}{0}
If the CSC is not the SIS, it SHOULD NOT send a Wake Up Interval Set Command to the included node.
\requirement{RT:01.11.0010.1}{0}
If the CSC is not the SIS and sends a Wake Up Interval Set Command, the destination NodeID MUST be the SIS’ NodeID.
8.4.1.2.5. CSC including an AOEN¶
Battery considerations
None.
8.4.1.2.6. CSC including another CSC¶
\requirement{RT:01.11.0013.1}{0}
If the CSC is included by another CSC, the included CSC MUST take the Inclusion Controller role and MUST support the following network functions:
Include new nodes (“Add mode”)
Exclude nodes
Learn mode
Remove failing node
\requirement{RT:01.13.0002.1}{0}
Additionally, it MAY support the following network function:
Replace failing node
Battery considerations
None.
8.4.1.2.7. CSC included by a PC, RPC, SSC¶
\requirement{RT:01.11.0014.1}{0}
The CSC MUST accept to take the SIS role when a PC, RPC or SSC assigns it to the included CSC.
Lifeline configuration
\requirement{RT:01.12.0003.1}{4}
If the CSC was assigned the SIS role, previously added nodes may have no lifeline associations. The CSC SHOULD create lifeline associations in all existing nodes that are directly reachable.
Battery considerations
None.
8.4.1.3. CSC Runtime Configuration¶
\requirement{RT:01.11.0015.1}{0}
The CSC MUST instruct a reporting node (RPC, RSEN, PEN) to return to sleep after application data has been delivered to the node. This is done by sending a Wake Up No More Information Command. An illustration is given in Figure 8.12.
8.4.1.4. CSC Runtime Communication¶
No requirements
