• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 52 subscribers
  • Views 290 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: BLE connection interval problem

JUNHO KIM
Prodigy 150 points
Part Number: CC2640R2F

Hi.

I'm using two cc2640r2f launchpads.

I uploaded simple_cental and simple_peripheral examples.

I tried to change the connection interval and succeeded in doing it. I checked the current consumption.

But after a while the BLE connection was disconnected.

I think that there are some rules in setting connection parameters.

I want to make sure that the devices are not disconnected.

What are some reasons why BLE connection is broken?

Thank you.

  • 0
    Guru 735685 points
    I suggest you to use sniffer to check what happens over the air.
  • 0
    TI__Guru 57865 points
    Hi Junho,
    As YK recommends, are you able to provide a sniffer capture where the disconnect occurs, or by debugging figure out why it happens?
  • 0 in reply to J Lindh
    Prodigy 150 points

    Thank you for your advice.

    I replied late because I purchased a sniffer module and tested it.

    first figure shows the simple peripheral and smartphone app (android) connection.
    I think Empty PDU means connection signal and they work very well.


    But if I used simple peripheral and central, I couldn't see any data even when I read and write data. (figure 2)


    I want to make central board similar to android.

    How can I do it?

  • 0 in reply to JUNHO KIM
    Prodigy 150 points
    I tested ble stack simple central (not BLE5) and it worked like android.

    Is there any problem in BLE5 stack?

    Best regards
  • 0 in reply to JUNHO KIM
    TI__Guru 57865 points
    You are correct that Empty PDU means that the connection is up and running. In your second sniffer capture, there seem to not be an successful connection, although I must say that there seem to be something fishy going on with the sniffer since it's indicating that the Slave sends the CONNECT_REQ which is incorrect. What modifications have you done to the project?