CC2530: cc2530 no use many to one router,but have many to one route failure error

DAVID CUI

Part Number: CC2530
Other Parts Discussed in Thread: Z-STACK

dear all:

We are using CC2530, Zstack is z-home 1.2.0, Gateway in communication with the router, there are many to one route failure error, but our gateway CONCENTRATOR_ENABLE is false, I do not know why there are many to one route failure problem?

over 7 years ago

0 YiKai Chen over 7 years ago

Guru 735685 points

Where do you see many to one route failure error?

0 Ryan Brown1 over 7 years ago

TI__Guru**** 217727 points

Is the CC2530 the router or gateway ZNP? Have any changes been made to the default configurations? Have you considered porting to Z-Stack 1.2.2a to avoid several known bugs? Can you provide a sniffer log?

Regards,
Ryan

0 DAVID CUI over 7 years ago in reply to Ryan Brown1

Intellectual 610 points

dear ryan:

Here is the log message grabbed

0 YiKai Chen over 7 years ago in reply to DAVID CUI

Guru 735685 points

I don't see what you said route failure problem in screen shot.

0 Ryan Brown1 over 7 years ago in reply to DAVID CUI

TI__Guru**** 217727 points

Like YK, I do not see any issue with the screenshot provided. Was the wrong image provided or is there something in the route record payload that you do not understand?

Regards,
Ryan

0 DAVID CUI over 7 years ago in reply to Ryan Brown1

Intellectual 610 points

0 Ryan Brown1 over 7 years ago in reply to DAVID CUI

TI__Guru**** 217727 points

Route records are reported from routing devices to the concentrator. This would imply that 0x92AB is the concentrator (typically the ZC but doesn't have to be) and that 0x65FE is sending a network status commands to let it know that a link failure exists with 0x0000 (coordinator). This makes enough sense as the Route Record and Power Configuration packets never make it to 0x0000. The concentrator's application must decide what to do with this information, whether to re-issue a MTO route request or otherwise. Can you please attach the actual sniffer log and further explain what role each device has in your network?

Regards,
Ryan

0 Minghui Liu over 7 years ago in reply to Ryan Brown1

Prodigy 70 points

Hi，Ryan，

Both router and coordinator are set CONCENTRATOR_ENABLE to false. So we were wondering why Router record and MTO failure came up .The relevant packets can be seen in line 303 of the attachment.西大园27-1002 房间三0849 network status 路由失败.cubx.123

0 Jose Maria Alvarez over 7 years ago in reply to Minghui Liu

Genius 3415 points

Hi,

In this capture the device with address 0x92AB doesn't exist, the coordinator is trying to find it because a message was generated for this device for some reason. This is causing the route failure.

Regards,

0 Minghui Liu over 7 years ago in reply to Jose Maria Alvarez

Prodigy 70 points

Hi,

But why dose coordinator not send route request to find route,but to send route record? this place bothers us.

0 Jose Maria Alvarez over 7 years ago in reply to Minghui Liu

Genius 3415 points

You are using Linux Gateway as a coordinator right, which version are you using?

0 Minghui Liu over 7 years ago in reply to Jose Maria Alvarez

Prodigy 70 points

We are using cc2530 as a coordinator and connect to our own master controller through the uart. our gatway use z-home 1.2.0 and set CONCENTRATOR_ENABLE false.

0 Jose Maria Alvarez over 7 years ago in reply to Minghui Liu

Genius 3415 points

According to the spec is not necessary to have Concentrator capabilities to send a route record. The device just requires to have an entry in the route record table that is created by a remote device that sends a Route Request that sets Many-to-One field of route request options equal to 1 or 2.

This is not an unexpected behavior but is weird that the coordinator is sending a message to a node that doesn't appear in the capture with address 0x92AB. Also the Route request that created the Route record entry doesn't appear in the capture.

Maybe the device 0x92AB sent this message before the capture was started and turned off after that.

Try to replicate the behavior from the beginning to see if you can catch the Many-to-One route request that is creating the entry in the table.

0 Minghui Liu over 7 years ago in reply to Jose Maria Alvarez

Prodigy 70 points

Hi ,Jose Maria Alvarez,
1.This is not an unexpected behavior but is weird that the coordinator is sending a message to a node that doesn't appear in the capture with address 0x92AB.
--> The 1,190 lines in the capture file are the data communication process restarted.
2.Try to replicate the behavior from the beginning to see if you can catch the Many-to-One route request that is creating the entry in the table.
-->The problem cannot be repeated, and the device is back to normal when it is restarted

0 Ryan Brown1 over 7 years ago in reply to Minghui Liu

TI__Guru**** 217727 points

Sounds like the issue is resolved then, please update this post if you are able to re-create the issue.

Regards,
Ryan

Zigbee & Thread

Zigbee & Thread forum

CC2530: cc2530 no use many to one router,but have many to one route failure error