Discovering characteristics on a vs service with 16 vs characterisitcs, but only receiving 7 characteristic

RE: Discovering characteristics on a vs service with 16 vs characterisitcs, but only receiving 7 characteristic

Hung Bui — Mon, 03 Dec 2018 08:29:34 GMT

I'm sorry the link to the message sequence chart was missing. Please follow the link here.

If you make sure you always call the second characteristic discover command after you receive a success one, you will reach the point that Attribute not Found is returned.

RE: Discovering characteristics on a vs service with 16 vs characterisitcs, but only receiving 7 characteristic

Dresse — Sat, 01 Dec 2018 10:45:01 GMT

Ahh that makes sense. Will I always get Attribute Not Found, or is there a sitaution where it would go into the next service?

RE: Discovering characteristics on a vs service with 16 vs characterisitcs, but only receiving 7 characteristic

Hung Bui — Fri, 30 Nov 2018 13:52:56 GMT

Hi Dresse,

If you have a look at this message sequence chart, you can find that after the first call to sd_characteristic_discover() and you don't have "Attribute Not found" return, you would need to continue discovery the characteristics until you receive Attribute Not Found. You need to update the start handle after each call base on the handle of the last chars you discover in the last call.

RE: Discovering characteristics on a vs service with 16 vs characterisitcs, but only receiving 7 characteristic

Dresse — Fri, 30 Nov 2018 11:55:18 GMT

And if I test with my phone connected to the peripheral, I can see 14 custom characteristic uuids, on the same service as I have shown in my log.