• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 340 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.

what is the meaning of Request connection parameters in CCS

Natalie Tsai
Prodigy 615 points

Hi team,

I am using Connection Control Service (CCS) in a project which was in sensortag. I can write comment to change the connection interval now. I use packet sniffer to know the value. however, could somebody explain the range of the parameter?

<Request connection parameters> CCC2 * Write 8 bytes write: max. connection interval, min. connection interval, slave latency, supervision timeout (2 bytes each)

for example, 

when I send 5c036c0300005001, it is for 1 sec connection interval.

if I want to change it for 2 sec connection interval, how can I know my parameter? thanks

BR,

Natlaie

  • 0
    TI__Guru 57865 points
    Hi Natalie,
    I believe to format is same as in the Bluetooth Spec.;

    Value 800 decimal (0x320 in hex)) would be 1s connection interval (1.25ms stepping) So two seconds would be 1600 decimal (0x640 in hex).

    You write 5c 03 6c 03 00 00 50 01;
    max. conn: 5c 03 => 0x0352 => 850 => 1062.5 ms
    min. conn: 6c 03 => 0x036c => 876 => 1095 ms
    slave latency: 00 00
    Supervision timeout: 50 01 => 0x0150 => 336 => 3360ms

    This will allow iOS to set a connection interval around 1s (actually between 1062.5 ms and 1095 ms)

    Best Regards
    Joakim
  • 0 in reply to J Lindh
    TI__Guru 57865 points
    And to answer the title; The point of the service is that you cannot set the connection parameters from iOS (it's prohibited). The only way to change the connection parameters is if the connected device requests new parameters. This is typically embedded, however the CCS service allows an iOS app to set the connection parameters from the App itself (which is then sent from the connected device as a request) so it's actually an workaround for the limitation.