This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF52 Slow To Discover Services In MCP

I am having trouble with the service discovery of my application. When I click Discover Services it takes several seconds to discover all of the services. For example between the GetDeviceInfo() shown in the MCP log and the Service Discovery Complete it takes 48 seconds total.

I have fast and slow advertising set up. Fast advertising is 25ms interval and slow is 500ms. The min connection interval is 400ms, max is 650 and the time out is 4000ms.

Any idea what would cause this?

Thanks

  • 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?

  • RK,

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

  • 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.

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

  • 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.

Related