This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Service discovered event from peripheral side

Hi,

I would like to know if there is an event from peripheral side to indicate that the discovery process is over.

The gold is to disconnect from the central if all the characteristic are not all discovered.

I'm working on NRF52832 with SDK 15.0

Best regards,

Julien F

Parents
  • You'll have to send a control signal from the application running the Client. F.x. an extra characteristic where the Client flips a bit when it is done with the Service Discovery procedure.  

    The gold is to disconnect from the central if all the characteristic are not all discovered.

     Why? 

  • In a new version of our central, i had characteristic, and it's over-range the constant BLE_GATT_DB_MAX_CHARS in my peripheral.

    So I increase this constants in my new version of my central.

    But in some case, an older central can see an new peripheral and i try to connect it. In this case, the two device stay connecty during a lot of time and to avoid this behaviour, i need to provoke a disconnection. 

  •  The SoftDevice does not send an event to the Server when a Service Discovery Procedure has completed. This means that we need to find another way to identify old Clients. 

    What else is changed between the old and new Clients? like connection parameters, supported PHYs, etc. 
    I'm thinking we can force a change in the link that is only acceptable to the new Clients in order to identify them.

Reply
  •  The SoftDevice does not send an event to the Server when a Service Discovery Procedure has completed. This means that we need to find another way to identify old Clients. 

    What else is changed between the old and new Clients? like connection parameters, supported PHYs, etc. 
    I'm thinking we can force a change in the link that is only acceptable to the new Clients in order to identify them.

Children
Related