https://devzone.nordicsemi.com/f/nordic-q-a/53618/52832-center-to-discover-2-service-uuiduse sdk:11.0 Reference routine：ble_nus_c now I use 52832 to connect a device,the service UUID like the photo. when I only discover one service UUID,like this code the center can connect the device,and send some command to control the deviceen-USTelligent Community 13Thu, 24 Oct 2019 11:05:02 GMThttps://devzone.nordicsemi.com/thread/216578?ContentTypeID=1Thu, 24 Oct 2019 11:05:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f001b46c-81ca-4eca-82f1-3034d7afe6deKenneth<p>Hi,</p> <p>Please read this tutorial on how to catch errors and assert, to find the actual file name, line number and error code that caused it.&nbsp;<a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/an-introduction-to-error-handling-in-nrf5-projects">https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/an-introduction-to-error-handling-in-nrf5-projects</a>&nbsp;</p> <p>By default the error handler is setup to reset the chip to safely recover, and this make sense for an end-product, however during development it is more useful to define DEBUG to catch such errors so you fix them. In your case the problem may be that you have not initialized the softdevice to support more than 1 vendor specific UUID, e.g.:</p> <p><pre class="ui-code" data-mode="c_cpp">p_ble_enable_params-&gt;common_enable_params.vs_uuid_count = ??</pre></p> <p>Also, is there any particular reason why you are working on an old SDK such as v11? The latest is nRF5 SDK v16. You should be aware that the system_nrf52.c file in SDK v11 is missing workaround for errata_108(), so this file should at least be updated from SDK v16 if you intend to continue work with SDK v11.</p> <p>Kenneth</p><div style="clear:both;"></div>