• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 57 subscribers
  • Views 467 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: ED cannot join on Coordinator

Zarko Kostadinovski
Prodigy 130 points

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

I have one coordinator with CC2530 and one Konke motion sensor. When I try to join Konke ED to coordinator, there is beacon request from ED, Coordinator respond with NwkOpen packet but Router and End Device capacity are 0 and Depth also. ED not join the network.

Why this ED not join the network? Log attached.

Konke Not Joining on Open Network Ubiqua.zip

  • 0
    TI__Guru**** 222287 points

    From what Z-Stack version and specific example did you program the CC2530 ZC?  Were any modifications made to the ZC project and did you make sure to erase all device memory before programming?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 130 points

    ZC is Sample Light application from Z-Stack Home 1.2.0. There is application modification but nothing related to network (PWM, Keys, etc).

    Flash was completely erased and then programmed the example for ZC.

    End Device is third party device, no control there.

  • 0 in reply to Zarko Kostadinovski
    TI__Guru**** 222287 points

    We cannot provide support on stacks pre-dating those found on Z-STACK-ARCHIVE.  As I assume this is not the first time this stack has been evaluated, please comment on any changes that may have caused the issue to arise.  Are TI or other 3rd-party devices able to join the network?  Make sure you are using the same IAR EW8051 version stated in the Release Notes.  If you can replicate the issue on HA 1.2.2a then please let us know.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 130 points

    Thanks. I'll try to migrate to newer version.

    I have other devices joined in the network and I can see if network is open on other routers in the network they respond with router and end device capability to yes, but ZC respond with no.

    Can you point out why this flags are no on ZC and is this flags are required to be yes in order end device to join on network?

  • 0 in reply to Zarko Kostadinovski
    TI__Guru**** 222287 points

    I recommend migrating to Z-Stack 3.0.2 for the best user experience and support.

    Zarko Kostadinovski said:
    Can you point out why this flags are no on ZC and is this flags are required to be yes in order end device to join on network?

    I do not know why the flags are reset on this deprecated ZC firmware.  It would insinuate that its association tables are full and that the device does not have enough storage for additional nodes to join.  This would mean the ZC has not been factory reset like previously stated.  Perhaps you could further clarify the network topology involved.  Zigbee Specification revisions that I am aware of require these flags to be set in order for devices to associate.

    Regards,
    Ryan

  • 0 in reply to Zarko Kostadinovski
    Guru 735695 points

    What 3rd party device do use? Are you sure the 3rd party device runs Zigbee HA profile or Zigbee 3.0 standard?

  • 0 in reply to YiKai Chen
    Prodigy 130 points

    I check association table and has only 3 entries, which point out that there is space for new devices..

    Anyway, I do factory reset from code and router and end device capabilities was set to yes and end device manage to associate. I do not understand the problem, but at least it is fixed.

    Thanks.