• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 413 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: How to select the best BLE peripheral connect parameter

jian chen
Prodigy 130 points
Part Number: CC2640R2F
Other Parts Discussed in Thread: BLE-STACK

Hi,

    Thanks for your support. 

    In my project, the cc2640r2f is act as peripheral role. And the issue is that some phones cannot connect to the cc2640r2f successful. I think maybe it is taken by the improper connection parameters. I want to know, does TI have any suggested connection parameters that can cover more phones. or does TI have any manual to help customer to select the best connection parameters.  connection parameters I have mention is as bellow shows

// Minimum connection interval (units of 1.25ms, 80=100ms) for parameter update request
#define DEFAULT_DESIRED_MIN_CONN_INTERVAL 8

// Maximum connection interval (units of 1.25ms, 104=130ms) for parameter update request
#define DEFAULT_DESIRED_MAX_CONN_INTERVAL 800

// Slave latency to use for parameter update request
#define DEFAULT_DESIRED_SLAVE_LATENCY 0

// Supervision timeout value (units of 10ms, 300=3s) for parameter update request
#define DEFAULT_DESIRED_CONN_TIMEOUT 1000

// Pass parameter updates to the app for it to decide.
#define DEFAULT_PARAM_UPDATE_REQ_DECISION GAP_UPDATE_REQ_ACCEPT_ALL//GAP_UPDATE_REQ_PASS_TO_APP

  • 0
    TI__Guru 57865 points
    Hi,
    In your case, it's the smartphone that mandates the connection parameters (Central Role) and our BLE-Stack support all parameters allowed by the BT Spec. Could you please be more specific when you say "cannot connect"?
  • 0 in reply to J Lindh
    Prodigy 130 points

    Hi, thanks for your support!  Perhaps my issue will be described more clearly as following.  My Iphone8 can easily connect success to CC2640R2F , during the connection handshake process, the Uart will print the log  "Pairing started   Pairing started  Pairing success  Bond save success",  but when another phones which cannot connect success start the connection, during its connection handshake process, the Uart will only print "Pairing started Pairing started",  after that  the connection process seems be blocked for a while and return failed.   What's more, I do not know the meaning of the parameter DEFAULT_PARAM_UPDATE_REQ_DECISION, can you tell me the detail difference between its  three values(GAP_UPDATE_REQ_ACCEPT_ALL GAP_UPDATE_REQ_DENY_ALL  GAP_UPDATE_REQ_PASS_TO_APP). 

    Thanks for your kind help.

  • 0 in reply to jian chen
    TI__Mastermind 34660 points
    Hello. The DEFAULT_PARAM_UPDATE_REQ_DECISION parameter, as well as all GAP parameters, is documented in the doxygen:

    dev.ti.com/.../group___g_a_p___params.html

    There is a link there to each individual value:

    dev.ti.com/.../group___g_a_p___constants.html