• State Resolved
  • Locked Locked
  • Replies 18 replies
  • Subscribers 58 subscribers
  • Views 3000 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.

Need Suggestion for Mesh network stack

Nipam Bhavsar
Intellectual 620 points
Other Parts Discussed in Thread: CC1310, Z-STACK, CC2538, CC2530

Hello,

We are working on one project in which we require mesh topology to cover more distance, more reliable communication. Our system requires two types of configuration, one is Master(Co-ordinator) and another is Slave(End-points). We found solution in TI like Zigbee(Z-stack - CC2538) and 6LoWPAN (CC1310) software stack.

But after exploring both the stacks, we found that to achieve mesh topology both stacks require extra routers(another configuration than co-ordinator and end-point). We found similar solution with "Digi Mesh protocol" but we want to go with TI solution. So our queries related to mesh topology and required software stack for the same.

Please find below our queries.
1) Does Zigbee(Z-stack) support "router+end-point" configuration simultaneously?
2) Is there any other software stack available which satisfies our requirement?
3) Please suggest solution other than mesh topology in which our requirement will be satisfied.

Any help in this case is appreciated.

Thanks,
Nipam

  • 0
    Intellectual 350 points

    Have look at the Radiocrafts modules with Tinymesh protocol. These are very easy to configure and use. All nodes that are mains powered will act as end point and router. You may also have pure end points for battery operated device.

  • 0
    Guru 735695 points
    Want do you mean to support "router+end-point" configuration simultaneously?
  • 0 in reply to YiKai Chen
    Intellectual 350 points
    It means that every node in the network can receive / transmit data from its local UART port or I/O pins. At the same time this node can re-transmit messages in the mesh - being a router.
  • 0 in reply to Peder Martin Evjen
    Guru 735695 points
    It sounds just a normal Zigbee router can do it.
  • 0 in reply to YiKai Chen
    Intellectual 620 points
    Hi Yikai Chen,

    Router+End-point configuration means node contains routing table as well as send node's data (i.e. Sensors attached with node) to co-ordinator.

    Thanks,
    Nipam
  • 0 in reply to Peder Martin Evjen
    Intellectual 620 points
    Hello Peder Martin Evjen,

    Thanks for suggesting Radicrafts modules. We are looking into those modules and checking that it is suitable or not.

    Thanks,
    Nipam
  • 0 in reply to YiKai Chen
    Intellectual 620 points
    Hello YiKai Chen,

    Let say if we consider two configuration, one is Master(works as Co-ordinator) and other is Slaves(work as Router - minimum 100 nodes) interfaced with all sensors. Now we want to send all sensors readings to Mater(co-ordinator) configured with zigbee mesh network at some particular interval. Is it possible to achieve mesh topology by using these configurations?

    Thanks,
    Nipam
  • 0 in reply to Nipam Bhavsar
    Guru 735695 points

    I see no problem to achieve this using Zigbee mesh network.

  • 0 in reply to YiKai Chen
    Intellectual 620 points
    Hello YiKai Chen,

    Thanks for your confirmation regarding these configurations.

    One more question is can you please suggest SoC and evaluation board so that we can move further in development? Is CC2538 suitable?
    Our master(co-ordinator) and slave devices(Routers) will be battery operated. Do all devices consume more power because of Co-ordinator and Routers configuration?

    Thanks,
    Nipam
  • 0 in reply to Nipam Bhavsar
    Guru 735695 points
    1. CC2538 or CC2530 are suitable and you can buy CC2538DK or CC2530Dk.
    2. Zigbee coordinator and router consume lots of power so it is not suitable for battery power.
  • 0 in reply to YiKai Chen
    Intellectual 620 points
    Hello YiKai Chen,

    Oh! again we stuck to decide mesh network stack. We expected that finally we get confirmation regarding zigbee.
    We found another variant of zigbee, Digi mesh protocol, supports mesh topology. Is there any device support available for Digi mesh in TI?

    Thanks for your all kind support.

    Thanks,
    Nipam
  • 0 in reply to Nipam Bhavsar
    Guru 735695 points
    I don't think TI would support this Digi mesh unless Digi mesh is actually Zigbee mesh network.
  • 0 in reply to YiKai Chen
    Mastermind 9802 points

    Note that Digi's Zigbee stack implementation is by default NOT compatible with the Zigbee Pro 2007 specification; they use their own proprietary implementation.

    There is no TI support for compatibility with Digi-Mesh.

    If you want to get going quickly, just use the A2530 module from Anaren - it has the full Z-Stack on it and has a SPI interface to a host MCU. That way you don't need to get bogged down with the network stack.

  • 0 in reply to YiKai Chen
    Intellectual 620 points
    Thanks YiKai Chen for confirming about Digi mesh.

    Can you please suggest us if any solution is available for sub-1 GHz(like CC1310, CC430)?

    We found that CC1310 supports mesh using 6loWPAN but same thing 6loWPAN also needs extra routers to achieve mesh topology.
    Kindly give your suggestions regarding Mesh network, whether is it possible to achieve mesh without using Routers or not. We do not want to go with Ready made modules.

    Any other solutions are also appreciated.

    Thanks,
    Nipam
  • 0 in reply to Nipam Bhavsar
    Guru 735695 points
    Router is mandatory in mesh network. No matter you use Zigbee or 6LowPAN.
  • 0 in reply to YiKai Chen
    Intellectual 620 points
    Thanks Yikai Chen for clearing all doubts about mesh network.
  • 0 in reply to Nipam Bhavsar
    Guru 735695 points
    You are welcome.
  • 0 in reply to Nipam Bhavsar
    Expert 1525 points
    A note regarding terminology seems suitable here: a router is able to route packets for other devices (and itself of course). In Zigbee, routers need to be always on, ie batteries are not suitable. End-points on the other hand may be duty cycled and battery operated, but they do not route packets, hence called "end-points". Zigbee routers require lots of RAM and flash, meaning that, depending on drivers and the application, a device may need to be dedicated router and not do anything else. This means that a Zigbee network other than trivial will be stars of stars and need lots of dedicated routers connected to mains power. A hefty cost and cumbersome requirement that may exclude more than trivial products with small networks and simple applications.

    A 6lowpan network on the other hand doesn't make this distinction. A device may route and run an application at the same time, while also being duty cycled. It depends on the protocols in use in the stack and how they are configured. 6lowpan typically means that you are running {IPv6, 6lowpan adaption layer, TCP/UDP, 802.15.4 for some PHY and network stuff}, but is really not set in stone. RPL is a common routing protocol.

    As a reference point, we run cc1310-devices as battery-operated 6lowpan devices that are application devices (ie remote sensing, or actuation etc) and routes packets in self-healing mesh networks many hops deep. No need for special "router devices". Have a look at my profile if you want to hear more on this.