How long should connection establishment take when devices are already bound?

RE: How long should connection establishment take when devices are already bound?

Primož Kralj — Wed, 23 Dec 2015 08:07:43 GMT

This topic has helped me to store and load application context using Device Manager.

RE: How long should connection establishment take when devices are already bound?

Primož Kralj — Wed, 23 Dec 2015 07:20:38 GMT

Wojtek, my connection params are OK I think because connection itself is very fast - what takes long time is (as Andrew mentioned in last paragraph) the discovery of services. This is when each event happens (when devices are already bound):

RE: How long should connection establishment take when devices are already bound?

Andrew — Tue, 22 Dec 2015 19:58:00 GMT

To establish a connection faster between two devices, the central needs to be performing a 100% duty cycle scan with the peripheral advertising in the shortest interval. Once the connection is established, you should be using the fastest possible connection interval possible to rebind faster. As far as I know, bonding does not affect speed of connection establishment but only establishes a secure connection.

Central Scan example: Scan window = 50ms Scan Interval = 50ms

Peripheral advertise example: Advertise interval 20ms (fastest allowed)

Central connection interval: 7.5ms (fastest allowed).

This should make things work as fast as possible.

One other thing that can take time is discovery of services and characteristics of the peripheral so if there is any way to store the handles on central that you need in persistent storage, you can skip discovery.

RE: How long should connection establishment take when devices are already bound?

Wojtek — Tue, 22 Dec 2015 15:22:36 GMT

What is your connection interval?