This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Custom Services and Advertising

Take into account an application on the nRF51822 and S110. I have defined different custom services, so UUID is 128bit long. When advertising:

  • Is it advisable to include all services? If yes, how can be managed taking into account the 31 bytes limit?
  • How is the 'uuids_more_available' field used?
  • Any other suggestion?
  • @Dani: Yes you have to take into account the limit of 31 bytes limit. The 128 bit UUID is already 16 bytes and you also have to use some bytes for flags, header, lengths etc. You have 2 seoarate packets advertising packet and scan response packet, each 31 bytes. uuids_more_available telling beside the list of UUID in the data field, there are more uuid in the attribute table. My suggestion is to add only most important 128 bit UUID into your advertising/scan response packet. The central can connect and do a service discovery when needed.

Related