 |
Developing with ZBOSS for Zigbee
|
|
Developing with ZBOSS for Zigbee
|
#include <zboss_api_buf.h>
Packet buffer header.
| zb_uint16_t zb_buf_hdr_s::data_offset |
data offset in buffer buf
| zb_bitfield_t zb_buf_hdr_s::encrypt_type |
payload must be encrypted before send, if !0.
| zb_uint8_t zb_buf_hdr_s::handle |
The handle associated with the NSDU to be transmitted by the NWK layer entity.
| zb_bitfield_t zb_buf_hdr_s::has_aps_payload |
if 1, than packet comes from APS, the flag is needed to increase APS packets counter in diagnostic data on packet sending
| zb_bitfield_t zb_buf_hdr_s::has_aps_user_payload |
if 1, than packet comes with APS user's payload
| zb_bitfield_t zb_buf_hdr_s::is_in_buf |
if 1, this is input buffer
| zb_bitfield_t zb_buf_hdr_s::is_rx_buf |
if 1, this is buffer with received packet and nwk_mac_addrs_t is at buffer tail
| zb_uint16_t zb_buf_hdr_s::len |
current layer buffer length
| zb_uint8_t zb_buf_hdr_s::multiplicity |
if greater that 1, then the following (multiplicity - 1) buffers are occupied with payload data and should not be treated as having valid headers, etc.
| zb_ret_t zb_buf_hdr_s::status |
some status to be passed with packet
| zb_bitfield_t zb_buf_hdr_s::tail_len |
the length of the perameters section
| zb_bitfield_t zb_buf_hdr_s::use_same_key |
if 1, use same nwk key packet was encrypted by
| zb_bitfield_t zb_buf_hdr_s::zdo_cmd_no_resp |
if 1, this is ZDO command with no response - call callback at confirm