The BLE service discovery but it isn't complete

[hvbon2010]

Hi everyone,

I'm using UART service and I have a problem when the central device connect to the peripheral.

The central device notify connected to the peripheral, but after start discovery service then it isn't complete and it isn't notify everything for me!

I aware that this problem occur when the central device notify connected but the peripheral don't notify.

Is there a way to solve this problem. Thank you!

[FormerMember]

Do you see the same problem if you use the central example ble_app_uart_c in the SDK?

If you connect to the peripheral using a phone, is the phone able to do the service discovery correctly?

If you use logging in the peripheral device, does it show any errors when the central stops the service discovery?

[hvbon2010]

Thank you for your reply,

My peripheral (running ble_app_uart_peripheral) is same that the central device(running ble_app_uart_c). When the central device is discovering, If I disconnect BLE then app_err_check fail.

I want the central service discovery have a timeout but the uart service discovery don't have!!!

[FormerMember]

Could you elaborate a little more on what you want to do?

What kind of timeout do you want for the service discovery?

To easily create a timer, you can use the app_timer library. For how to use it, see the documetation and for example ble_app_hrs (main.c -> timers_init() ).

 

[hvbon2010]

This timeout is the time allowed the central discover the service of the peripheral device. Currently, I'm using a timer to make timeout for discovery process. Again, I hope the central service will support this discovery timeout configure in the ble_nus_c_evt_type_t