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.

CC2652R: PER measurement for different peripheral connections

Part Number: CC2652R

Hello,

I am trying to implement Packet error rate information collection. The weird thing that I have encountered is that parent event of HCI_EXT_PER, namely HCI_VE_EVENT_CODE doesn't provide connHandle information. This can be seen here in line 1071 of hci.h  (this is the structure connected with HCI_VE_EVENT_CODE event):

For other events, there is often a connection handle provided - for example in line 1094.

So, my question is this really the case that we can not distinguish between connections in case of PER raport event? Or there is some other way how we can achieve it?

  • Hi,

    The HCI_EXT_PacketErrorRateCmd() is used for reading and resetting the PER counters in a connections. One of the parameters that is passed to this function is the connection handle. So when the function is called we know which connection handle we are referring to, so when the event is received it should correspond to the connection handle used to read the PER.

    Best Regards,

    Jan

  • Hello Jan,
    Sure thing, but this makes it only more weird :) Why does API need this connection handle to be passed and then it is not giving this information back? So basically most important question here is: Do I have to implement a queue with devices, which will make PER being checked only on one device at the time? In perfect world I would do all PER in parallel (that would require the smallest amount of code with good quality and small complexity) but then I need to know for which device is the data that I am obtaining.

  • Hi Karol,

    When calling the HCI_EXT_PacketErrorRateCmd() for a specific connection handle, then I would expect the first HCI_EXT_PER event back would correspond to the first call of the function. So you should be able to distinguish which HCI_EXT_PER event corresponds to which by keeping track of call order.

    Best Regards,

    Jan

  • Ok, thanks Jan.