• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 55 subscribers
  • Views 844 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.

Ideal topology for TI HA Gateway(BeagleBone) - CC2530(with/without CC2591)

cyclonmaster geostigma
Expert 1030 points
Other Parts Discussed in Thread: CC2591, CC2530, Z-STACK

I wonder what is practical range of CC2531-CC2530(with CC2591) indoor? It's said in datasheet can support up to 1000m outdoor, CC2530(without CC2591) 100m outdoor. As I test it roughly around 17m range only. More than that it's ittermittently connect/disconnect with coordinator. CC2530(without CC2591) much worst, might be 5m for stable range.

This is star topology, coordinator to many Endpoint(samplelight).

Then I extend it much further using Coordinator-many Router(samplelight)-many Endpoint(samplelight). This is mesh network right? Seem that I can extend the network further this way. Unfortunately, reconnection router/endpoint to coordinator took really much more time(1-2minutes). Sometimes it's failed to connect/disconnect by itself. Turn On/Off light also had a delay. Sometimes no response due to disconnection.

There is just release TI Z-Mesh stack, if I want to use this integrate to HA stack. How can I proceed? Will it give some improvement to the network?

For normal 2 storey house with around 20 lights/devices, should I go star or mesh? What topology would you all recommend? For mesh, how many routers/endpoint should there be for 20 lights?

Thanks

  • 0
    Guru 735685 points

    1. According to my experiences, CC2530 without PA/LNA can have about 100m in free space and about 50 m under indoor test. However, it depends on how your partition is. This number is tested in my office. If you have concrete in between ZC and ZED, the distance will be decreased. For CC2530+CC2591, I can have about 250m in free space and about 100m under indoor test.

    2. TI Z-Stack Home support mesh network based on HA profile. I don't see the reason why you change to TI Z-Mesh stack if you have to do HA compliant.

    3. For a 2 story house, I would suggest using mesh network.

  • 0 in reply to YiKai Chen
    Expert 1030 points

    Getting at least 50m range is impressive. I can get that range too but really hard to get it stabilize. Always disconnected. How's yours? Is it stable and remain connected to the coordinator all times?

    In samplelight, there is still a LCD Display code which I did not use. If I get rid of that code, do you think I can get better performance in term of connectivity? CC2530+CC2591 17m and less is really bad. If it within in between wall could be worst.

  • 0 in reply to cyclonmaster geostigma
    Guru 735685 points

    1. Our products are stable when connection.

    2. Do you define HAL_PA_LNA in your project when you use CC2530+CC2591? 

  • 0 in reply to YiKai Chen
    Expert 1030 points

    Yes, I already enable HAL_PA_LNA inside hal_board_cfg.h

    What I test so far:

    1. Star Topology: Coordinator-Many Zigbee End Devices(Lights) , worst connection. Only suitable for short range(less 17m)

    2. Mesh Network: Coordinator-Many Routers(Lights)-Many Zigbee End Devices(Lights), Can connect many devices. Unfortunately, Zigbee End Devices(Lights) suffers disconnection problem frequently since it only connect to routers. Not in full mesh network. I wonder this setup makes ZED only connect to ZR and not to ZC?

    3. Mesh Network: Coordinator-Many Routers(Lights). The best connection so far. All devices connecting to each other.

    Right now, I make all the light as router. But sometimes some lights get disconnected. In this case, I cannot control the light from the coordinator anymore. When you are away from home this will be a problem.

    How do you propose to solve the disconnection problem? In cease the lights get disconnected from coordinator, how to make it auto recover and reconnect to coordinator again?

    Thanks.

  • 0 in reply to cyclonmaster geostigma
    Guru 735685 points

    I suggest you use Ubiqua Packet analyzer to check why your lights get disconnected. You have 3 cases and they might have different root causes to this uncontrollable issue. You should verify them one by one. If I don't know the root cause, I can't give you suggestion.

  • 0 in reply to YiKai Chen
    Expert 1030 points

    I had enable NV_INIT & NV_RESTORE in compile option. I get confuse, is it NV_RESTORE or NV_RESTORE=TRUE?

     

    Let's say I have a stable connection. In the case of power failure, how to recover the connection between coordinator and end device? Will enable NV_INIT & NV_RESTORE in compile option above helps?

     

    I had cases where the end device disconnected, it did not want to return to connect to coordinator. Even if I bring it close to coordinator. until I reset it, or power off/on, then it will back connecting.

  • 0 in reply to cyclonmaster geostigma
    Guru 735685 points

    1. It is NV_RESTORE.

    2. When ZED is out of radio coverage or ZC is turned off, ZED will send orphan mortification and start beacon. If ZED returns into radio coverage or ZC is back, it will rejoin to ZC.

    3. You have to use Ubiqua Packet Analyzer to check what happens.