The Z-Wave driver is designed to act as a Z-Wave secondary controller, operating in one of three modes: as a Static Controller, a Static Update Controller (SUC), or a SUC ID Server (SIS) on the Z-Wave network. If possible, it is highly recommended that you configure the network so that the JACE is an SIS or SUC. This provides the best overall performance and ease of installation.
If battery-powered devices are going to be used on the Z-Wave network, consider this SUC or SIS operation as a requirement.
For related details, see About JACE Z-Wave operation modes.
The two main methods use these different install procedures:
To install the JACE as an SUC or SIS
The portable primary controller used to install Z-Wave devices must support SUC and/or SIS functionality. The JACE must be the first Z-Wave device installed, in order for it to operate as an SUC or SIS. It is assumed that the JACE has already been configured, and it has a running station with a ZWaveNetwork.
Use the following procedure to install the JACE on the Z-Wave network as an SUC or SIS device.
Uninstall any Z-Wave devices previously installed, using the portable primary controller.
It is recommended you reset the portable primary controller back to its factory defaults.
This should remove any network/node information, ensuring that the JACE will be the first node added (as a result of transferring the primary role to it, later in this procedure).
Open the property sheet of the ZWaveNetwork.
The property “Configure As SIS” is used to select the JACE to act as either an SIS or SUC.
The default value is true (SIS). If SUC operation is needed, change to false, and .
Transfer the primary controller role to the JACE.
Double-click the network, to bring up the device manager (ZWave Device Manager).
Prepare the portable primary controller to initiate a replicate (send), to shift the primary role.
Although it may seem the primary controller has nothing to send on replication (it was cleared in Step 2), in fact this results in the JACE being added as the first node, with the node ID 2.
In the ZWave Device Manager, click the button .
Within a few seconds, from the primary controller, complete the replication send / primary role shift, as started in substep 2
After this replication completes, the “Home ID” property of the ZWaveNetwork should match that of the primary controller, and its “Interface Node Id” property should be 2.
Transfer back to the primary controller. If SIS operation has been selected, this make the portable primary controller a “Z-Wave Inclusion Controller”.
Using the portable primary controller, initiate a replicate receive.
In the ZWave Device Manager, click the button .
(This substep must be done within 30 seconds of the previous substep.)
This should leave the JACE operating in the desired SIS or SUC role.
Now you can use the portable primary controller to install other Z-Wave devices. As each device is installed, the JACE is automatically notified. The Z-Wave driver automatically adds the appropriate ZWaveDevice component, including child components and proxy points, according to the device’s supported Z-Wave command classes.
By operating in the SIS or SUC mode, this eliminates the need for any additional replications to the JACE.
For a summary of how all the command classes are modeled, including the dynamically added components, see Z-Wave command classes supported.
To install the JACE as a Static Controller
Z-Wave driver versions prior to 3.5.25.7 only supported this mode of operation. However, it is recommended that the JACE be
configured as an SIS or SUC instead. See To install the JACE as an SUC or SIS. If these modes are not available, the JACE will still work as a Static Controller. However, issues with battery-powered
devices are likely, as described in Z-Wave jobsite requirements.
The Z-Wave network of devices should already be installed, using a portable primary controller. This primary controller must support replication to a secondary controller (in this case, the JACE). It is assumed that the JACE has already been configured, an it has a running station with a ZWaveNetwork.
Use the following procedure to install the JACE on the network, while replicating network information from the portable primary controller.
Using the portable primary controller used to install Z-Wave devices on that network, prepare to initiate a replicate (send).
Double-click the ZWaveNetwork, to bring up the device manager (ZWave Device Manager).
In the ZWave Device Manager, click the button .
After a second or two, while holding the Z-Wave portable primary controller near the JACE, initiate the replicate send. (You have up 30 seconds after clicking .)
This automatically starts a discovery job that performs the following sequence:
Transfers the Z-Wave network topology from the Z-Wave portable primary controller to the Z-Wave secondary controller (JACE).
Adds a ZWaveDevice (ZWaveDevice or ZWaveThermostat) for each slave Z-Wave device that is discovered.
Reads the Z-Wave node information from each device, to determine the command classes supported by that device.
For each command class that the device supports (and that the driver also supports), adds an associated component under the device object, or proxy points,
When the discovery job completes, the station should have all the components and points to provide monitor and control functions for each of the network’s Z-Wave devices. For each device, the Z-Wave driver automatically adds the appropriate ZWaveDevice component, including child components and proxy points, according to the device’s supported Z-Wave command classes.
If battery-powered devices are involved, it is recommended to force each battery-powered device to “wake up” 3 times for the
JACE to learn all of its command classes. Typically, you do this by pressing a button or switch on a battery-powered device.
For a summary of how all the command classes are modeled, including the dynamically added components, see Z-Wave command classes supported.
Copyright © 2000-2014 Tridium Inc. All rights reserved.