• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 1919 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

RTOS/CC2640R2F: CC2640R2F Maximum advertising payload size

RTOS/CC2640R2F: CC2640R2F Maximum advertising packet length

stebin tharakan
Intellectual 890 points
Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2642R

Tool/software: TI-RTOS

Hi all,

I am working on CC2640R2F Advertisement part. Am sending my data along with my Advertisement packet. I can see that the advertisement packet can hold up-to  31 byte normally. Am adding extra 1 byte to my code so its now 32 byte.Now i got problem on receiver end. I put 60 devices for testing, in there some of my devices start to act weird like packet format goes wrong, data collision is happening, my doubt is is this because of changing advertisement packet length?? If i revert back my changes ie; advertisement packet length is 31  then its works fine.I couldn't get any conclusion. can anybody explain to me why this is happens.is there any link between data destruction and advertisement packet length? if so why only some device act as weird??

Thanks,

Stebin J Tharakan

  • 0
    TI__Guru* 78091 points
    Hi stebin,

    Which BLE version are you using - BLEv4.2 (e.g. the 1.50.00.58 SDK)? Unless you are using BLE5 with advertising extensions feature, BLE4.2 only supports a max AdvData payload of 31 bytes, as defined by the Bluetooth SIG specification version 4.2 [Vol 6, Part B] section 2.3.1.1 ADV_IND. If you need to send more data, it should be done in the form of a scan response. So you would switch your advertising type to being scannable and then put additional data in the scan response that can be provided when a device sends a scan request.

    Then new BLEv5 SIG spec includes an advertising extensions feature that can potentially support much larger amounts of advertising data. Our CC2642R device with SDK simplelink-cc26x2-sdk includes this feature.

    Regards,
    Katie
  • 0 in reply to Katie Pier
    Intellectual 890 points

    Hi Katie,

    Thanks for your reply.Am using BLE5 Stack.I know i cant send 32 byte normally. but my question was why  collision is happening? is it due to 32 byte i have sent? if so why its not happening all my devices only few of them are affected can you please clarify my this doubt

    Thanks,

    Stebin J Tharakan

  • 0 in reply to Katie Pier
    Intellectual 890 points
    Hi Katie,

    Thanks for your reply.Am using BLE5 Stack.I know i cant send 32 byte normally. but my question was why collision is happening? is it due to 32 byte i have sent? if so why its not happening all my devices only few of them are affected can you please clarify my this doubt

    Thanks,

    Stebin J Tharakan
  • 0 in reply to stebin tharakan
    TI__Mastermind 39950 points
    Stebin,

    Are you using advertising extended advertising features provided with BLE5? If you are trying to use a normal advertising type and trying to send 32 bytes, we cannot comment on what exactly will happen other than that it will not work because it's not defined by the BLE Spec and not characterized by TI because so. The only way you can send 32-bytes of advertisement data is by using advertising extensions in ble5.

    This SimpleLink Academy is for CC26x2 but largely applies to the BLE5 stack for CC2640R2
    dev.ti.com/.../ble_scan_adv_basic.html
  • 0 in reply to Evan W
    Intellectual 890 points
    Ok Thanks.Am also in confused by seeing the behavior of my device And i cant say what is the exact issue. Now am trying 31 bytes only using BLE5 no issues are found