Hi,
What macro should be used in the bt_data ad struct in order to advertise a custom 128 bit UUID? I have tried the following: BT_UUID_128_ENCODE(BT_UUID_CUSTOM_SERVICE).
Thanks,
Adam
Hi,
What macro should be used in the bt_data ad struct in order to advertise a custom 128 bit UUID? I have tried the following: BT_UUID_128_ENCODE(BT_UUID_CUSTOM_SERVICE).
Thanks,
Adam
the ad seems to be of total bytes of 2 (flags) + 1 type for flags + 6 (HTS+DIS+BAS) + 1 (type for HTS/DIS/BAS) + 1 (length field) = 11 bytes.
So you have 27-11 = 16 bytes for device name + type and length, which equals 14 bytes of actual device name.
Thanks Susheel,
However, it seems that it is the introduction of the SD data that limits the length of the name. I don’t have an issue with this when I am not sending scan response data. Have you included the SD data in your calculation?
I was only calculating the actual payload and excluding the headers and other overheads.
adam_atmo said:I don’t have an issue with this when I am not sending scan response data.
i believe that you have a solution with this configuration when you are using scan response data aswell.
Sorry Susheel, I am still confused as to why I cannot see the full name...
In addition to the code that I have already attached, this is what I have in my prj.conf:
CONFIG_BT_DEVICE_NAME="abcdefghigklmnop"
This is what I see on the Android nRF Connect app:
Regards,
Adam
I will try to test this tomorrow, I think you have given me all the information needed to replicate your setup.