• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 166 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.

CC2340R2: Low Power Wireless communication

Drake Burtrum
Prodigy 130 points

Part Number: CC2340R2
Other Parts Discussed in Thread: CC2340R5

Hello,

I'm looking for a device that's capable of low power, short distance wireless communication. I was thinking Bluetooth or radio might be the best option. I don't have much experience with wireless communication. The application will require up to a dozen senders in close proximity transmitting to a single receiver. Signal saturation would be a concern. Line-of-sight communication won't be a possibility as there will be multiple obstructions. Let me know what you think might be the best possibility for this type of situation. 

  • 0
    TI__Genius 15844 points

    Hello Drake Burtrum,

    There are a few paths here that we could take.

    First I want to ask if you ever plan on needing your device connect to a phone or laptop, if this is the case then you would need to peruse a Bluetooth application. 

    If not using Bluetooth you can easily use our proprietary rf (proprf) PHYs like the GFSK or MSK PHYs in SmartRF Studio 8. 

    Next what is the data rate? If you need a high data rate then 2.4 GHz would be a good option on the other hand if the data rate is slow you could switch to sub-1 GHz.

    For range sub-1 GHz is the best but if you are around 30 meters or so 2.4 GHz should be reliable (2.4 GHz can still go higher than 30 meters). 

    Drake Burtrum said:
    multiple obstructions.

    Can you describe these obstructions? I have tested the CC2340R5 device in office with ~8 cubicles in the way non line of sight at 30 meters while still being able to receive data. 

    As for signal saturation I don't know exactly what you are doing but if you are doing something like each device has an address, each device is given a time slot to communicate and the receive device can process the data in the windows between the time slots you should be ok; but details are important here to make a definitive conclusion. 

    Thanks,
    Alex F

  • 0 in reply to Alex Fager
    Prodigy 130 points

    The device will most likely need to connect to a desktop. We will probably want a high data rate. 30 meters should be around the upper limit for range. 

    This will be used in a factory setting. Obstructions can include walls, windows, and machines. 

    The devices will be placed close together. Around 6" apart if I had to guess. I've heard that radio signals can saturate when placing multiple transmitters in close proximity. Each device will need an address so that the receiver can identify which transmitter it came from. We can give each device a time slot to communicate and receive data with time to process. This will be a high-speed environment. Ideally, the whole communication process would take less than a second per signal transmission. 

  • +1 in reply to Drake Burtrum
    TI__Genius 15844 points

    Hello Drake Burtrum,

    If you need to connect to a desktop wirelessly (not via UART) then you would need to peruse a BLE solution. We do have quite a few useful getting started guides and examples in the SDK. 

    SimpleLink Low Power F3 Environment Setup Guide

    SimpleLink basic_ble example

    As for device you may be able to have the sensors be CC2340R52 but the receiver would likely need to be CC2340R53 because it would need to store connection information so it would need more space for the NVS region. If the sensors communicate with each other then all devices would likely need to be CC2340R53.

    Drake Burtrum said:
    The devices will be placed close together. Around 6" apart if I had to guess. I've heard that radio signals can saturate when placing multiple transmitters in close proximity. Each device will need an address so that the receiver can identify which transmitter it came from. We can give each device a time slot to communicate and receive data with time to process. This will be a high-speed environment. Ideally, the whole communication process would take less than a second per signal transmission. 

     I have placed two CC2340R5 launchpads 1 inch from each other (TX/RX) and they were ok, the BLE stack should handle the address, timeslot and so on. 

    Thanks,
    Alex F