CC2640R2F: Regarding HCI_EXT_SetFastTxResponseTimeCmd command usage.

Hi Atul,

in my understanding, this setting only matters if you're using slave latency. Fast tx activated will avoid any delay through slave latency and will send the response with the next coming connection interval. This leeds to a faster response but higher current consumption. So, it is a trade off of what is more important.

I don't know what your warning about multirole applications is about, but this setting only makes sense in slave role.

I already had trouble in a multirole application:

I'm working on a project zero based project using SDK 4.30.00.54. This is stated in the functions documentation in hci.h : 

/**
* Set Fast TX Response Time
*
* This command is used to configure the Link Layer fast transmit response time
* feature. The default system value for this feature is
* @ref HCI_EXT_ENABLE_FAST_TX_RESP_TIME. When the Host transmits data, the
* controller (by default) ensures the packet is sent over the LL connection
* with as little delay as possible, even when the connection is configured to
* use slave latency. That is, the transmit response time will tend to be no
* longer than the connection interval. This results in lower power savings
* since the LL may need to wake to transmit during connection events that would
* normally have been skipped. If saving power is more critical than fast
* transmit response time, then this feature can be disabled using this command.
* When disabled, the transmit response time will be no longer than slave
* latency + 1 times the connection interval.
*
* @note This command is only valid for a Slave controller.
*
* @par Corresponding Events
* @ref hciEvt_VSCmdComplete_t with cmdOpcode @ref HCI_EXT_SET_FAST_TX_RESP_TIME
*
* @param control @ref Fast_TX
*
* @return @ref HCI_SUCCESS
*/

I deactivated this feature at the end of ProjectZero_init()

HCI_EXT_SetFastTxResponseTimeCmd(HCI_EXT_DISABLE_FAST_TX_RESP_TIME);

You should check the corresponding event if it worked.

Cheers 

Oliver