When specifying a routing mechanism, there are some important attributes that will determine the success or failure of a message reaching it's target. Some of the more obvious attributes used are the destination address, destination endpoint, and group ID. However, some of the more complex attributes are covered below.
The Radius attribute represents the maximum number of hops a message will be allowed to traverse when being routed to a target device.
R1. 'Every device has an associated depth that indicates the minimum number of hops a transmitted frame must travel, using only parent-child links, to reach the ZigBee coordinator. The ZigBee coordinator itself has a depth of 0, while its children have a depth of 1. Multi-hop networks have a maximum depth that is greater than 1. The ZigBee coordinator also determines the maximum depth of the network.'
Setting the Radius attribute value to 0x00 will result in the sum of 'nwkMaxDepth' * 2 being used instead. The nwkMaxDepth value is how many hops it would take to reach the furthest away child device in network (populated during the discovery phase).
Example:
R1. 'The non-member radius attributes indicates the range of a multicast when relayed by devices that are not members of the destination group. Receiving devices that are members of the destination group will set this field to the value of the MaxNonmemberRadius(calculated at stack level) sub-field. The originating device and receiving devices that are not members of the destination group will discard the frame if the non-member radius has value 0 and will decrement the field if the non-member radius field has a value in the range 0x01 through 0x06. A value of 0x07 indicates an infinite range and is not decremented.'
Example:
The following responses and acks are possible when sending a command, depending on wether they are enabled or not. Below you will find a concise overview of each.
Status Response:
The Status Response is a response that is sent from either the Module to the Host or from the Host to the Module upon receipt of a command from the RHA protocol.
ZDO/ZCL Response Received:
Certain commands, such as the Read Attribute commands expect a response from a target device when sent. The ZCL/ZDO Response Received command is sent by the Module to the Host on reception of ZCL/ZDO message from the network. That is, the command is generated if the Host had configured an outgoing Send ZCL/ZDO Unicast or Send ZCL/ZDO Broadcast with Response Options indicating that a response is expected (i.e. enable reception of ZCL/ZDO Response Received with corresponding Transaction Sequence Number.
APS Acks:
The ZCL/ZDO APS Ack command is sent by the Module to the Host on reception of an equivalent acknowledgement from the network, triggered by the initial transmission of a ZCL/ZDO message that required an APS Ack among its Response Options. The Module will also generate the command when a given acknowledgment is not received and therefore times out.
Some responses or acks will not be sent, depending on the the type of table routing used. Below you will find the expected responses and acks for each type of table routing.
A status response will be returned by the Module when a command is sent by the Host which is intended for a single target device.
If the command being sent to the target device, expects a response, then a single ZDO/ZCL Response Received command is expected in return.
An APS Ack is expected from the target device APS Layer...dependent on whether the option is selected.
A status response will be returned by the Module when a command is sent by the Host which is intended for multiple targets using group addressing.
If the command being sent to the target devices, expects responses, then a ZDO/ZCL Response Received command per target device is expected in return.
No APS Ack is expected from the target device per the Zigbee HA1.2 and Zigbee 3.0 Specification
A status response will be returned by the Module when a command is sent by the Host which is intended for all target devices on the network.
If the command being sent to the target devices, expects responses, then a ZDO/ZCL Response Received command is expected, per target device, in return.
No APS Ack is expected from the target device per the Zigbee HA1.2 and Zigbee 3.0 Specification
{style} .wiki-content h1 { font-family: 'Helvetica Neue', sans-serif; font-size: 30px; font-weight: bold; color: #20b6e1; letter-spacing: 1px; line-height: 1; text-align: left; #border-bottom: 1px solid #98bddd !important; } .wiki-content h2 { font-family: 'Helvetica Neue', sans-serif; font-size: 20px; font-weight: normal; color: #00517f; letter-spacing: 1px; line-height: 1; text-align: left; } .wiki-content h3 { font-family: 'Helvetica Neue', sans-serif; font-size: 15px; font-weight: bold; color: #00517f; letter-spacing: 1px; line-height: 1; text-align: left; } .wiki-content h4 { font-family: 'Helvetica Neue', sans-serif; font-size: 15px; font-weight: normal; font-style:italic; color:#00517f; letter-spacing: 1px; line-height: 1; text-align: left; } #title-text{ font-family: 'Helvetica Neue', sans-serif; font-size: 40px; font-weight: 500; letter-spacing: 1px; line-height: 1; text-align: left; } .panel, #content .panel { -moz-border-radius: 5px; -webkit-border-radius: 5px; border-radius: 5px; } .panel .panelHeader { text-align: left; color: #FFFFFF; line-height: 1em; padding: 10px 10px 5px; margin-bottom: 0; background-color: #00517f; -moz-border-radius-topleft: 5px; -moz-border-radius-topright: 5px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px; border-top-right-radius: 5px; border-top-left-radius: 5px; color:#FFFFFF } {style} |