TI公司的Z-Stack开发者指南：Zigbee协议栈详解

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

"TI公司的Z-Stack Developer's Guide是一份详细介绍了Zigbee协议栈开发的指南，涵盖了从基础到高级的各种主题。这份文档自2006年首次发布以来，经过多次更新以适应Zigbee技术的发展，包括对ZigBee 2007和ZigBee PRO特性的增强，以及对安全、网络管理和MAC层的改进。" Z-Stack Developer Guide是TI公司为开发者提供的一份关键参考资料，旨在帮助他们理解和应用Zigbee协议栈进行无线网络设计和开发。Zigbee是一种基于IEEE 802.15.4标准的低功耗、短距离无线通信技术，广泛应用于智能家居、物联网(IoT)设备和工业自动化等领域。此文档的早期版本（1.0）提供了Zigbee协议栈的基础知识，包括ZDOMessageRequest的介绍。随着版本的升级，文档逐步加入了对ZigBee 2007和ZigBee PRO特性的支持，这些特性增强了网络的稳定性和安全性，如在1.2版本中的更新。此外，文档还关注了预配置密钥管理，如1.3版本中更新的zgPreConfigKeys的位置，以及网络管理模块的名称变更（1.5版本）。安全性是Z-Stack的重要部分，体现在1.7版本中对多个预配置信任中心链接密钥的支持和1.8版本新增的安全密钥数据管理章节。网络性能的优化也在不断进行，例如1.6版本更新了4.1.1.1节，可能涉及MAC层的某个特定功能，而1.10版本则对2.1和2.1.1节进行了编辑性修改，可能涉及到网络拓扑或设备角色的描述。物理层的扩展在1.9版本中被提及，添加了Extended PANIDs（扩展个人区域网络标识符）的章节，这允许更大的网络规模和更复杂的网络结构。此外，1.11版本增加了5.6节，专门讨论了Router Off-Net（路由器离网）的场景，这对于理解如何处理网络断开或临时离线的路由器至关重要。 Z-Stack Developer's Guide是开发者深入理解Zigbee协议栈、构建高效可靠的Zigbee网络的重要参考资料，它详尽地阐述了从网络配置、设备角色、安全性到网络管理的各个层面，是实现Zigbee解决方案的关键工具。随着技术的不断发展，该文档也持续更新，确保开发者能够掌握最新的技术和最佳实践。

展开

Z-Stack Developer's Guide SWRA176 Version 1.13

3.2.2 Stochastic Addressing

ZigBee PRO uses a stochastic (random) addressing scheme for assigning the network addresses. This addressing

scheme randomly assigns short addresses to new devices, and then uses the rest of the devices in the network to

ensure that there are no duplicate addresses. When a device joins, it receives its randomly generated address from

its parent. The new network node then generates a “Device Announce” (which contains its new short address and its

extended address) to the rest of the network. If there is another device with the same short address, a node (router)

in the network will send out a broadcast “Network Status – Address Conflict” to the entire network and all devices

with the conflicting short address will change its short address. When the conflicted devices change their address

they issue their own “Device Announce” to check their new address for conflicts within the network.

End devices do not participate in the “Address Conflict”. Their parents do that for them. If an “Address Conflict”

occurs for an end device, its parent will issue the end device a “Rejoin Response” message to change the end

device’s short address and the end device issues a “Device Announce” to check their new address for conflicts

within the network.

When a “Device Announce” is received, the association and binding tables are updated with the new short address,

routing table information is not updated (new routes must be established). If a parent determines that the “Device

Announce” pertains to one of its end device children, but it didn’t come directly from the child, the parent will

assume that the child moved to another parent.

3.3 Addressing in Z-Stack

In order to send data to a device on the ZigBee network, the application generally uses the AF_DataRequest()

function. The destination device to which the packet is to be sent is of type afAddrType_t (defined in

ZComDef.h).

typedef struct

{

union

{

uint16 shortAddr;

ZLongAddr_t extAddr;

} addr;

afAddrMode_t addrMode;

byte endPoint;

} afAddrType_t;

Note that in addition to the network address, the address mode parameter also needs to be specified. The destination

address mode can take one of the following values (AF address modes are defined in AF.h)

typedef enum

{

afAddrNotPresent = AddrNotPresent,

afAddr16Bit = Addr16Bit,

afAddr64Bit = Addr64Bit,

afAddrGroup = AddrGroup,

afAddrBroadcast = AddrBroadcast

} afAddrMode_t;

The address mode parameter is necessary because, in ZigBee, packets can be unicast, multicast or broadcast. A

unicast packet is sent to a single device, a multicast packet is destined to a group of devices and a broadcast packet is

generally sent to all devices in the network. This is explained in more detail below.

Z-Stack Developer's Guide SWRA176 Version 1.13

3.3.1 Unicast

This is the normal addressing mode and is used to send a packet to a single device whose network address is known.

The addrMode is set to Addr16Bit and the destination network address is carried in the packet.

3.3.2 Indirect

This is when the application is not aware of the final destination of the packet. The mode is set to

AddrNotPresent and the destination address is not specified. Instead, the destination is looked up from a

“binding table” that resides in the stack of the sending device. This feature is called Source binding (see later section

for details on binding).

When the packet is sent down to the stack, the destination address and end point is looked up from the binding table

and used. The packet is then treated as a regular unicast packet. If more than one destination device is found in the

binding table, a copy of the packet is sent to each of them. If no binding entry is found, the packet will not be sent.

3.3.3 Broadcast

This address mode is used when the application wants to send a packet to all devices in the network. The address

mode is set to AddrBroadcast and the destination address can be set to one of the following broadcast addresses:

NWK_BROADCAST_SHORTADDR_DEVALL (0xFFFF) – the message will be sent to all devices in the network

(includes sleeping devices). For sleeping devices, the message is held at its parent until the sleeping device polls for

it or the message is timed out (NWK_INDIRECT_MSG_TIMEOUT in f8wConfig.cfg).

NWK_BROADCAST_SHORTADDR_DEVRXON (0xFFFD) – the message will be sent to all devices that have the

receiver on when idle (RXONWHENIDLE). That is, all devices except sleeping devices.

NWK_BROADCAST_SHORTADDR_DEVZCZR (0xFFFC) – the message is sent to all routers (including the

coordinator ).

3.3.4 Group Addressing

This address mode is used when the application wants to send a packet to a group of devices. The address mode is

set to afAddrGroup and the addr.shortAddr is set to the group identifier.

Before using this feature, groups must be defined in the network, see aps_AddGroup() in the Z-Stack API [2]

document.

Note that groups can also be used in conjunction with indirect addressing. The destination address found in the

binding table can be either a unicast or a group address. Also note that broadcast addressing is simply a special case

of group addressing where the groups are setup ahead of time.

Sample code for a device to add itself to a group with identifier 1:

aps_Group_t group;

// Assign yourself to group 1

group.ID = 0x0001;

group.name[0] = 6; // First byte is string length

osal_memcpy( &(group.name[1]), “Group1”, 6);

aps_AddGroup( SAMPLEAPP_ENDPOINT, &group );

3.4 Important Device Addresses

An application may want to know the address of its device and that of its parent. Use the following functions to get

this device’s address, defined in Z-Stack API [2] document:

剩余56页未读，继续阅读

身份认证购VIP最低享 7 折!

30元优惠券

dragonwhl

粉丝: 1

TI公司的Z-Stack开发者指南：Zigbee协议栈详解

zigbee_Z-Stack 3.0 开发者中文手册.rar

基于ZigBee3.0开发实战手册.rar

Z-Stack Developer's Guide _F8W-2006-0022_

Z-Stack 3.0 Developer's Guide.pdf

13_基于Z-Stack的串口通信.rar_HDD_z-stack

Z-Stack 3.0.2-.7z.zip_Z-STACK 3.0.2_Z-STACK-3.0.2_z-stack 3_z-st

Z-Stack Developer's Guide

elk-stack-guide-cn.pdf

ChatGPT-Prompt-template-Full-Stack Software Developer.pdf 全栈工程师

ZStack-MSP2618-2.2.0-1.3.0文档：Z-Stack Developer's Guide

最新资源