Easy-reading introduction to Z-Wave entry control devices. Date CET Initials Name Justification

Transcription

1 Application Note Z-Wave Entry Control Basics Document No.: APL13306 Version: 3 Device Class Ver 0.9 Description: Easy-reading introduction to Z-Wave entry control devices Written By: ABR;CST;JFR;NOBRIOT;BBR Date: Reviewed By: Restrictions: BBR Public Approved by: Date CET Initials Name Justification :39:51 NTJ Niels Thybo Johansen This document is the property of Silicon Labs. The data contained herein, in whole or in part, may not be duplicated, used or disclosed outside the recipient for any purpose. This restriction does not limit the recipient's right to use information contained in the data if it is obtained from another source without restriction.

2 REVISION RECORD Doc. Rev Date By Pages affected Brief description of changes ABR ALL First revision CST Introduction Remove Notification CC from list BBR All Added Silicon Labs template silabs.com Building a more connected world. Page ii of ii

3 Z-WAVE ENTRY CONTROL BASICS Z-Wave enables a variety of monitoring and control applications. Sensors can send data to a gateway or control actuators directly based on certain criteria. Input devices like remote controls or wall mounted control devices may report button presses to a scene controller or control actuators directly. Entry control systems may comprise a combination of sensors, keypads, RFID tags, door locks and acoustic devices. Secure Z-Wave communication is employed to prevent unintended use. A Z-Wave based entry control system uses Z-Wave command classes such as Entry control Command Class for advertising user input to central control applications Indicator Command Class for providing user feedback in keypads or tag readers Door Lock Command Class for remote controlling Door Locks User Code Command Class for setting up user profiles in Door Locks for local operation An entry control input device operates as a dumb terminal. Key presses and tag data are sent to the central control application. Indicator states are managed by the central control application except for local feedback like a short beep on each button press.this allows system integrators to provide the same user feedback across different brands of entry control input devices. Another benefit of this approach is that the user immediately notices if the connection to the central control application is down. Buttons are treated in two categories. Credential buttons are the decimal digits 0-9, the letters A-Z as well as special characters like * and #. Command buttons are buttons like <Enter>, <Arm> or <Disarm>. The entry control input device may operate in two operational modes. In streaming mode, the device immediately notifies the central application each time an event occurs, whether it is a key press or an RFID tag. In caching mode, manually entered digits and RFID tag data are cached locally and sent to the central application when a command button is pressed. Digits are also sent if the cache reaches its limit or if the cache times out. The following examples outline how similar entry control input devices may be used in different usage scenarios depending on the behavior of the central control application. The order of button presses and which buttons need to be pressed are manufacturer specific. This document presents examples of how systems may be designed. The examples address several approaches based on different philosophies. Other approaches may exist. A designer will have to choose one consistent approach. silabs.com Building a more connected world. Page 1 of 7

4 Example 1 shows how a user gets access to a protected area by presenting his RFID tag. Example 1: Using RFID tag to unlock door The user holds the RFID tag close to the tag reader. The tag reader notifies the gateway that an RFID tag was detected. The gateway approves the RFID credentials. The gateway sends an instruction to the door lock to open for a limited period and it instructs the tag reader to turn on its Ready LED for 5 seconds. silabs.com Building a more connected world. Page 2 of 7

5 Example 2 shows how a user disables the alarm by first presenting the RFID tag and then pushing the Home button. Example 2: Using RFID and then <Home> to disable alarm The user holds the RFID tag close to the keypad. The keypad notifies the gateway that an RFID tag was detected. The gateway approves the RFID credentials. The gateway instructs the keypad to flash its Armed LED for 5 seconds to alert the user that the alarm is currently armed and that a button press is required to disarm it. The user pushes the Home button to request that the alarm is disabled. The keypad notifies the gateway that the Home button was pressed. The gateway disarms the alarm state and it instructs the keypad to turn on its Disarmed LED for 5 seconds. silabs.com Building a more connected world. Page 3 of 7

6 Example 3 shows how a user disables the alarm by first pushing the Home button and then authenticating the operation with an RFID tag. Example 3: Using <Home> and then RFID to disable alarm The user pushes the Home button to request that the alarm is disabled. The keypad notifies the gateway that the Home button was pressed. The gateway instructs the keypad to flash its Armed LED for 5 seconds to alert the user that the alarm is currently armed and that additional input is required to disarm it. The user holds the RFID tag close to the keypad. The keypad notifies the gateway that an RFID tag was detected. The gateway approves the RFID credentials. The gateway disarms the alarm state and it instructs the keypad to turn on its Disarmed LED for 5 seconds. silabs.com Building a more connected world. Page 4 of 7

7 Example 4 shows how a user disables the alarm by first pushing a number of digits and then pushing the Home button. Example 4: Pushing digits and then <Home> to disable alarm The user pushes the first digit of his personal PIN. The keypad notifies the gateway that the user has started entering digits. The gateway instructs the keypad to flash its Armed LED for 5 seconds to alert the user that the alarm is currently armed and that additional input is required to disarm it. The user pushes the remaining digits of his personal PIN and then pushes the Home button to request that the alarm is disabled. The keypad notifies the gateway that the Home button was pressed and attaches the cached digits. The gateway approves the cached digits as a valid PIN. The gateway disarms the alarm state and it instructs the keypad to turn on its Disarmed LED for 5 silabs.com Building a more connected world. Page 5 of 7

8 Example 5 shows how a user changes the alarm state by just pushing four digits. Example 5: Pushing four digits to enable alarm The user pushes the first digit of his personal PIN to request that the alarm state is changed. The keypad notifies the gateway that the user has started entering digits. The gateway instructs the keypad to flash its Disarmed LED for 5 seconds to alert the user that the alarm is currently disarmed and that additional input is required to arm it. The user pushes the remaining digits of his personal PIN. After four button presses, the keypad notifies the gateway that digits have been received. The gateway approves the cached digits as a valid PIN. The gateway then arms the alarm and it instructs the tag reader to turn on its Armed LED for 5 seconds. silabs.com Building a more connected world. Page 6 of 7

9 REFERENCES [1] SDS12657 Z-Wave Command Class Specification, A-M [2] SDS12652 Z-Wave Command Class Specification, N-Z [3] SDS11847 Z-Wave Plus Device Types Specification [4] SDS11846 Z-Wave Plus Role Types Specification silabs.com Building a more connected world. Page 7 of 7

10 Smart. Connected. Energy-Friendly. Products Quality Support and Community community.silabs.com Disclaimer Silicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and "Typical" parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice and limitation to product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Silicon Labs shall have no liability for the consequences of use of the information supplied herein. This document does not imply or express copyright licenses granted hereunder to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any Life Support System without the specific written consent of Silicon Labs. A "Life Support System" is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons. Trademark Information Silicon Laboratories Inc., Silicon Laboratories, Silicon Labs, SiLabs and the Silicon Labs logo, Bluegiga, Bluegiga Logo, Clockbuilder, CMEMS, DSPLL, EFM, EFM32, EFR, Ember, Energy Micro, Energy Micro logo and combinations thereof, "the world s most energy friendly microcontrollers", Ember, EZLink, EZRadio, EZRadioPRO, Gecko, ISOmodem, Micrium, Precision32, ProSLIC, Simplicity Studio, SiPHY, Telegesis, the Telegesis Logo, USBXpress, Zentri, Z-Wave and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. All other products or brand names mentioned herein are trademarks of their respective holders. Silicon Laboratories Inc. 400 West Cesar Chavez Austin, TX USA