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.

CC1310: CC1310 Star Network

Part Number: CC1310

Hi forum!

I am looking for a star network solution using the CC1310/CC1312.

I read the TI's implementation of 802.15.4

It utilizes CSMA/CA for data exchange once the network is establshed.

I really liked the network association/dissociaton and etc for establishing and mantaining the network using beacon and non beacon modes.

I believe my application is even simpler:

1.I have a co-ordinator device setup very similar to the one setup in the coordinator example.

2.End devices broadcast their data to all the nodes in the network once every second at their designated/programmed slot,there is no unicasting or private data exchange between any 02 nodes.every node always shares its data to all the peers hence making the CSMA/CA useless in my case.

3.The broadcast decision to be made by every end node may be based on either CSMA/CA,LBT or TDMA.

However,

1. CSMA/CA creates hidden node problem so I am trying to avoid it.

2. LBT also does not solve my problem.

3. Retries add overhead and contention into the system.

4.TDMA solves my problem but i want to implement the network management using the out of the box 802.15.4 to save time and effort while TI 802.15.4 doesnt have TDMA implemented. 

Please suggest if I can use the already implemented TI's 802.15.4 and modify it as per my application or any other design philosophy that might solve my problem.

Best Regards

Ali Awan

  • Hi Ali,

    Could you maybe describe a bit more about your application? Do you require all the IEEE PHY features or you only need the frame format?

    There is a few different option that I see here.

    1. You could try tweak the TI15.4 stack offering to sort of fit your ultimate need
    2. Only use the MAC part of the TI15.4 stack to implement your own stack
    3. Write our own proprietary stack using the RF driver and the IEEE commands (the Technincal Reference Manual and Proprietary User's Guide is the documentation in this case).

  • Hi M-W!

    My application is very very simple.

    I have a co-ordinator node that will initiate the network and it may have as many nodes attached to it as possible initially unknown.

    The nodes may be as little as 5 or as many as 25.I want to benefit from the way 802.15.4 initially builds the network using CSMA/CA and beacon transmission.

    Power is not an issue, the nodes may transmit anytime as and when required.

    Once the network has been setup, the co-ordinator may poll each end device to allow broadcasting at the designated time slot. As the nodes enter the network, they may be assigned a broadcasting sequence ID say the first end device gets the ID 01 and the 25th node gets the ID 25.

    In a TDMA fashion, the co-ordinator may poll every node in the network in a round robin and exhaust the nodes from 01 to 25.

    Once a node receive the command  from the co-ordinator to broadcast its data, that node shares its sensor information to the entire network by broadcasting at a fixed frequency to be received by all the nodes.

    I do not want an IEEE or 802.15.4 specific functionality, I just want what I have shared.

    The only functionality I would like to utilize in my application is the way the co-ordinator sends a beacon in the network after a regular interval to sense the active number of end devices in the network and re-assign TDMA slots to end devices accordingly.

    A node may enter or leave the network at any time without compromising the efficiency of the network say if the number of nodes reduce from 25 to 20, the TDMA slots should automatically be reduced to 20 to keep maximum efficiency in the system.

    If the TI's implementation of 802.15.4 serves my purpose I shall be really glad to implement it right away.

    Best Regards

    Ali Awan

     

  • Hi Ali,

    It sounds like you are better of going with your own implementation. While you could potentially work around the TI15.4 stack and "bend it to your will", I suspect this will make for more headache then implementing what you want yourself using the RF Driver. 

  • Thank you M-W

    I guess that would be more appropriate...

    :)