Other Parts Discussed in Thread: Z-STACK
Hi Ti,
I want to know which process will change this mac path? I have been enable source route path,but the mac layer send data to the finish path.
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.
Hi Tenang,
I recommend you read through the Z-Stack User's Guide Z-Stack Overview and Network Configuration sections in regards to MTO and source routing: http://dev.ti.com/tirex/explore/node?node=ANbR0LtTwkMnDCiEhygF7A__pTTHBmu__LATEST
Then provide more information and the sniffer log if your question still is not answered.
Regards,
Ryan
Hi Ryan,
U can find that the message is send by source route. Path: 0x0000-> 0x9247 -> 0x9c42.
For nwk layer, message source is 0x0000 and destination addr is 9c42. So message is zco send to 0x9c42,
But it has source route in this message. (0x9247)
Thus,message destination addr should be 0x9c42 at mac layer and another message including same frames is 0x9c42 sending by 0x9247.
I am confuse that why this message does not deliver by 0x9247?
Hi YK,
Sry, this log can not share.
I has test this multiple times,this rarely happens. Most of the time is 0x0000 -> 0x9247 -> 0x9c42.
I have confuse because 0x9c42 is zed and parents is 0x9247.
So 0x9c42 can not get message sending by zco.
According sniffer log,0x9c42 does not change it parent in whole process.
Hello Tenang,
I agree with YK, it would be best if you could find a way to share the sniffer log. Which Z-Stack version are you using? It would also help if you could easily reproduce the issue using the examples provided by TI. What changes have been made to the stack and are there any specific packet types that display this behavior?
Regards,
Ryan
Tenang,
Has this issue been resolved? If not then please respond to the questions previously asked.
Regards,
Ryan