Configuration in application layer defines the basic functionality of the wireless node. Usually, those configurations may differ among different wireless nodes in the same application, depending on the wireless node's role in the network and application.
Configurations in application layer include following categories:
* Choice of wireless protocol
* Choice of RF transceiver
* System Resources Definitions
* Enable/Disable functionalities according to application needs
* Application specific information
Macros
|
|
Name |
Description |
 |
ADDITIONAL_NODE_ID_SIZE defines the size of additional payload will be attached to the P2P Connection Request. Additional payload is the information that the devices what to share with their peers on the P2P connection. The additional payload will be defined by the application and defined in main.c | |
|
|
P2P_CONNECTION_SIZE defines the maximum P2P connections that this device allowes at the same time. | |
|
|
ENABLE_ACTIVE_SCAN will enable the device to do an active scan to to detect current existing connection. | |
|
|
ENABLE_BROADCAST will enable the device to broadcast messages for the sleeping devices until they wake up and ask for the messages | |
|
|
ENABLE_ED_SCAN will enable the device to do an energy detection scan to find out the channel with least noise and operate on that channel | |
|
|
ENABLE_FREQUENCY_AGILITY will enable the device to change operating channel to bypass the sudden change of noise | |
|
|
ENABLE_HAND_SHAKE enables the protocol stack to hand-shake before communicating with each other. Without a handshake process, RF transceivers can only broadcast, or hardcoded the destination address to perform unicast. | |
|
|
ENABLE_PA_LNA enable the external power amplifier and low noise amplifier on the RF board to achieve longer radio communication range. To enable PA/LNA on RF board without power amplifier and low noise amplifier may be harmful to the transceiver. | |
|
|
ENABLE_INDIRECT_MESSAGE will enable the device to store the packets for the sleeping devices temporily until they wake up and ask for the messages | |
|
|
ENABLE_NETWORK_FREEZER enables the network freezer feature, which stores critical network information into non-volatile memory, so that the protocol stack can recover from power loss gracefully. Network freezer feature needs definition of NVM kind to be used, which is specified in HardwareProfile.h | |
|
|
ENABLE_SECURITY will enable the device to encrypt and decrypt information transferred | |
|
|
ENABLE_SLEEP will enable the device to go to sleep and wake up from the sleep | |
|
|
EUI_0 to EUI_7 defines the Extended Universal Identifier, or permanent address, for the wireless node. The length of the EUI is defined as MY_ADDRESS_LENGTH. | |
|
|
HARDWARE_SPI enables the hardware SPI implementation on MCU silicon. If HARDWARE_SPI is not defined, digital I/O pins will be used to bit-bang the RF transceiver | |
|
|
Definition of MRF24J40 enables the application to use Microchip MRF24J40 2.4GHz IEEE 802.15.4 compliant RF transceiver. Only one RF transceiver can be defined. | |
|
|
Definition of MRF49XA enables the application to use Microchip MRF49XA subGHz proprietary RF transceiver. Only one RF transceiver can be defined. | |
|
|
Definition of MRF89XA enables the application to use Microchip MRF89XA subGHz proprietary RF transceiver | |
|
|
MY_ADDRESS_LENGTH defines the size of wireless node permanent address in byte. This definition is not valid for IEEE 802.15.4 compliant RF transceivers. | |
|
|
MY_PAN_ID defines the PAN identifier. Use 0xFFFF if prefer a random PAN ID. | |
|
|
NWK_ROLE_COORDINATOR is not valid if PROTOCOL_P2P is defined. It specified that the node has the capability to be coordinator or PAN coordinator. This definition cannot be defined with NWK_ROLE_END_DEVICE. | |
|
|
NWK_ROLE_END_DEVICE is not valid if PROTOCOL_P2P is defined. It specified that the node has the capability to be an end device. This definition cannot be defined with NWK_ROLE_COORDINATOR. | |
|
|
PROTOCOL_MIWI enables the application to use MiWi mesh networking stack. This definition cannot be defined with PROTOCOL_P2P. | |
|
|
PROTOCOL_MIWI_PRO enables the application to use MiWi PRO stack. This definition cannot be defined with PROTOCOL_P2P or PROTOCOL_MIWI. | |
|
|
Definition of Protocol Stack. ONLY ONE PROTOCOL STACK CAN BE CHOSEN | |
|
|
RFD_WAKEUP_INTERVAL defines the wake up interval for RFDs in second. This definition is for the FFD devices to calculated various timeout. RFD depends on the setting of the watchdog timer to wake up, thus this definition is not used. | |
|
|
RX_BUFFER_SIZE defines the maximum size of application payload which is to be received | |
|
|
TARGET_SMALL will remove the support of inter PAN communication and other minor features to save programming space | |
|
|
TX_BUFFER_SIZE defines the maximum size of application payload which is to be transmitted |