Z-Wave 500系列应用开发指南：API与6.50版本详解

5星 · 超过95%的资源需积分: 10 123 浏览量更新于2024-07-22 收藏 4.1MB PDF 举报

Z-Wave通信是一种无线通信技术，专用于智能家居和物联网（IoT）应用中设备之间的低功耗、长距离、网络化的连接。《Z-Wave 500系列应用编程指南v6.50.00 Beta》是一本针对开发基于Z-Wave 500系列产品的应用程序的专业手册。该指南由JFR、MVO、PSH、EFH、JBU和ABR撰写，于2013年6月3日发布，经过了CHL、PSH和BBR的审查。该文档详细介绍了如何利用Z-Wave开发者套件v6.5x的API进行应用程序开发。Z-Wave 500系列是Z-Wave标准的后续版本，它相较于早期版本如Z-Wave 400系列，在性能、兼容性和安全性方面有所提升。开发人员可以借助这份指南学习如何构建高效、可靠且符合Z-Wave网络协议的应用程序，以便实现家居自动化控制、安防监控等场景中的设备交互。书中可能涵盖了以下关键知识点： 1. **Z-Wave网络架构**：介绍Z-Wave网络的工作原理，包括星形拓扑结构、节点类型（如主控制器、路由器和终端设备）以及它们在通信过程中的角色。 2. **API接口详解**：解释API的不同组件和功能，包括数据包格式、命令类、属性类、安全机制等，帮助开发者理解和操作Z-Wave设备的行为。 3. **设备发现与配置**：指导如何通过Z-Wave网络发现和配置新设备，包括网络初始化、设备配对和固件更新。 4. **错误处理与诊断**：提供故障排除的方法，如何识别并解决网络连接问题、数据传输错误等问题。 5. **电源管理与节能策略**：由于Z-Wave强调低功耗，指南会介绍如何优化设备的休眠模式和通信策略以节省电池寿命。 6. **安全与认证**：探讨Z-Wave的安全特性，如加密技术、节点认证和防篡改措施，确保通信安全。 7. **示例代码与开发流程**：包含实用的开发步骤和示例代码，帮助读者快速上手并理解实际编程实践。 8. **版本兼容性与升级**：对于从Z-Wave 400系列向500系列的迁移，可能涉及到软件升级和向后兼容性策略。 9. **行业规范与标准遵循**：确保开发者了解Z-Wave联盟的最新规定，保证产品符合国际标准。 10. **保密条款**：强调知识产权保护，明确指出数据不得未经授权复制或对外公开，除非来源于无限制的其他来源。《Z-Wave 500系列应用编程指南v6.50.00 Beta》是一份实用的资源，旨在帮助开发者深入理解Z-Wave通信技术，以创建出符合现代智能家居需求的高质量应用程序。

INS12308-1 Z-Wave 500 Series Appl. Prg. Guide v6.50.00 Beta 2013-06-03

Sigma Designs Inc.

Z-Wave software Architecture

Page 5 of 418

CONFIDENTIAL

3.1 Z-Wave System Startup Code

The Z-Wave modules include the system startup function (main). The Z-Wave system startup function

first initializes the Z-Wave hardware and then calls the application hardware initialization function

ApplicationInitHW. Then initializing the Z-Wave software (including the software timer used by the timer

module) and finally calling the application software initialization function ApplicationInitSW. Execution

then proceeds in the Z-Wave main loop.

3.2 Z-Wave Main Loop

The Z-Wave main loop will call the list of Z-Wave protocol functions, including the ApplicationPoll

function and the ApplicationCommandHandler function (if a frame was received) in round robin order.

The functions must therefore be designed to return to the caller as fast as possible to allow the MCU to

do other tasks. Busy loops are not allowed. This will make it possible to receive Z-Wave data, transfer

data via the UART and check user-activated buttons, etc. “simultaneously”. In order not to disrupt the

radio communication and the protocol, no application function must execute code for more than 5ms

without returning.

For production testing the application can be forced into the ApplicationTestPoll function instead of the

ApplicationPoll function.

3.3 Z-Wave Protocol Layers

When transmission of data to another node is requested, the Z-Wave protocol layer adds a frame header

and a checksum to the data before transmission. The protocol layer also handles frame retransmissions,

as well as routing of frames through “repeater” nodes to Z-Wave nodes that are not within direct RF

communication reach. When the frame transmission is completed, an application-specified transmit

complete callback function is called. The transmission complete callback function includes a parameter

that indicates the transmission result. The transmission complete callback function indicate also when

the next frame can be send to avoid overwriting the transmit queue.

The Z-Wave frame receiver module (within the MAC layer) can include more than one frame receive

buffer, so the upper layers can interpret one frame while the next frame is received.

3.1 Z-Wave Routing Principles

The Z-Wave protocol use source routing, which is a technique whereby the sender of a frame specifies

the exact route the frame must take to reach the destination node. Source routing assumes that the

sender knows the topology of the network, and can therefore determine a route having a minimum

number of hops. The Z-Wave protocol supports up to four repeaters between sender and destination

node. Routing can also be used to reach FLiRS destination nodes. Source routing allows implementation

of a leightweight protocol by avoiding distributed topologies in all repeaters. Nodes containing the

topology can also assign routes to a topology-less node enabling it to communicate with a number of

destination nodes using routes.

In case sender fails to reach destination node using routes an explorer mechanism can be launched on

demand to discover a working route to the destination node in question. The explorer mechanism builds

on AODV routing with adjustments for source routing and memory footprint. Explorer frames implement

managed multi-hop broadcast forwarding and returns a working route to sender as result. The application

payload piggybacks on explorer frame to reduce latency.

INS12308-1 Z-Wave 500 Series Appl. Prg. Guide v6.50.00 Beta 2013-06-03

Sigma Designs Inc.

Z-Wave software Architecture

Page 6 of 418

CONFIDENTIAL

The routing algorithm store information about successful attempts to reach a destination node avoiding

repetition of previously failed attempts. The last successful route used between sender and destination

node are stored in NVM and is called Last Working Route (LWR). The LWR list comprises of 232

destination nodes having up to one route/direct each. The LWR can also contain direct attempts.

Updating LWR happens in the following situations:

 When receiving a successful explorer frame route.

 When receiving a successful routed/direct request from another node.

 When receiving a successful acknowledge for a transmitted explorer frame.

 When receiving a successful acknowledge for a transmitted routed/direct frame.

The LWR is removed from the LWR list in case it fails.

The routing attempts depend on the Z-Wave library and transmit options used in the node, for details

refer to section 3.7.

The source routing algorithm does not alter the topology due to failed attempts or store any statistics

regarding link quality.

3.2 Z-Wave Application Layer

The application layer provides the interface to the communications environment which is used by the

application process. The application software is located in the hardware initialization function

ApplicationInitHW, software initialization function ApplicationInitSW, application state machine (called

from the Z-Wave main poll loop) ApplicationPoll, command complete callback functions, and a receive

command handler function ApplicationCommandHandler.

The application implements communication on application level with other nodes in the network. On

application level, a framework is defined of Device and Command Classes [1] to obtain interoperability

between Z-Wave enabled products from different vendors. The basic structure of these commands

provides the capability to set parameters in a node and to request parameters from a node responding

with a report containing the requested parameters. The Device and Command Classes are defined in the

header file ZW_classcmd.h.

Wireless communication is by nature unreliable because a well-defined coverage area simply does not

exist since propagation characteristics are dynamic and unpredictable. The Z-Wave protocol minimizes

these "noise and distortion" problems by using a transmission mechanisms of the frame there include

two re-transmissions to ensure reliable communication. In addition are single casts acknowledged by the

receiving node so the application is notified about how the transmission went. No precautions can

unfortunately prevent that multiple copies of the same frame are passed to the application. Therefore is it

very important to implement a robust state machine on application level there can handle multiple copies

of the same frame. Below are shown a couple of examples how this can happen:

INS12308-1 Z-Wave 500 Series Appl. Prg. Guide v6.50.00 Beta 2013-06-03

Sigma Designs Inc.

Z-Wave software Architecture

Page 9 of 418

CONFIDENTIAL

3.4 Z-Wave Hardware Timers

The 100/200/300/400/500 Series Z-Wave Single Chips have a number of hardware timers/counters.

Some are reserved by the protocol and others are free to be used by the application as shown in the

table below:

Table 1. 100/200/300/400/500 Series Z-Wave Single Chips hardware timer allocation

200 Series

300 Series

400 Series

500 Series

TIMER0

Protocol

system clock

Protocol

system clock

Available for

the application

Available for

the application

TIMER1

Available for

the application

Available for

the application

Used by the

protocol

Available for

the application

GPTIMER

Available for

the application

Available for

the application

Available for

the application

Available for

the application

The TIMER0 and TIMER1 are standard 8051 timers/counters. TIMER1 is used by the protocol.

3.5 Z-Wave Hardware Interrupts

Application interrupt service routines (ISR) must use 8051 register bank 0. However, do not use USING 0

attribute when declaring ISR‟s. The Z-Wave protocol uses 8051 register bank 1 for protocol ISR‟s, see

table below regarding application ISR availability:

Table 2. 200/300/400 Series Z-Wave Single Chip Application ISR availability

200 Series

300 Series

400 Series

500 Series

INUM_INT1

INUM_TIMER1

INUM_SERIAL

INUM_SPI

INUM_TRIAC

INUM_GP_TIMER

INUM_ADC

INUM_INT1

INUM_TIMER1

INUM_SERIAL

INUM_SPI

INUM_TRIAC

INUM_GP_TIMER

INUM_ADC

INUM_INT0

INUM_TIMER0

INUM_SERIAL0

INUM_SPI0

INUM_TRIAC

INUM_GP_TIMER

INUM_ADC

INUM_USB

INUM_IR

INUM_INT0

INUM_INT1

INUM_TIMER0

INUM_SERIAL0

INUM_SPI0

INUM_TRIAC

INUM_GP_TIMER

INUM_ADC

INUM_USB

INUM_IR

It is not allowed to disable interrupts more than it takes to received 8 bits, which is around 0.8ms at

9.6kbps.

Refer to ZW020x, ZW030x.h, ZW040x.h and ZW050x.h header files with respect to ISR definitions. For

an example, refer to UART ISR in serial API sample application.

剩余442页未读，继续阅读

galaxysilverstar

粉丝: 2
资源: 12

Z-Wave 500系列应用开发指南：API与6.50版本详解

Z-Wave IP Communication

物联网建设短距离无线通信技术分析.zip

A Series of Standalone Products Communication SDK manual

Wireless_Communication_Protocol.rar_wireless

Wavefront compensation simulation of modulating retroreflector free-space optical link utilizing micro corner-cube-reflector arrays

行业资料-电子功用-信息家电控制系统的介绍分析.rar

行业分类-电子-关于应用于数字家庭中的PLC总线控制电路的介绍分析.rar

资料-通信标准信息服务.zip

qt-openzwave:适用于OpenZWave的QT5包装器

基于Wi-Fi与电力载波的智能家居系统设计与实现.pdf

最新资源