nrfxlib API 3.3.99
Loading...
Searching...
No Matches

LE CIS Established [v2]. More...

#include <sdc_hci_cmd_le.h>

Data Fields

uint8_t status
 
uint16_t conn_handle
 
uint32_t cig_sync_delay: 24
 
uint32_t cis_sync_delay: 24
 
uint32_t transport_latency_c_to_p: 24
 
uint32_t transport_latency_p_to_c: 24
 
uint8_t phy_c_to_p
 
uint8_t phy_p_to_c
 
uint8_t nse
 
uint8_t bn_c_to_p
 
uint8_t bn_p_to_c
 
uint8_t ft_c_to_p
 
uint8_t ft_p_to_c
 
uint16_t max_pdu_c_to_p
 
uint16_t max_pdu_p_to_c
 
uint16_t iso_interval
 
uint32_t sub_interval: 24
 
uint16_t max_sdu_c_to_p
 
uint16_t max_sdu_p_to_c
 
uint32_t sdu_interval_c_to_p: 24
 
uint32_t sdu_interval_p_to_c: 24
 
uint8_t framing
 

Detailed Description

LE CIS Established [v2].

The description below is extracted from Core_v6.3, Vol 4, Part E, Section 7.7.65.25

This event indicates that a CIS has been established, was considered lost before being established, or—on the Central—was rejected by the Peripheral. It is generated by the Controller in the Central and Peripheral. The Connection_Handle parameter shall be set to the value provided in the HCI_LE_Create_CIS command on the Central and in the HCI_LE_CIS_Request event on the Peripheral.

The CIG_Sync_Delay parameter is the maximum time, in microseconds, for transmission of PDUs of all CISes in a CIG event (see [Vol 6] Part B, Section 4.5.14.1).

The CIS_Sync_Delay parameter is the maximum time, in microseconds, for transmission of PDUs of the specified CIS in a CIG event (see [Vol 6] Part B, Section 4.5.14.1).

The Transport_Latency_C_To_P and Transport_Latency_P_To_C parameters are the actual transport latencies, in microseconds, as described in [Vol 6] Part G, Section 3.2.1 and [Vol 6] Part G, Section 3.2.2.

The PHY_C_To_P parameter indicates the PHY selected for packets from the Central to Peripheral. The PHY_P_To_C parameter indicates the PHY selected for packets from the Peripheral to Central.

The remaining parameters are the corresponding parameters of the CIS (see [Vol 6] Part B, Section 4.5.13.1).

If this event is generated on the Peripheral with a non-zero status, the Controller shall delete the Connection_Handle and any associated ISO data paths.


The documentation for this struct was generated from the following file: