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.

CC1350: Asynchronous Mode

Part Number: CC1350
Other Parts Discussed in Thread: CC1101, , CC1310, CC1352R

Hi Ter,

 the customer still has to define the system architecture and protocols. But the features requested are the following:

- star connections with a central module (coordinator module).

- when a particular event happens all peripheral module wake up and they need to acquire internally from sensors two analog values with 100Hz rate for 2 seconds; totally each sensor needs to transmit about 800 bytes.

-transmission can be done during acquisition or at the end at max speed possible, to avoid that next event will happen and will be lost.(time between two events could be 1 sec).

 

Can you suggest if CC1350 as coordinator and CC1310 as peripheral sensor is the best solution , or you mentioned CC1101(that is not preferred because needs external uC)?

Which is the max TX speed used by our stack to support the system?

Do we support 868/915 and 790(for China)Mhz applications?

Is there a specific modulation, packet configuration you could suggest?
Thanks

Umberto

 

  • I can't see that I have received answers to the following:
    Could you give some information about the packet format, modulation, datarate, deviation etc? Is this a legacy system? What performance do they expect/ need to have?

    The chip is not designed for async mode. It's possible but the performance will not be optimal and in most cases using a CC1101 will give better performance.
    ---
    Is async mode still on the table on if that is the case, why?

    dev.ti.com/.../ti154stack-overview.html covers what is supported in the 15.4 stack. If you are not planning to use the stack the datasheet covers which frequencies that are possible.

    - Why do you want to use CC1350 as coordinator compared to CC1310?
    - How many sensors are in use pr coordinator? This is needed to calculate the total data that you have to transmit within a given time periode.
  • Hi Ter,
    CC1350 will be used because they need to connect the coordinator also with BLE.
    There are 4 sensors each transmitting 800 bytes in 1 second.
    Protocol, modulation are customer choice, no legacy issues; looking at the table you could transmit at about 50kb/sec,.
    The transmission was defined by us as asynchronous, because there is no synchronization between sensors, but if there is way to sequentially transmitting sensor infos avoiding any collision, this could be implemented.
    Any comment or suggestion to use our stack as it is?
    Thanks
    Umberto
  • - Note that CC1350 does not have enough flash to run sub 1 GHz and BLE at the same time, you can only do sub 1 and beacons. If they want full BLE, look into CC1352R
    - 800 bytes from 4 sensors is more than 25 kbps of data, not counting preamble, sync. meaning that the datarate should be higher than 50 kbps to get the required throughput.
    - Since the sensors needs to transfer a lot of data in a time slot some sort of sync between the sensors could be useful. Is it an option to let each sensor send each 1 s but sensor1 starts @0, sensor2 @0.25s and so on?