I’ve been working on BLE and the guides and examples provided by particle. All is working well but I found a really weird characteristic. I am trying advertise as a UART capable peripheral and loading up the UART example works perfectly well (https://docs.particle.io/tutorials/device-os/bluetooth-le/#uart-peripheral).
However, this UART Capable “tag” seems to disappear after I append a local name which is >=9 characters long. Now I’ve read https://docs.particle.io/reference/device-os/firmware/argon/#appendlocalname- and it mentions:
" The name takes up the length of the name plus two bytes (type and length). The total advertising data is limited to 31 bytes (
BLE_MAX_ADV_DATA_LEN ), and if you include service identifiers there isn’t much left space for the name."
Is this maybe a limitation due to the advertising data limit?
This doesn’t seem to affect functionality but I would like the UART tag since I am trying to filter and only view surrounding devices with this tag.
This can be replicated by just adding a local name to the UART peripheral project. The device I am using is a Boron 3G device on OS 1.4.4. Example:
BleAdvertisingData data; data.appendLocalName("Doug_Devi"); // This name stops the UART characteristics from showing up data.appendServiceUUID(serviceUuid); BLE.advertise(&data);
BleAdvertisingData data; data.appendLocalName("Doug_Dev"); // UART Characteristics still show up data.appendServiceUUID(serviceUuid); BLE.advertise(&data);
See screen shots of the Bluefruit app I am using to check this:
Articles/Posts I’ve read: