• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 2212 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.

CC2640R2F: CC2640R2 long range examples (difference?)

Crater.J
Prodigy 110 points

Part Number: CC2640R2F

Dear TI Community,

We are using two CC2640R2 launchpad boards to evaluate Bluetooth Low Energy long range functionality. So far we have tried communication between two boards with 2 examples from Github - longrange (central + peripheral) and throughput (central + peripheral).

We have not managed to establish a long range connection (maximum about 10 meters, or less), despite adding a little antenna on the peripheral board. My question is, is there some setting I need to modify in the code or in the menus when using the examples?

And also, when it comes to long range functionality, how is longrange demo different from throughput demo? I see that both of the demos support S8 encoding, with no other major difference at first sight.

Thank you very much and best regards!

J Crater

  • 0
    TI__Guru** 105180 points
    Hello,

    We routinely hear reports of LE Coded PHY connections exceeding 600m+ so I suspect something is amiss with your setup or the modification to the antenna. What is the range when using the default PCB antenna on the LaunchPad? What are the steps performed?

    In terms of longrange demo vs. throughput demo, a connection is a connection and what you do during that connection is up to you. These are just two examples of what can be done on a LE Coded PHY connection.

    BTW, are you using BLE5 SDK 1.50?

    Best wishes
  • 0 in reply to JXS
    Prodigy 110 points

    Hello and thank you for your reply!

    There may be something wrong with the setup/antenna indeed. The range is usually about 10 meters, indoors, with no obstacles on the way. Displayed RSSI (over UART) is then about -90 dBm.

    Thank you for the explanation. I am using BLE5 SDK 1.40. The README on Github exmples page says:
    These examples and demos are for TI SimpleLink CC2640R2 SDK 1.40.00.45
    Should we be using SDK 1.50 after all?

    Best regards,

    JC

  • 0 in reply to Crater.J
    Guru 735695 points
    Yes, it's recommended to use SDK 1.50 for testing.
  • 0 in reply to Crater.J
    TI__Mastermind 33460 points

    Hi JC,

    As YiKai suggests below, SDK 1.50 is the latest and greatest, and contains the latest fixes from the R&D team.

    However, the Github examples have not been ported to SDK 1.50, so they may not work out of the box.

    The major difference between the throughput and LR demos is the throughput is focused on flooding notifications, while the LR demo is intended to be headless for the peripheral and intermittently reports temperature data.

    As JXS highlights, both are demo projects and the data sent over the connection is up to your application.