• State Resolved
  • Replies 1 reply
  • Subscribers 56 subscribers
  • Views 130 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

Original question:

CC2340R5: As a router device, the link status message does not show all the entry

CC2340R5: why coordinator always send route request message before sending a zcl command?

senjin
Prodigy 170 points
Part Number: CC2340R5
Other Parts Discussed in Thread: Z-STACK, CC2652R

Tool/software:

I use CC2652 as coordinator, and CC2340R5 as router,  and only one router in the network.

When I send the ZCL command to the zed from the coordinator, I see that the coordinator always sends the router request command first. Although the zed has reply with a route reply message, the coordinator send the route request again. Because my ZCL command is sent frequently, this affects the work efficiency.

when I use CC2652 as coordinator and router,  the problem doesn't happen. I guess it's the CC2340R5 problem.

I have added the sniff log in both test environments to the attachment.

7774.Log.zip

  • +1
    TI__Guru**** 211047 points

    Hello Senjin,

    The SimpleLink F2 SDK Z-Stack has a GOOD_LINK_COST definition which sets the allowable link cost for a route between neighbors.  You can see that before packet 82 there was no issue with direct communication.  However, packet 83 is a link status message from the CC2340R5 ZR which shows an incoming cost of 0x5 from the CC2652R ZC.  Thus this coordinator's outgoing cost to the router is 0x5 which is above GOOD_LINK_COST (0x01 is the best, 0x07 is the worst, 0x0 is broken, default good cost is 0x03 or less) and so the ZC attempts to find another route.  Failing to receive a route reply with a better cost path, it will eventually accept the direct packet send to the ZR.

    From your previous E2E thread it is apparent that the CC2340R5 Zigbee stack has consistent/average incoming costs of 0x04 which is unexpected.  I will provide this information to the Zigbee R&D Team so that the link cost calculations can be improved in zb_nwk.h, until then you can consider lowering increasing the GOOD_LINK_COST in Z-Stack or forcing a lower link cost value in the F3 SDK.

    Regards,
    Ryan