Service discovered event from peripheral side

RE: Service discovered event from peripheral side

haakonsh — Tue, 04 Aug 2020 13:57:54 GMT

Only if it requires authentication, see GATTS Read Request with Authorization vs GATTS Read Request without Authorization.

RE: Service discovered event from peripheral side

Julien — Tue, 04 Aug 2020 13:50:43 GMT

Nothings except the BLE_GATT_DB_MAX_CHARS.

Before to read the issued service, i read an other service. There is a way to know from the server how many characteristics has been readed from the client?

RE: Service discovered event from peripheral side

haakonsh — Tue, 04 Aug 2020 13:36:07 GMT

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.

RE: Service discovered event from peripheral side

Julien — Tue, 04 Aug 2020 13:24:10 GMT

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.

RE: Service discovered event from peripheral side

haakonsh — Tue, 04 Aug 2020 11:27:30 GMT

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.

[quote user=""]The gold is to disconnect from the central if all the characteristic are not all discovered.[/quote]

Why?