path |
|
file |
|
description |
|
|
|
|
|
beta.CC2420Radio.ieee.802.15.4.MCPS |
|
MCPS_DATA.nc |
|
The MCPS-SAP supports the transport of SSCS protocol data units (SPDUs) between peer SSCS entities. |
|
|
MCPS_PURGE.nc |
|
MCPS_PURGE is used to manage MSDU handles in the transaction queue of the MCPS of the MAC sublayer. |
|
|
|
|
|
beta.CC2420Radio.ieee.802.15.4.MLME |
|
MLME_ASSOCIATE.nc |
|
The MLME-SAP association primitives define how a devices becomes associated with a PAN. |
|
|
MLME_BEACON_NOTIFY.nc |
|
The MLME-SAP beacon notification primitive defines how a device may be notified when a beacon is received during normal operation conditions. |
|
|
MLME_COMM_STATUS.nc |
|
The MLME-SAP communication status primitive defines how the MLME communicates to the next higher layer about transmission status, when the transmission was not instigated by a .request primitive, and security errors on incoming packets. |
|
|
MLME_DISASSOCIATE.nc |
|
The MLME-SAP dissassociation primitives define how a device can disassociate with a PAN. |
|
|
MLME_GET.nc |
|
The MLME-SAP get primitives define how to read values from the PIB. |
|
|
MLME_GTS.nc |
|
The MLME-SAP GTS management primitives define how GTSs are requested and maintained. |
|
|
MLME_ORPHAN.nc |
|
The MLME-SAP orphan notification primitives define how a coordinator can issue a notification of an orphaned device. |
|
|
MLME_POLL.nc |
|
The MLME-SAP polling primitives define how to request data from a coordinator. |
|
|
MLME_RESET.nc |
|
The MLME-SAP reset primitives specify how to reset the MAC sublayer to its default values. |
|
|
MLME_RX_ENABLE.nc |
|
The MLME-SAP receiver state primitives define how a device can enable or disable the receiver at a given time. |
|
|
MLME_SCAN.nc |
|
The MLME-SAP scan primitives define how a device can determine the energy usage or the presence or absence of PANs in a communications channel. |
|
|
MLME_SET.nc |
|
The MLME-SAP get primitives define how to write values to the PIB. |
|
|
MLME_START.nc |
|
The MLME-SAP start primitives define how an FFD can request to start using a new superframe configuration in order to initiate a PAN, begin transmitting beacons on an already existing PAN, facilitating device discovery, or to stop transmitting beacons. |
|
|
MLME_SYNC.nc |
|
The MLME-SAP synchronization primitives define how synchronization with a coordinator may be achieved. |
|
|
MLME_SYNC_LOSS.nc |
|
The MLME-SAP primitives for how a loss of synchronization is communicated to the next higher layer. |