nRF52 Slow To Discover Services In MCP

RE: nRF52 Slow To Discover Services In MCP

WestCoastDaz — Fri, 11 Mar 2016 18:13:15 GMT

Bjorn,

Thank you very much for the tip! That did the trick.

RE: nRF52 Slow To Discover Services In MCP

Bjørn Inge — Fri, 11 Mar 2016 17:49:49 GMT

You say that the connection interval is between 400 and 650 ms, which means one request and response will take around 1 second. If you set the connection interval to 7.5ms, which is the lowest available, the discovery will go much faster.

RE: nRF52 Slow To Discover Services In MCP

FormerMember — Fri, 11 Mar 2016 11:33:27 GMT

Do you use one of the examples in the SDK? If not, do you see the same problem if you use one of the examples in the SDK?

RE: nRF52 Slow To Discover Services In MCP

WestCoastDaz — Fri, 11 Mar 2016 06:45:27 GMT

I am using Wireshark 1.10.14 with the Sniffer 1.0.1_1111. I select the device in the sniffer tool, launch Wireshark, scan using MCP (connected to the same computer as the sniffer) I can see advertising packets in Wireshark but no Scan response packets. I make a connection in MCP, I don't see those packets either or the ones when I perform a service discovery.

RE: nRF52 Slow To Discover Services In MCP

RK — Fri, 11 Mar 2016 06:41:07 GMT

sniffer always works fine for me - you did select the device from the list before going into connection right

RE: nRF52 Slow To Discover Services In MCP

WestCoastDaz — Fri, 11 Mar 2016 06:40:07 GMT

I have 4 services with 3 to 4 characteristics each with 128bit UUIDs. I tried using the Nordic sniffer but it only seems to capture the advertising packs. Several people have posted about this problem with the sniffer and Nordic hasn't really provided an answer except to say it is a problem they are working on.

RE: nRF52 Slow To Discover Services In MCP

WestCoastDaz — Thu, 10 Mar 2016 17:40:31 GMT

RK,

No the slave latency is set to 0. I will get a sniffer trace and see what's going on.

RE: nRF52 Slow To Discover Services In MCP

RK — Thu, 10 Mar 2016 01:39:53 GMT

Get a sniffer trace and you'll see directly what's going on, anything else is guesswork. How many characteristics and services do you have? Advertising interval not relevant unless the initial connection is taking a while to hit an advertising event it can reply with a connection event to. Do you have slave latency set and if so to what?