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.

CC2642R: Packet loss using notification

Part Number: CC2642R
Other Parts Discussed in Thread: SYSCONFIG

Hi,

I am using simple_peripheral_oad_onchip and sdk version - sdk_5_10_00_48.

In my application, device sends 230 bytes size packet every 150 ms to connected mobile device through notification. But i found that few of the packet gets loss.

After debugging found that the return value for "GATTServApp_ProcessCharCfg" is 0x16 which defines "blePending".

So i want to know that how packet loss can be avoided?

  • Hi,

    This behavior may occur if the BLE stack has still not managed to send out all the data enqueued so far. You should make sure the throughput available on the link is sufficient to allow the transmission of the data, including in the case  cases where so packets have to be re-transmitted.

    For a first test, you may want to try one of these elements:

    • reduce the connection interval. If needed, you can leverage the peripheral latency to keep the power consumption similar.
    • increase the max size of the PDUs
    • increase the maximum number of PDUs

    All these can be configured using SysConfig.

    I hope this will help,

    Best regards,

  • What should be the ideal connection interval?

    What parameters should be consider while deciding connection interval?

  • Hi,

    The "ideal connection interval" depends on your requirements in terms of power consumption, latency, throughput, etc.

    Regards,

  • Thanks for the update.