BLE interface design advices

Hi,

We are defining a BLE interface for our product, choosing SIG and custom services, and while working on BLE for years now, I have still questions on how to design the BLE interface; like: 

  • How many characteristics per service should we respect ?
  • Should we choose to order data with characteristics and custom descriptors ? Or just more characteristics ?

Do you have maybe some guidelines regarding BLE interface ? 

Thanks,

Parents
  • Hi,

    There is no practical limitation on the number of characteristics, this is more about organizing the service(s) in a logical way. This is particularly important for the standard services defined by the SIG that are used in all kinds of different products, but for your custom services you can choose whichever makes most sense for you and your application. More characteristics will add overhead and memory usage though, so I would try to keep the number of characteristics within reasonable limits.

Reply
  • Hi,

    There is no practical limitation on the number of characteristics, this is more about organizing the service(s) in a logical way. This is particularly important for the standard services defined by the SIG that are used in all kinds of different products, but for your custom services you can choose whichever makes most sense for you and your application. More characteristics will add overhead and memory usage though, so I would try to keep the number of characteristics within reasonable limits.

Children
No Data
Related