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: Using ll_sheduler to get the next connection event?

Part Number: LAUNCHXL-CC26X2R1

Hi,

I am using the simple peripheral project. There are 3 centrals connected to the peripheral. Each with different connection intervals. I need to set a different pin for the peripheral in the user task depending on which central the next connection event is for. A good place to do that would be in SimplePeripheral_processConnEvt(). The problem is that the information for which connection the next connection event is happening is not available by means known to me. Since the the ll sheduler should know this information I wonder if we can use some of the exposed api without risking the unexpected behaviour mentioned in ll_sheduler.h

Best Regards

  • Hi Hermann,
    Are you looking for ways to characterise the performance with multiple connections or is this related to application use case? I have assigned an expert on the topic although we have entered national holidays until 23rd, so response might be slow.
  • Hi Joakim,
    it is an application use case which is necessary for a certain antenna arrangement.

    Please take your time and enjoy your holidays!
    Best Regards!
  • At least in simplelink_cc13x2_26x2_sdk_3_10_00_53, the handle is available in SimplePeripheral_processConnEvt(). It is already being extracted and used to find the connection index:

    static void SimplePeripheral_processConnEvt(Gap_ConnEventRpt_t *pReport)
    {
      // Get index from handle
      uint8_t connIndex = SimplePeripheral_getConnIndex(pReport->handle);