• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 1025 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

the question about "route reply"

ZIGBEE LEARNER
Prodigy 20 points


I used two rounter and one coordinator to establish a network. And i used the sniffer packet to catch the information.
Firstly, the Frame"route request" was sent by coordinator,and it was reached the destination address successful.But after the destination address sent the "rount reply" to the originator address, the frame "rount reply" coundn't get to the originator address, there is no frame "ACK". Then the coordinator sent "route request" again, so i think the route is failed. how can i do for take the route successful?

6758.2014.7.22-8.2.psd

please look at the NO.92--NO.115 in the "PSD". 

  • 0
    TI__Genius 9180 points

    How long does this continue for, is it just for some time after a devices enters the network, or does it always happen?  

    The devices need to be in the neighbor table or association table before the messages will be processed by the nwk layer. If the device is not in the association table then the neighbor table is populated by Link Status messages, so once the devices have seen enough messages it will process the route rsp. You can check the neighbor table of the devices by looking at the Link Status payload, this will show the neighbors and the Link Cost. 

    Are the devices in range or on the boundary between in range and out of range?

    Also what application are you using? Did you try it with one of the ZStack-Lighting-1.2.0 Sample applications?

    Regards, TC.

  • 0 in reply to TopCat
    TI__Genius 9180 points

    I just decoded the packet trace with ubiqua. I notice that the Coord is not sending the periodic link status messages, can you confirm that you have not change the following in nwk_globals.h:

    #if !defined ( NWK_LINK_STATUS_PERIOD )
    #define NWK_LINK_STATUS_PERIOD 15 // 15 seconds
    #endif

    If you have not then I would advise that you look for a memory leak or pointer overflow in your application as the stack seems to be behaving incorrectly.

    Can you try replicating the simple test case of joining devices these devices and sending data with a ZStack-Home-1.2.0 sample app Coord?

    Regards, TC.

  • 0 in reply to TopCat
    Prodigy 20 points

    Thank you for your answer, first
    I didn't change the code which you mentioned in "nwk_globals.h". And the question was occured at telecommunication, about 150 meters.Most of the time when i took a test, the "route reply" coundn't get to the coordinator.but the "route request" that from the coordinator cound get to the destination address. I can't explain this phenomenon.
    Through multiple tests, i find the Coordinator is sending the periodic link status messages,there is no link status messages from coordinator maybe cause of the position where packet sniffer put is so far from the coordinator.
    I confirmed that the device is in the neighbor table.

  • 0 in reply to ZIGBEE LEARNER
    Guru 735685 points

    What is it if you put all of your routers around coordinator and not as far as 150M?