Saturday April 29th 2017

  

May 23, 2011

What Is Basic Repeater Slave?

The slave nodes are devices that do not contain routing tables. The so-called routing slave nodes and enhanced routing slave nodes can contain a number of pre-configured routes (assigned to them by a controller). Any slave node can act as a repeater for frames going to other nodes. The only requirement for being able to act as repeater is that the node is in listening state. This requires that the node is permanently powered, and in order to limit battery consumption, this means that only main-powered nodes will act as repeaters in most practical installations. Battery-operated slaves that do not listen continually are disregarded by controllers when they calculate routes.

There are three types of slave nodes. The slave node type is able to receive frames and reply if necessary. The slave node cannot host pre-configured routes to other nodes. The slave node is typically used for devices that only require input (and report status if polled) and do not generate frames unsolicited. An example of a device using this type could be a power outlet.

Routing Slave

The routing slave can host a number of routes for reaching other slaves or controllers. Such routes are called “Return Routes.” Routing Slaves can use these routes to communicate with either controllers or other slave nodes. The routing slave can either be A/C powered or battery powered. If the routing slave is A/C powered it is used as a repeater in the Z-Wave network, otherwise it will be disregarded when routes are calculated. The routing slave functionality is used for devices that need to report unsolicited status or alarms. An example of a routing slave node could be a thermostat or a passive infrared (PIR) movement sensor. A wall switch might also be a routing slave and could then be used to control small lighting scenes, or to establish a kind of “virtual” three-way switching.

Frequently Listening Routing Slave (FLiRS)

A special case of a battery-powered routing slave is the rrequently listening routing slave (FLiRS). This is a routing slave configured to listen for a wakeup beam in every wakeup interval. This enables other nodes to wake up the FLiRS node and send a message to it. One example of a FLiRS node is as chime node in a wireless doorbell system.

Enhanced Slave

The enhanced slave has the same basic functionality as a routing slave node, but more software components are available because of more features on the hardware. Enhanced slave nodes have software support for External EEPROM and an RTC2. An example of a device using this type of slave nodes could be a thermostat.

Zensor Net Routing Slave

The Zensor Net routing slave node is basically a routing slave node configured as FLiRS with the additional functionalities:

• Zensor Net binding

• Zensor Net flooding

The Zensor Net is an alternative network to the classic Z-Wave network having its own binding method and a mechanism to flood messages to the entire Zensor Net. An example of a Zensor Net routing slave node could be a smoke detector.

Previous Topic:

Twitter Feed