• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 57 subscribers
  • Views 1467 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.

CC2531: CC2531

hobieboy
Intellectual 660 points

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

Hi,

I ran into a mysterious problem recently - using TI CC2531 USB dongle acing as a Zigbee coordinator. I have a device joined the network. Everything is working fine.

Then, I plugged in a Samsung Smartthings (Zigbee) Hub. After some time (a few hours it looks like), the device stopped "talking" the my Zigbee coordinator.

Through the sniffer, there is no more traffic from the device to the coordinator. So it means that the device somehow switched to a different Zigbee channel?

Based on limited testing, if I power recycle the device, it will start communicating again.

I tried using a sniffer to sniff, the coordinator is communication on channel 11. And there's lots of traffic when everything works. When the device stops communicating, even if I snoop channels 14, 15, 19, 20, 24 & 25 there is no traffic.

Anyone knows what would happen IF there are multiple coordinators in the network (I assume Samsung hub wants / is presenting itself as a coordinator)?

Thanks!

  • 0
    Guru 735695 points

    Can you elaborate what is your device joined the network in your test? Is it based on TI chips? If so, which Z-Stack version and example does it use?

  • 0 in reply to YiKai Chen
    Intellectual 660 points
    Hi YiKai,

    Thanks for the quick response... I am using Z-stack 1.2.2.a on the USB dongle. The device under test is a Securifi Motion Sensor that is HA 1.2 compliant device.

    As I explained, the strange behaviour is that they worked reliably until I powered up a 2nd Zigbee coordinator (my assumption of the Samsung Hub)
  • 0 in reply to hobieboy
    Guru 735695 points
    If it's Securifi Motion Sensor stoping working, I suppose you can only contact Securifi to help you finding the issue.
  • 0
    Prodigy 40 points
    When I use CC2531 as coordinator it uses PanID 1A62 on Channel 11.
    I attach a Philips Hue bulb to it, it joins the PanID 1A62 on Channel 11.

    I poweroff CC2531 coordinator, the Philips Hue bulb is powered on only, it creates a zigbee network with PanID 1A62 on Channel 11.
    I poweron CC2531 coordinator, it creates a new zigbee network on the next available PanID "1A63", id is increased by 1. if network is busy as well it will create PanID 1A64. Meanwhile the powered on Philips Hue bulb stays on 1A62.

    This meaning i need to turn off all my devices on PanID 1A62, only then I can turn on my 1A62 coordinator that is the CC2531 device,only after that I can turn on my philips hue bulbs which all will be on the 1A62 PanID communicating with eachother.

    Might be or might not be your case, hope it helps.
  • 0 in reply to Sofia Sofia
    Intellectual 660 points

    Thanks for the suggestion Sofia, I'll look into that!

  • 0 in reply to hobieboy
    TI__Mastermind 35070 points
    Hi,

    The hub likely implements a Zigbee coordinator. Sniff each channel (11-26) for possible activity.

    Since this happens with a Securifi Motion Sensor, please check if you can reproduce similar behavior with an unmodified out of box example from Z-Stack 1.2.2a.

    If further analysis is required, please post a sniffer log and point out when you observe the mysterious behavior.


    Regards,
    Toby