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-CC2640R2: Connection interval VS power consumption and notification

Part Number: LAUNCHXL-CC2640R2
Other Parts Discussed in Thread: CC2640

Dear Sir or Madam:

When i'm testing the connection interval influence on power consumption. I encountered some problems, one is that on TI Github throughput testing, it says the larger the connection interval, the larger the throughtput. However when i go throught the TI CC2640 developer guide it shows below, that higher interval means lower throughtput.

Is that i misunderstand the meaning or not? 

And another problem is about the notification. When the slave want sent a notification, it must wait until the next connection, right? And in each connection, how many notification can i send? One or multiple?

Thanks,

Jianan

  

  • Hello Jilanan,

    The power consumption is determined by the active time of the radio & MCU and the sleep current. So, if you use a long connection interval and send continuous packets during the connection event (CE), then it will be the same as a faster connection interval where you continuously send data throughout the event. This is an a-typical condition in BLE - the nominal case is to send data infrequently such that you mostly send empty connection events. In this case, having a longer connection event results in lower current consumption. I suggest reading app note SWRA478 which details how to measure current consumption.

    There is no defined limit on the number of Notifications that can be sent during a CE, although memory and peer device capability may impose limitations.

    Best wishes
  • Hi JXS:

    For that i can continuously send data during a event. I'm not that really understand.
    If i set the interval connection as 100ms, but i send a notification every 10ms. Can i receive the package ever 10ms?
    When i testing it, i only can receive the package every 100ms.

    Thanks,
    Jianan