• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 2087 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.

star network configuration for CC1310

erik lee2
Genius 3060 points
Other Parts Discussed in Thread: CC1310, TPL5111

Hi,

If setting the CC1310 as the star network type, how many end-node can the central receiver connect to?

what major things need to consider?

actually i need to set 100+ sets of CC1310 in a network, but i cna't set it to be mesh type, because i need to use the TPL5111 to cut off the power of CC1310 to lower the power consumption. 

  • 0
    TI__Genius 9180 points

    I suggest that you look at the EasyLink Wireless Sensor network example in TIRTOS. Download the version 2.14.03.28 of TI RTOS for SimpleLink MCU's from here:

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/tirtos/index.html

    Open the resource explorer in CCS and iport the projects under "SimpleLink Wireless MCU->CC1310F128->CC1310 Development Kit->Driver Examples->Rf Examples->RF Wireless Sensor Network Concentrator" and "Sensor Network Node".

    This will give you an example of a simple star network using CC1310 DK's.

    The EasyLink Examples are all based on the "EasyLink API" (which is apart of the examples) which abstracts the RF driver to make it easier for customers to create proprietor applications. If you need to connect a host then there is an AT Network Processor example which can be used to interface the CC1310 to a host MCU via the UART.

    Regarding the question:

    erik lee2 said:

    If setting the CC1310 as the star network type, how many end-node can the central receiver connect to?

    what major things need to consider?

    This is a very hard question to answer with out more details, one of the most basic considerations is "how much data does each node need to send".

    The overriding limitation is the OTA bandwidth available, which will depend on may factors. The default setting in the example is 50kbps 2GFSK modulation, which gives an OTA bit rate of 50kbps. You can consider this as your maximum, but there are other factor such as interferes which will reduce this. There is also application level details like the requirement for acknowledgements and arbitration between nodes that need to be taken into account.

    As a very simple model we can assume:

    • 50kbps BW
    • A requirement for acknowledgements
    • No interference (maybe unrealistic)
    • 10 byte data packet and 8 byte acknowledgement
    • Each sensor sends data every 1s
    • You have some mechanism to stop sensors talking over each other like network synchronization or Listen Before Talk (of which non are currently implemented in our examples)

    So this VERY simplistic model produces a theoretical node limit of:

    BitPerSecond_AvailableBandWidth - (BitsPerNode + BitsPerAck )

    50kbps / ((10B + 8B)*8) = 347 Nodes

    Note that the last assumption will reduce the available BW, in either packets used to sync the network, or in "dead" time caused by an "LBT back off". You will also need to take into account SW time taken to process packets and send Acks, but this should be negligible. 

    Regards, TC.