• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 192 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CC2652R: Duration of advertising event

CC2652R: Connection event duration

Rahul Chowdary Pinnaka
Prodigy 90 points
Part Number: CC2652R

Hi Team,

I have few queries regarding connection event and it's timing.

1) What is the duration of the connection event which involves one standard packet with standard payload from M->S and S->M ?

2) How long can the connection event be extended ?. I read closing connection events section in Bluetooth spec 5.2. What is the maximum duration a connection event be extended using MD (More Data) bit in the header of the PDU either from master or from slave ?. I am sure it will have some limit otherwise there is no point of having connection interval.

Looking forward to receiving your reply.

Regards

PRC

  • 0
    TI__Mastermind 25810 points

    Hey PRC,

    Rahul Chowdary Pinnaka said:
    1) What is the duration of the connection event which involves one standard packet with standard payload from M->S and S->M ?

    This really depends on a few factors. To name a few, the PHY (1M, 2M, S8), PDU size, MAX_NUM_PDU are the first to come to my head. I would recommend employing the recommendations in the related thread to take some measurements on your particular application.

    Rahul Chowdary Pinnaka said:
    2) How long can the connection event be extended ?. I read closing connection events section in Bluetooth spec 5.2. What is the maximum duration a connection event be extended using MD (More Data) bit in the header of the PDU either from master or from slave ?. I am sure it will have some limit otherwise there is no point of having connection interval.

    This is another factor that affects the duration of the connection event. The factors that can limit the connection event length are, again, the size of the PDU and the MAX_NUM_PDU. The MAX_NUM_PDU is the maximum number of PDUs that the stack can queue. This is explained in more detail in this related post. Your concern is valid, but the maximum duration that can be extended is likely the length of the connection interval. If you limit the MAX_NUM_PDUs, you can ensure you are not extending the connection interval past the limit. However, the stack handles this level of detail with regards to timings (otherwise, we would see erroneous behavior like missed connection events and potentially disconnections).

    I hope this helps.

  • 0 in reply to Ammar N
    Prodigy 90 points

    Hi Ammar,

    Thank you so much for detailed answer. I got clear idea from your answer and related threads to the 2nd question. I just need your help with 1st question. My requirements are 1M PHY with only 1 PDU from M->S and S->M and let's say PDU size is 69 which is minimum with LE secure connections. Please let me know the duration of the LL connection event with these conditions. I am awaiting this timing information for multi_role application. Please help me in this regard.

    Looking forward to your reply.

    Regards

    PRC

  • +1 in reply to Rahul Chowdary Pinnaka
    TI__Mastermind 25810 points

    Hey Rahul,

    The best recommendation I can give to estimate timing on your end application is to enable the RX/TX observables using your application. I believe there are instructions in the related post linked (see here).

  • 0 in reply to Ammar N
    Prodigy 90 points

    Hi Ammar,

    Thanks for the reply. I found the timing details for connection event. Please mark this issue as closed. Thanks for your valuable support.

    Regards

    PRC