Hi, I'm working on a BLE peripheral project using nRF52840 with nRF5SDK version 17.0.2 and softdevice S140 version 7.2.0
We are considering to increase our full device name from 10 bytes to 14 bytes. However, this cannot fit into our current adverting packet. Our current advertising packet looks like this:
- Flags => 1 + 1 + 1 = 3 bytes
- Attributes => 1 + 1 + 2 = 4 bytes
- Manufacturer specific data => 1 + 1 + 2 + 8 = 12 bytes
- Full device name (old) => 1 + 1 + 10 => 12 bytes
Therefore, we are considering to move full device name from advertising packet into scan response packet instead. So the new packet will look like this:
Advertising packet:
- Flags => 1 + 1 + 1 = 3 bytes
- Attributes => 1 + 1 + 2 = 4 bytes
- Manufacturer specific data => 1 + 1 + 2 + 8 = 12 bytes
Scan response packet:
- Full device name (new) => 1 + 1 + 14 => 16 bytes
However, our team has some concerns on this design and we would like your help to confirm these points if possible.
1.) Will there be any impact to our already existing BLE service and characteristics ID from this change alone? We have some concerns that if this changes affects the existing service and characteristics ID then it will be a big change on both firmware and our application side.
2.) If we implement this way, do we need to update any RAM configuration for softdevice?
3.) We will use our device with mostly PC and mobile phone (both iOS & Androids) so are there any known compatibility issues of using scan response packet for sending device full name? We have tested with a couple of iOS and android devices on our hands and they seems to work fine however we'd also like to know if there are such cases where compatibility issues might arises.
