why connectivity time is not similar

RE: why connectivity time is not similar

RK — Fri, 08 Jan 2016 13:46:17 GMT

Why don't you use the sniffer on both of the connections and see what the difference both in time taken before the central sends the connect request and then the time before the connect request and all the discovery of all the characteristics has completed. Pay attention to the connection parameters which are negotiated, are they the same.

Because there's lots and lots of things can affect the time taken to connect so just listing them down is no real substitute for sniffing the packets and seeing what it does especially as you have a test case to test.

RE: why connectivity time is not similar

makouda — Fri, 08 Jan 2016 13:35:46 GMT

ntoe that I have one service with a set of 12 characteristics, it doesnt affect connection time??

RE: why connectivity time is not similar

makouda — Fri, 08 Jan 2016 13:33:45 GMT

no im advertising continuasly until I connect

RE: why connectivity time is not similar

Wojtek — Fri, 08 Jan 2016 13:32:24 GMT

Are you advertising continuously? Or in intervals?

(ex. like that: 5s advertising---5s sleeping---.....---5s advertising)

RE: why connectivity time is not similar

makouda — Fri, 08 Jan 2016 13:08:17 GMT

It means when I click connect button to connect and show my services. Sometimes it connect instantly and sometimes it turn for seconds before being connected

RE: why connectivity time is not similar

Wojtek — Fri, 08 Jan 2016 12:53:55 GMT

And what is the difference - much more means few secs or what?

RE: why connectivity time is not similar

makouda — Fri, 08 Jan 2016 12:50:07 GMT

My advertising interval is 32 unit's (min)

RE: why connectivity time is not similar

awneil — Fri, 08 Jan 2016 11:48:27 GMT

Could also be influenced by interference, other apps running on the host, etc, etc, ...

RE: why connectivity time is not similar

RK — Fri, 08 Jan 2016 11:16:34 GMT

well what's your advertising interval and what are you connecting to? If your advertising interval is long then the central looking for you may not see you for a while, it has to be listening at the exact time you're advertising. If the advertiser and scanner get 'in sync' and keep missing each other, it can take a while to connect.

RE: why connectivity time is not similar

makouda — Fri, 08 Jan 2016 11:06:47 GMT

the difference is that one connection took more much time then other connection, wating longer to connect

RE: why connectivity time is not similar

Wojtek — Fri, 08 Jan 2016 11:04:35 GMT

What is the difference?