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.

Issues for routers joining network

Other Parts Discussed in Thread: Z-STACK

Hi guys,


I am using ZStack 2.5.1 and have a mesh network with a coordinator and a couple of routers.

Unfortunately my routers have problems joining the network.

What happens is that in ZDApp_NwkDescListProcessing() the network description returned by nwk_getNwkDescList() doesn't have the routerCapacity / deviceCapacity flag set. So logically, the router will not join the network. But if I use the Smart RF Sniffer program, I can see, that in the coordinators beacon response, the flags are set, meaning the coordinator allows joining the network.

The issues doesn't show each time a router tries to join, but more often than not. The code for nwk_getNwkDescList() or where ever the network description is created unfortunately is not available.

So the question is, is there a possible bug or are there conditions that cause ZStack to override the information received from the coordinator?

Thx,

Jens

  • Which sample does your test based on? I have no such problem using router device with Z-Stack 2.5.1a. Do you modify anything in Z-Stack?

  • My program is based on the SampleApp sample. I did some changes around that area where the network to join is picked since I am playing around with dynamic EPANIDs. But I didn't modify the network description handed over by nwk_getNwkDescList().

    I am quite sure usually the code works just fine. It's an essential part of the software. But what could cause the router to overwrite the routerCapacity flag received from the coordinator?


    Jens

  • Is it possible that this is somehow a function of the link quality?

    I have three boards here running the exact same software. While two of them always connect, the third one always has trouble.

    Using the RF Sniffer again, I found that the troublesome device always shows a significantly lower (only half or even third) LQI value, even if the three boards are right next to each other with antennas all pointing into the same direction.

    Jens

  • It sounds that your 3rd board has HW trouble. Ask some HW guys to check the antenna.

  • Out of Box in Z-Stack it is required that the incoming beacon for association has an LQI greater than  gMIN_TREE_LINK_COST please see the function ZDO_beaconNotifyIndCB(). So the hardware issue may be causing the 3rd router to not join the network. 

  • Suyash, YiKai,

    thak you for the clarification. It would be better if ZStack would tell me if the link quality isn't good enough instead of overwriting some data that I can see in the sniffer, but it makes sense not to connect.

    Thanks for the answers.

    Jens

  • Jens,

    ZStack doesn't overwrite any parameter/data in case the link quality is not good. It could be that the "bad" router didn't receive any beacons from other "good routers" and the co-ordinator ,  hence the network list was not populated. It seems to be hardware issue.

    Saurabh