Configurations in wireless protocol layer can be used to fine tune the behavior of wireless protocol. The possible configurations differ between different protocols.
Macros
|
|
Name |
Description |
 |
ACTIVE_SCAN_RESULT_SIZE defines the maximum active scan result that the stack can hold. If active scan responses received exceed the definition of ACTIVE_SCAN_RESULT_SIZE, those later active scan responses will be discarded | |
|
|
CONNECTION_RETRY_TIMES is the maximum time that the wireless node can try to establish a connection. Once the retry times are exhausted control will be return to application layer to decide what to do next | |
|
|
COUNTER_CRYSTAL_FREQ defines the frequency of the crystal that is connected to the MCU counter to perform timing functionality when MCU is in sleep. | |
|
|
ENABLE_DUMP will enable the stack to be able to print out the content of the P2P connection entry. It is useful in the debugging process | |
|
|
ENABLE_ENHANCED_DATA_REQUEST enables the Enhanced Data Request feature of P2P stack. It combines the message that is send from the sleeping device with Data Request command upon wakeup, to save 20% - 30% active time for sleeping device, thus prolong the battery life. | |
|
|
ENABLE_TIME_SYNC enables the Time Synchronizaiton feature of P2P stack. It allows the FFD to coordinate the check-in interval of sleeping device, thus allow one FFD to connect to many sleeping device. Once Time Synchronization feature is enabled, following parameters are also required to be defined: TIME_SYNC_SLOTS COUNTER_CRYSTAL_FREQ | |
|
|
FA_BROADCAST_TIME defines the total number of times to broadcast the channel hopping message to the rest of PAN, before the Frequency Agility initiator jump to the new channel | |
|
|
INDIRECT_MESSAGE_SIZE defines the maximum number of packets that the device can store for the sleeping device(s) | |
|
|
INDIRECT_MESSAGE_TIMEOUT defines the timeout interval in seconds for the stored packets for sleeping devices | |
|
|
RESYNC_TIMES defines the maximum number of times to try resynchronization in all available channels before hand over the control to the application layer | |
|
|
RFD_DATA_WAIT is the timeout defined for sleeping device to receive a message from the associate device after Data Request. After this timeout, the RFD device can continue to operate and then go to sleep to conserve battery power. | |
|
|
TIME_SYNC_SLOTS defines the total number of time slot available within one duty cycle. As a rule, the number of time slot must be equal or higher than the total number of sleeping devices that are connected to the FFD, so that each sleeping device can be assigned to a time slot. The time slot period is calcualted by following formula: Time Slot Period = RFD_WAKEUP_INTERVAL / TIME_SYNC_SLOTS The length of time slot period depends on the primary oscillator accuracy on the FFD as well as the 32KHz crystal accuracy on sleeping devices. The definition of TIME_SYNC_SLOTS is only valid if... more |
Topics
|
Name |
Description |
|
Following configurations can be used to fine tune the behavior of MiWi(TM) P2P wireless protocol. | |
|
Following configurations can be used to fine tune the behavior of MiWi(TM) mesh networking protocol. |