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.

What is the Power Consumption to maintain constant connection between CC2640 and iOS (8 and 9)?

Other Parts Discussed in Thread: CC2640

I am working on a project that requires a continuous connection 24/7 between a peripheral device using CC2640 and iOS. There isn't a lot of data exchange between the two devices, but I  have to maintain the connection to improve system responsiveness.

1. What are the connection parameters on the CC2640 to achieve this continuous connection?

2. What is the power consumption on CC2640 to do so?

3. Will continuous advertising in 2 sec interval achieve the same effect?


Thanks,

Bryan

  • Hi Bryan,

    What are you trying to achieve as an end application?

    1) If you want the peripheral (CC2640) to connect to the iOS device then you will want to setup a connection with a long connection interval and long slave latency to save power. This allows the peripheral to wake up as few times as possible, thus saving power.

    2) This guide, www.ti.com/.../swra478.pdf provides a lot of detail about power consumption and how to measure it. It is highly dependent on a multitude of factors, especially the connection parameters mentioned in #1

    3) Continuously advertising sounds more like a beaconing application, this is fundamentally different than a connectable peripheral. It depends on your end use case to determine which is best. You can read more about beacons here: www.ti.com/.../swra475.pdf
  • Hi Sean,

    This is an always on wearable BLE device. There are two-way data exchange between the iOS and this BLE device. Hence, it's essential to maintain the connection on all the time.

    1. iOS has a guideline on connection parameters. Will these parameter settings work and maintain a very low power consumption on CC2640?
    Slave Latency: 4 sec
    Interval Max : 400 msec
    Intercal Min: 380 msec
    Connection Supervision Timeout : 6 sec
    Advertising Interval : 2 sec?

    2. Is it more efficient to maintain the connection using connection interval or using Beacon?

    Thanks,
    Bryan
  • Bryan,

    1. These connection parameters seem reasonable. Again, you want to choose the parameters that result in the fewest peripheral (your wearable) wakeups that are also supported by your central device (iOS). Fewer wakeups means less power consumption

    2. If you need to transfer data bidirectionally, beaconing probably isn't the correct method for you.