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.

LAUNCHXL-CC26X2R1: "Connection Event" duration

Part Number: LAUNCHXL-CC26X2R1

Tool/software:

Hi.

In the first description in the “GAP Connection State” section of the BLE5-Stack User Guide, the connection event is described as follows.

> A BLE device can be either in the Central or Peripheral role in the Connection State. After devices enter connection state, the devices exchange data under specific time within a specific time slot. This slot where the data is exchanged is called a Connection Event.

How long is the “specific time slot” in this statement?


Can it be considered the same time as the connection interval?

Best regards.

  • Hi !

    In BLE, the peripheral and the central exchange data during a connection event. These connections event last for a period of time which has no definitive name in the bluetooth specification. In the BLE user guide we refer to both as a connection event window

    The anchor point is the "specific time" and the connection event window is the "specific time slot". While the connection interval, AKA the time between two anchor points, can be set by the user, the connection event window is defined by the central and peripheral when exchanging the CONNECT_IND and AUX_CONNECT_REQ PDUs. You can read more about it in the chapter 4.5.3 Connection event transmit window of the BLE Specification :

    to allow the Central to efficiently schedule connection events for multiple
    connections or other activities it may be involved in, the Central has the
    flexibility to schedule the first connection event anchor point at a time of its
    choosing. The CONNECT_IND and AUX_CONNECT_REQ PDUs include
    parameters to determine when the Central sends its first packet in the
    Connection State to set the anchor point and when the Peripheral listens.


    The CONNECT_IND and AUX_CONNECT_REQ PDUs include three
    parameters used to determine the transmit window. The transmit window starts
    at transmitWindowDelay + transmitWindowOffset after the end of the packet
    containing the CONNECT_IND PDU or AUX_CONNECT_REQ PDU, and the
    transmitWindowSize parameter shall define the size of the transmit window.
    The connInterval is used in the calculation of the maximum offset and size of
    the transmit window. The transmitWindowOffset and transmitWindowSize
    parameters are determined by the Link Layer

    Kind regards,
    Maxence

  • Hi.

    Thanks for the reply.

    I understand very well.

    Thank you for even providing the reference to the Bluetooth core specification.

    Best regards.