This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Hi, we are using the ZNP project for a coordinator connected to our device, and we recently updated the project from the 4.40 SDK to the 7.41. To simplify the migration, we created a new project importing ZNP from the SDK, and made the changes in syscfg:
Z-Stack->Power Management->Power Mode of Operation = Always On
Z-Stack->Network->Network Maximum Device List = 64
Z-Stack->Network->Maximum Unique TC Link Keys = 64
Z-Stack->Advanced->Routing Table Size = 80
And in project properties:
Build->Tools->Arm Compiler->Predefined Symbols->NVOCMP_NVPAGES=4
Build->Tools->Arm Compiler->Predefined Symbols->MAX_DEVICE_TABLE_ENTRIES=64
Build->Tools->Arm Linker->Advanced Options->Command File Preprocessing->NVOCMP_NVPAGES=4
While we were able to pair 64 devices with these changes, we had 2 instances where the ZNP became unable to receive messages, while still responding to commmands. This would look like a reset of the device, but no start messages were sent, so we don't know what exactly happened. It may be a problem with lack of heap space or something like that? I don't know which variable we should need to change to better support these devices, since the only solution right now would be to keep sending messages to any non sleepy device and check when communication is lost to restart the ZNP, which is far from optimal.
Thanks for any suggestion,
Gustavo.
Hi Gustavo,
Consider using some of the images here: https://github.com/Koenkk/Z-Stack-firmware/tree/develop/coordinator/Z-Stack_3.x.0/bin
There have been improvements in stability, such as UART2 (new UART driver compared to 4.40 SDK) and network settings for larger networks.
Thanks,
Toby
Hi Toby,
while we can't use a completely new image (we would need to test the full communication with our base device, and need the changes to be compatible with old devices) we didn't know about the bug with configuring TX Power above 5DBm, which would seem to be the problem I was noticing.
After applying the patch provided in the projects, I din't notice further crashes, and was able to have a stable network with all devices paired, so this would be the solution.
Thanks a ton for pointing me to the solution.
Regards,
Gustavo