Download BitCloud User Guide

Networking overview
Figure 5-3.
Network leave sequence diagram (local call).
Application
Stack
ZDO_ZdpReq()
ZDO_ZdpRep()*
No network start
in application
ZDO_SUCCESS_STATUS
ZDO_MgmtNwkUpdateNotf()
ZDO_NETWOK_LEFT_STATUS
* Function registered as callback for argument of ZDO_ZdpReq().
Figure 5-4.
Network leave sequence diagram. Device1 requests Device2 to leave Network.
Air interface
Device 1
Application
Stack
ZDO_ZdpReq()
ZDO_ZdpRep()*
ZDO_SUCCESS_STATUS
Device 2
Stack
Application
LeaveReq frame
LeaveRsp frame
SUCCESS STATUS
Leave NWK frame
ZDO_MgmtNwkUpdateNotf()
ZDO_NETWORK_LEFT_STATUS
* Function registered as callback for argument of ZDO_ZdpReq().
5.3
Data exchange
Obviously the purpose of establishing a ZigBee network as described in “Network formation and join” on
page 5-1 is to perform data exchange between remote nodes as required by application functionality.
This section gives an overview about node configuration, packet transmission parameters and BitCloud
API functions responsible for communication on application level.
5.3.1
Application endpoint registration
Within ZigBee the application data is exchanged between so called application endpoints that represent
certain applications on each device. In order to enable communication on application level each node
shall register at least one endpoint using APS_ReqisterEndPoint() function with an argument of
APS_RegisterEndpointReq_t type. The argument specifies endpoint descriptor (simpleDescriptor field)
which includes such parameters as endpoint ID (a number from 1 to 240), application profile ID, number
and list of supported input and output clusters. In addition APS_DataInd field specifies indication callback function which will be called upon data reception destined for this endpoint.
BitCloud User Guide
5-6
8199B–MCU Wireless–02/09