ZigBee | Ember | Frequency of call Embertick ()

Title problem, can also be understood as, how to improve the Ember ZigBee equipment Large-scale network processing capacity .

Call the Embertick function as much as possible to keep the protocol stack well timed and compatible with 802.15.4 Macs. At a minimum, the function should be called once in each while cycle

If the network information is very heavy, especially at the receiving end, the function should be called more. Ideally, when you receive a packet, you should call the function within 500ms, so that you can have a lot of time to reply to the ACK to avoid receiving an ACK on the sending side and reach the maximum transmission time (1.28s). In the worst case, as long as your acceptance message queue does not overflow, you should call this enough multiple times, more packet buffering means more flexibility in calling the Embertick function before overflow. If the ideal is not achieved, it means more information is retry, which leads to more traffic jams and higher probability of loss of information. If the worst case cannot be reached, it means that you will lose the receiving message and it is possible to lose all of the protocol stack buffer.

It is worth remembering that the number of calls to Embertick is very small, because if the protocol stack is not in the pending state, the stack returns immediately without affecting the execution of other programs. Of course, if the call is too frequent, it can result in loss of information, as well as the lack of buffer, but also increase the routing packet delay.

Additional personal Views:

For a Zed device, it is generally sufficient to call Embertick once per while loop. but for ZC equipment, according to the actual test situation of large-scale network, retry phenomenon will be obvious, even lead to incorrect information transmission. At this point, multiple calls to Embertick will be a good choice.

ZigBee | Ember | Frequency of call Embertick ()