• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 777 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.

CC2650: Throughput test

Seamus Pu
Intellectual 830 points

Part Number: CC2650

Hi Expert,

I'm using CC2650 to do the throughput test, the followings are the details of my setup:

HW: LAUNCHXL-CC2650

SW: https://github.com/TexasInstruments/ble_examples/tree/ble_examples-2.2 with ti\simplelink\ble_sdk_2_02_07_06 

  • throughput_example_peripheral
  • throughput_example_central

I just use the example code and didn't change any thing, the throughput is about 36.6 kB/s.

When I changing the MAX_PDU_SIZE from 27 to 255 in ble_user_config.h, but the result is the same (36.6 kB/s). 

What can I do if I want the throughput increase to 100kB/s?

Best regards,

Seamus

  • 0
    TI__Guru** 101570 points

    Hi Seamus,

    The throughput offered by a Bluetooth connection depends of many elements, such as the connection interval, the number of packets exchanged per connection interval, the number of bytes in each packet, the number of packet re-transmissions, etc.

    May I kindly ask you to provide a Bluetooth sniffer log showing these elements?

    Appreciate your understanding,

    Best regards,

  • 0 in reply to Clément
    TI__Intellectual 830 points

    Hi Clement,

    Sorry, I don't have BT sniffer logs, is there any other way to check these parameters?

    Are all of these parameters in the ble_user_config.h file?

    Best Regards,

    Seamus

  • 0 in reply to Seamus Pu
    TI__Guru** 101570 points

    Hi Seamus,

    I am afraid the elements requested cannot be set statically - they are actually negotiated by the devices participating in the connection or dependent on the environment. 

    You can consider enabling the RF debug signal to attempt to measure the connection interval and the number of packet per connection (see here). This way, using a logic analyzer, you can see the radio activity and guess when the connection events start and the number of packets exchanged.

    Similar approach can be used to assess the length of the packets. Measure the duration of the Tx operations during the connection events for a few different configurations (e.g. for 27 bytes, 69 bytes, 100 bytes, 150 bytes, 200 bytes and 255 bytes). You should expect longer Tx duration when transmitting more bytes. 

    In order to minimize the number of re-transmissions, make sure to run the test in a quite environment, with small amount of Bluetooth and Wifi devices in the surroundings.

    I hope this will help,

    Best regards,