Download the Z-Wave SDK 6.81 for secured Z-Wave applications. These documents are necessary for robust and secured Z-Wave application development using SDK 6.81
|SDK 6.81.01 Support Documentation (Release Date 22/03/2018)|
|Z-Wave 500 Series SDK v 6.81.01 Software Release Note|
|Known Test Observations SDK v 6.81.01|
|Working in 500 Series Environment User Guide|
|Z-Wave Plus Application Framework v 6.81.0x|
|Z-Wave 500 Series Application Programmers Guide v 6.81.00|
|Z-Wave 500 Series SDK Contents v 6.81.01|
|Z-Wave SDK 6.81: Serial API Support Documentation
|Serial API Host Appl. Prg. Guide|
|Z-Wave PC controller v 5.30 Support Documentation
|Z-Wave PC based Controller v 5 User Guide|
|Z-Wave DLL v 5 User Guide|
|Software Release Note|
|SmartStart Support Documentation|
|SmartStart Labeling Guide|
|SmartStart Production Control|
The SDK 6.81 includes the following features:
Z-Wave SmartStart Secure Interoperability Made Easy
Z-Wave SmartStart builds upon S2 security to gain all the benefits of secure communication between devices, and makes it easy.
Gateway SDK 6.81 introduced the DSK concept and the QR representation of the digits to allow for easy out-of-band transfer of the authentication data from device to gateway. Z-Wave SmartStart takes this one step further by allowing the end device to be automatically included by a gateway that has the authentication data.
Devices can now exist in a provisioning list of the gateways so users are aware of them in the pre-included state. When they are powered on they will automatically be included the network and the state of the device can be updated in the gateway user interface.
For gateways, Z-Wave SmartStart consist of three new features:
End devices supporting Z-Wave SmartStart will send inclusion request frames at a predictable interval. To inform nearby gateways that they are ready for inclusion. To conserve battery power and avoid network congestion the interval between requests will be increased over time. Z-Wave gateways will use two inclusion request messages to include a device. The first message to match authentication and the second to quickly include the device. This allows end devices to return to sleep faster preserving battery.
The Z-Wave protocol and Application Framework handles this communication when Z-Wave SmartStart is enabled for a product.
New QR Format
For Z-Wave SmartStart to work, the gateway needs to know that a device added supports Z-Wave SmartStart. The S2 generation 1 QR provides the DSK, but does not offer means to identify if the device is Z-Wave SmartStart capable. To solve this information shortage, a new generation 2 QR format has been specified. The new format includes device capabilities, including what inclusion methods are supported. In addition the new device data also includes information such as Icon Type and Manufacturer ID. This information allows gateways to offer a much better user experience of a device prior to inclusion.
The new generation 2 QR format also use more optimized encoding. This allows the QR label to contain all the additional information about the device and still be smaller than the generation 1 format.
FLiRS Multicast Groups
In addition to Z-Wave SmartStart, the protocol release also includes updates to the FLiRS wakeup options.
Controllers can now send multicast to FLiRS nodes so they react simultaneously to a command if they are in direct range of the controller.
The FLiRS multicast is based on a special destination address, so nodes that are not a part of a FLiRS multicast group will not wake up when a FLiRS multicast frame is sent.
The Z Wave header files and libraries are the software files needed for building a Z Wave enabled product. The files are organized in directories used for building Z Wave controllers and slaves respectively.
- Z-Wave\include: contains Z Wave header files needed for interfacing to the Z-Wave protocol and hardware peripherals that reside on the 500 Series Single Chip.
- Z-Wave\IO_defines: contains hardware definition files needed for building an application e.g. the development controller application.
- lib\bootloader_ZW050x: contains a bootloader that is used in connection with OTA firmware update.
- lib\controller_bridge_ZW050x: contains all files needed for building a Z Wave bridge controller application.
- lib\controller_portable_ZW050x: contains all files needed for building a Z Wave controller application.
- lib\controller_static_ZW050x: contains all files needed for building a Z Wave static controller application.
- lib\controller_static_norep_ZW050x: contains all files needed for building a Z Wave static controller application without repeater functionality.
- lib\controller_static_single_ZW050x: contains all files needed for building a Z Wave static single controller application.
- lib\slave_enhanced_232_ZW050x: contains all files needed for building a Z Wave enhanced 232 slave node application.
- lib\slave_prodtest_dut_ZW050x: contains all files needed for building a production test DUT application on a Z Wave module.
- lib\slave_prodtest_gen_ZW050x: contains all files needed for building a production test generator application on a Z Wave module.
- lib\slave_routing_ZW050x: contains all files needed for building a Z Wave routing slave node application on a Z Wave module.
- lib\ext_nvm: contains external non-volatile memory (NVM) drivers, which can be used to substitute default driver in library.
- lib\init_vars: contains an init_vars.obj object file, which replaces the standard Keil initialization procedure.
- lib\rf_freq: contains all the possible RF initialization object files ZW_rf_050x_xx.obj.
Z-Wave Application Framework
You can write robust Z-Wave application code using the Z-Wave Application Framework. It comes with number of well defined module for better security, parsing, frame composition, I/O handling, battery monitoring and firmware update.
If you are building a new application we highly recommend using Z-Wave application framework.
Z-Wave SDK comes with a number of tools to build, debug and test your applications.
Some tools like Z-Wave Programmer are not bundled with SDK anymore, learn more about other tools.
|Enhanced Reliability Test Tool (ERTT)||Use ERTT scripts for reliability test of your application.|
|FixBootCRC||FixBootCRC tool is used when building bootable applications|
|FixPatchCRC||FixPatchCRC tool is used when building patchable applications.|
|HexTools||HexTools is used when building patchable applications.|
|IMAToolBox||The IMA Tool Box supports an installation and maintenance procedure, which can ensure an easy installation and provide an operational qualification of the installation.|
|IncDep||It is a python script that is used for making dependency files when building the applications.|
|Make||The directory contains a DOS/Windows version of the GNU make utility.|
|MergeHex||MergeHex tool helps to merge two files in Intel hex format.|
|Micro RF LinkX||Micro RF LinkX helps to verify the RF performance of a device without the overhead of the Z-Wave protocol.|
|uVisionProjectGenerator||uVision Project Generator program generates uVision projects when running the makefile from a DOS prompt.|
|Zniffer||Zniffer is a development tool for capturing Z Wave RF communication and presenting the frames in a graphical user interface on a PC.|
Z-Wave SDK for 500 series supports a number of different boards.
|Development Board||Module/Chip||Hex File Name|
Use the Z-Wave porting guides to port your applications Z-Wave 500 Series platform.