• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 441 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.

CC2652P: How about all devices join the same network simultaneously

Alex Zhang
Intellectual 1305 points
Part Number: CC2652P
Other Parts Discussed in Thread: Z-STACK

Hi team

  • I have 30 end devices power on at the same time and request to join the same network, given the air congestion, it's acceptable that some of them fail to jion.  So the devices join again 3 seconds after failure until successful join.
  • the problem is that some devices will never join successfully, even if I turn off most devices to reduce congestion. From the sniff log, I know the end device send a association request and get a response from  the coordinator which didn't send a network key to end devices later. Also, if I reboot the coordinator, the device can successfully join the network. So I think the problem is on the coordinator side.
  • An additional point is that it's ok to join if the 30 end devices join one by one, not at the same time. Has anyone encountered the same problem?  Please help analyze it, thanks.

Best regards

Alex

  • 0
    TI__Guru**** 218837 points

    Hi Alex,

    What SDK are you evaluating?  Can you provide the sniffer log and identify some devices which do not join?  You can try to increase the STACK_TASK_STACK_SIZE and APP_TASK_STACK_SIZE to compensate for this traffic, or monitor the heap for overflow, but ultimately TI does not test the Z-Stack solution against this type of usage and recommends that you stagger device joining. You can also trigger a reset of the coordinator from its application code if you can detect that the issue has occurred.

    Regards,
    Ryan