DA14580
Basic Development Kit with added analog sensors & EEPROM
SDK 5.0.3
Hello again Dialog,
I'm continuing work on an application based on the ble_app_peripheral example and recently added SUOTA to my application. In so doing, I had to shorten my device ID to build .... which I confess was on the long side. I'm wondering why this happened? I don't see anything obvious in the spotar tasks that indicates bytes in the scan response packet are being used. Are they? I'd like to determine how much of the PDU is left for Manufacturer Specific data. As you're aware, the ble_app_peripheral example includes a 16 bit counter in the Manufacturer Specific data area that I'm looking at replacing with my own data.
Thanks, Max
Device:
Hi Max,
I dont get what you mean by Device ID, i suppose that you mean somekind of custom ID attached in the advertising data ?
In order for the SUOTA application to track a SUOTA enabled device you need to add a specific UUID on the advertising string (if the ADV_UUID_SPOTAR_SERVICE "\xF5\xFE") if this string is not present on the advertising data the phone won't track the device.
Thansk MT_dialog
MT,
Sorry, I meant USER_DEVICE_NAME. I did add the UUID as you posted above and in another response by you for adding SUOTA to the ble_app_peripheral example. The Android SUOTA app is working nicely with my application. Nice app BTW.
I was just wondering why my excessively long device name that worked previously had to be shortened to be accepted after merging in SUOTA. Maybe I'm not clear on the process, but I thought adding the UUID as above was in the ADV_IND packet and the device name and manufacturer specific data then appeared in the scan response packet. I was trying to determine if the SPOTAR service was using additional data bytes in the scan response.
Max
Hi Max44,
The data that you can insert in the advertising string is limited to 31 bytes by the BLE spec, by which 3 bytes are mandatory, so in the SDK when you place additional data in the advertising string that exceed the length of the advertising string the rest of the data will be placed in the scan response. So i suppose that if by adding an extra service like the SUOTA UUID in the advertising string, there is no room for the counter as well (the manufacturer specific data) so the scan response fills with the long name of your device and the manufacturer specific data and if they exceed the scan response length (31 bytes), well you will have to shorten the device's name.
Thanks MT_dialog
MT,
Aha! I wasn't aware that data would flow from the advertising string into the scan response. That explains it.
Thanks again, Max
I wanted to use SUOTA service on my DA14583 device and I am going to use SUOTA app to for software update.
To achieve that, is it compulsory to add 16-bit SUOTA service UUID in advertisement data?
Hi Ankit,
Yes, if you dont place the 16-bit UUID then the SUOTA android/ios application wont be able to see the device supports the SUOTA application thus it will not track your device.
Thanks MT_dialog