We are trying to replace an existing solution that uses a custom Service with 4 Characteristics. Unfortunately none of those share the same base UUID.
Basically the Service should look like this:
8dc1e5f5-b9b9-4398-8a4a-4357a1b3ba32 Custom Service
35434ec7-d846-43a4-b897-92e0ad172f09 Characteristic 1
4708882b-7d63-4be7-9682-7b9c3ca7aeb8 Characteristic 2
c3ef83eb-5e13-4c57-b7a6-9310be5ca1ba Characteristic 3
46ab9fb3-915d-4bd2-b038-c7ffe90ebb0b Characteristic 4
From this devzone article I understand that every single 128bit UUID costs 1.5kb of memory.
-> 5 custom UUIDS -> 5x sd_ble_uuid_vs_add() -> 7.5kb of memory.
That makes implementing the Service with an nRF52 nearly impossible and I can not believe that is correct.
We are currently using nRF5 SDK 11.0.0 with SoftDevice S132 2.0.1 on a nRF52.