• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 56 subscribers
  • Views 206 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.

CC2530: link status issue

Cherry Zhou
Mastermind 22235 points
Part Number: CC2530

Hi team,

Here's an issue from the customer may need your help:

ZStack-CC2530-2.5.1a version.

The router device short address 0x0001 sends out a link status message with the Incoming /Outgoing cost to the coordinator as 0. The coordinator then sends a route request message. Then the outgoing cost from link status to 0x00001 in the coordinator becomes 0. (See here for Message)

As the message shows,  Line 4447, 000 1 transmit exception link status. Line 4450, the coordinator sends the route request.

Issues:

1) How to ignore a message from router with link status Incoming /Outgoing cost of 0?

2) Or how can the coordinator update the Incoming /Outgoing cost in their neighbor table to normal after receiving any APS layer message or any other message from the router device?

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    Guru 735685 points

    You cannot or should not do this but you can try to revise rtgTable
    and neighborTable. There’s no guarantee for this to work.

  • 0
    TI__Guru**** 217737 points

    Hi Cherry,

    1) The ZC should not desire to ignore messages from a valid neighbor router, this is why it attempts to send a Route Request to repair the connection.  You could try to invalidate the neighbor/routing entries as YK mentioned but this interferes with the Zigbee network layer which is not recommended, and may attempt to self-correct regardless.  Although the link status messages from the ZR are very sporadic, the constant Reserved Profile messages from 0x0001(with no Route Request although it has an outgoing cost of zero) maintain the neighbor/routing entry for this disconnected time period.

    2) The link status message of the ZC is updated for the 0x0001 entry from packet 4483 onward to reflect its ability to receive messages from the ZR but not be able to send them.  The link appears to heal around packet 5046 and communication between the two nodes continues from there.  This is the intended healing properties of Zigbee, and you will find that the link status messages from the ZC continue to show valid costs after this time period.

    Regards,
    Ryan