This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

does the advertizing data Length can more than 31 byte?

I use nrf51822qfaa ,s110 V8.00,keil mdk V5 ide. does advertizing data Length can more than 31 byte? why? ble_advertising_init(&advdata, &respadvdata, &options, on_adv_evt, NULL); the respadvdata is resp the advertizing? I can add data in respadvdata?

I can both add BLE_UUID_TYPE_BLE and BLE_UUID_TYPE_VENDOR_BEGIN in the advertizing data?

#define BLE_UUID_TYPE_BLE 0x01 //< Bluetooth SIG UUID (16-bit).
#define BLE_UUID_TYPE_VENDOR_BEGIN 0x02 //< Vendor UUID types start at this index (128-bit).

Parents
  • FormerMember
    0 FormerMember

    The maximum length of the advertising data, 31 bytes, is defined by the Bluetooth Core Specification, see Bluetooth Core Specification v 4.2, vol 3, part C, chapter 11.

    Yes, you can add both Bluetooth SIG UUIDs (16 bit) and custom/vendor specific UUIDs (128-bit) to the same advertising data.

    The SDK example ble_app_uart shows how to use custom UUIDs, and among others how to add a custom UUID to the advertising data.

Reply
  • FormerMember
    0 FormerMember

    The maximum length of the advertising data, 31 bytes, is defined by the Bluetooth Core Specification, see Bluetooth Core Specification v 4.2, vol 3, part C, chapter 11.

    Yes, you can add both Bluetooth SIG UUIDs (16 bit) and custom/vendor specific UUIDs (128-bit) to the same advertising data.

    The SDK example ble_app_uart shows how to use custom UUIDs, and among others how to add a custom UUID to the advertising data.

Children
No Data
Related