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 issue about coordinator could not send the msg to End device

Other Parts Discussed in Thread: Z-STACK

hi  all

         there  are one ZED and two  ZR

        ZED was the child node of the ZR1 at frist。

        i take ZED and  ZR2  far  from  the ZC, and  make sure they could not  link with ZC any more。

       sometime later  ZED change parents  with ZR2。 and  then take them back  to ZC。

      

       after  doing above Testing step (to simulate ZC had  not notificed  ZED changing parents)  several cycle 。

       i found  sometimes ZC could  send the msg  to ZED via  ZR2(the right  one) 

       sometimes  it  could  not  send the msg  via ZR2 ,although  using  the wrong way via ZR1  forever~~~~

       then  it could  control ZED anymore。。。

       when  it  could send  the msg  via  ZR2, i saw  something strange in the log  ,which shows  :“Reversed”:

       i saw  there is a MAC  address in  the APS  payload, but  i don't know what does it  mean

       and  there  is nothing like that while  ZC choosing  the wrong  way  to sending the msg ~~~~~~

       so  does  anybody knows  what will caused  the ZC  had  not updating the routing path ?

       is  that related with  this “Reversed” msg !!!!