📄 allfiles_f.html.svn-base
字号:
<html><head><title>All File Index</title></head><body><font size="-1"><b><font color="blue"><a href="apps_p.html">Apps</a></font></b> <b><a href="components_p.html">Components</a></b> <b><a href="interfaces_p.html">Interfaces</a></b> All Files <b><a href="index.html">Source Tree</a></b> </font><hr><h1 align="center">All File Index</h1><center><table border=0 cellpadding=0 width="80%"><tr valign="top"><td><a href="allfiles_p.html"><em>path</em></a></td><td> </td><td><em>file</em></td><td> </td><td><em>description</em></td></tr><tr valign="top"> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MCPS.MCPS_DATA.nc.html">beta.CC2420Radio.ieee.802.15.4.MCPS</a></td> <td> </td> <td>MCPS_DATA.nc</td> <td> </td> <td>The MCPS-SAP supports the transport of SSCS protocol data units (SPDUs) between peer SSCS entities. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MCPS.MCPS_PURGE.nc.html">beta.CC2420Radio.ieee.802.15.4.MCPS</a></td> <td> </td> <td>MCPS_PURGE.nc</td> <td> </td> <td> MCPS_PURGE is used to manage MSDU handles in the transaction queue of the MCPS of the MAC sublayer. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_ASSOCIATE.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_ASSOCIATE.nc</td> <td> </td> <td>The MLME-SAP association primitives define how a devices becomes associated with a PAN. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_BEACON_NOTIFY.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_BEACON_NOTIFY.nc</td> <td> </td> <td>The MLME-SAP beacon notification primitive defines how a device may be notified when a beacon is received during normal operation conditions. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_COMM_STATUS.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_COMM_STATUS.nc</td> <td> </td> <td>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. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_DISASSOCIATE.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_DISASSOCIATE.nc</td> <td> </td> <td>The MLME-SAP dissassociation primitives define how a device can disassociate with a PAN. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_GET.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_GET.nc</td> <td> </td> <td>The MLME-SAP get primitives define how to read values from the PIB. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_GTS.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_GTS.nc</td> <td> </td> <td>The MLME-SAP GTS management primitives define how GTSs are requested and maintained. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_ORPHAN.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_ORPHAN.nc</td> <td> </td> <td>The MLME-SAP orphan notification primitives define how a coordinator can issue a notification of an orphaned device. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_POLL.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_POLL.nc</td> <td> </td> <td>The MLME-SAP polling primitives define how to request data from a coordinator. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_RESET.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_RESET.nc</td> <td> </td> <td>The MLME-SAP reset primitives specify how to reset the MAC sublayer to its default values. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_RX_ENABLE.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_RX_ENABLE.nc</td> <td> </td> <td>The MLME-SAP receiver state primitives define how a device can enable or disable the receiver at a given time. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_SCAN.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_SCAN.nc</td> <td> </td> <td>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. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_SET.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_SET.nc</td> <td> </td> <td>The MLME-SAP get primitives define how to write values to the PIB. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_START.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_START.nc</td> <td> </td> <td>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. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_SYNC.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_SYNC.nc</td> <td> </td> <td>The MLME-SAP synchronization primitives define how synchronization with a coordinator may be achieved. </td></tr><tr valign="top"> <td><a href="beta.CC2420Radio.ieee.802.15.4.MLME.MLME_SYNC_LOSS.nc.html">beta.CC2420Radio.ieee.802.15.4.MLME</a></td> <td> </td> <td>MLME_SYNC_LOSS.nc</td> <td> </td> <td>The MLME-SAP primitives for how a loss of synchronization is communicated to the next higher layer. </td></tr></table></center><hr>Generated by <a href="../../../nesc/doc/nesdoc.html">nesdoc</a><br></body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -