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.

BLE- time to establish connection

Hi,

I am considering to implement a product using BLE, and I am of trying to get a basic understanding of the power consumption without going into detailed understanding of the BLE.

Our product is very simple and is intended to be one master-one slave, the master should send a "keep alive" packet every 5 seconds, if the slave doesn't receive it - it will activate a buzzer.

For this I would like to know:

1) What is the typical time for establishing a connection between a single master-slave(how many advertisement packet would I typically need to send), and can I assume that the total power consumption is the sum of the advertisement packet power( i.e the master slave are in sleep mode between these packets transmission?).

2) Would I need to send a separate data packet after the connection was established(assuming the application just needs a very simple keep alive packet without any additional information)?

3) is it possible/ advisable to use broadcast communication for such a product, there's a very low possibility of multiple masters/slaves in one location.

Really I need to know these answers- as a rule of the thumb, and not exact figures, and would appreciate any help from anyone with better understanding of BLE than me,

Thanks in advance

Udi

  • Hi Udi,

    1) This depends on your method of discovery, you can whitelist (connect to only certain subset of devices) this should make the process go quicker. Central device should be able to detect within a couple advertising packets

    2) The BLE stack is responsible to keeping the connection alive, even if no data is transferred

    3) Broadcasters send their data in their advertising packets, this means it would be readable by all devices with a BLE radio, that is a security question that is up to your end application
  • Sounds like you might be using BLE in a product as a way to help people from forgetting important things, am I right :) ? Anyway, the devices will be notified in the application by the stack if the connection drops, so you don't need a keep alive packet, the stack will take care of this for you. Take a look at the simpleblecentral and simplebleperipheral projects, they have code that updates the LCD on connection/disconnection.