• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 226 views
  • Users 0 members are here
Options
Related

DA14531 Extended Advertisement to transfer more data than the Standard Advertisement data limit(32Bytes)

Harish

Hello Team,

SDK:  6.0.16.1144

Module: DA14531MOD

Is there support for Extended Advertisement as per Bluetooth 5.1? In my application I am using Unconnected broadcast to advertise the data and need to transfer more data hence I am looking for Extended Advertizement support as DA14531 claims it supports Bluetooth 5.1. 

I was thinking of implementing chunks of 200 bytes or more if Extended Advertisement supports and in the data packet header(custom) I can indicate the total bytes in the data and whether the complete data has been transferred in that chunk, just like file transfer chunks. However, the current 32 bytes with Standard Advertisement is very small in size for chunks as it has to transfer multiple times, hence looking for an Extended Advertisement feature.

I checked the support questions and I found this question: advertising-extensions. However, it says the DA14531 does not support it, is this true even now?

And also the suggestion from the above forum thread "Except from the advertising data, you can also use the scan response data" - If I use scan response data, what was the maximum data that it can transfer? Is this still achievable in unconnected mode? I feel Scan Requests from Central device can come only in connected mode. Please correct me if my understanding is not correct.

The referred example describes with connected mode, however, I need unconnected mode. Is there any reference example available to send a large amount of data(over 500 bytes, or at least multiple chunks ) over unconnected mode, or any approach that you can suggest?

Thanks & Regards

Harish.  

Parents
  • 0

    Hi Harish,

    Thank you for posting your question online.
    Let me try to answer your questions:

    Harish said:
    I checked the support questions and I found this question: advertising-extensions. However, it says the DA14531 does not support it, is this true even now?

    Unfortunately, the Extended Advertisement (ADV_EXT_IND) is not supported on the DA14531. 

    Harish said:
    And also the suggestion from the above forum thread "Except from the advertising data, you can also use the scan response data" - If I use scan response data, what was the maximum data that it can transfer? Is this still achievable in unconnected mode? I feel Scan Requests from Central device can come only in connected mode. Please correct me if my understanding is not correct.

    Yes, you are correct. In order to receive the Scan Response Data, the central must perform Active Scan and the peripheral device cannot be performing unconnected advertising. 
    The Scan Response data have the same size as the Advertising data, 31 bytes, but they do not need the 3 first bytes reserved for Flags. So if you are interested in undirected advertising you can save 28 bytes of data on the Advertising Data and another 31 bytes of information on the Scan Response data. 
    Keep in mind that in the Advertising/Scan Response data you will need to save the Device Name as well. 
    Please refer on our GitRepo examples for beacons' (unconnected advertising):
    1) BLE_SDK6_examples/connectivity/ibeacon at main · dialog-semiconductor/BLE_SDK6_examples · GitHub
    2) BLE_SDK6_examples/interfaces/wakeup_hibernation_ext_timer at main · dialog-semiconductor/BLE_SDK6_examples · GitHub
    3) BLE_SDK6_examples/connectivity/simple_beacon at main · dialog-semiconductor/BLE_SDK6_examples · GitHub
    4) BLE_SDK6_examples/connectivity/svc_data_beacon at main · dialog-semiconductor/BLE_SDK6_examples · GitHub
    Keep in mind that in unconnected advertising you are able to advertise 31 bytes of data but the Device Name can be saved on the Scan Response Data, no other data could be saved on the Scan Response Data.

    Harish said:
    The referred example describes with connected mode, however, I need unconnected mode. Is there any reference example available to send a large amount of data(over 500 bytes, or at least multiple chunks ) over unconnected mode, or any approach that you can suggest?

    Unfortunately, we do not have any example with unconnected advertising that can support over 500 bytes being transmitted in each advertising packet. 
    You will have to send 31 bytes of information on each advertising packet. 
    You could use undirected advertising in order to use the Scan Response Data as well and you could implement Security on your DA14531 so no central will be able to connect.  This way you will be able to send 28+31 (-Device Name bytes) for your advertising packets.

    Kind Regards,
    OV_Renesas

Reply
  • 0

    Hi Harish,

    Thank you for posting your question online.
    Let me try to answer your questions:

    Harish said:
    I checked the support questions and I found this question: advertising-extensions. However, it says the DA14531 does not support it, is this true even now?

    Unfortunately, the Extended Advertisement (ADV_EXT_IND) is not supported on the DA14531. 

    Harish said:
    And also the suggestion from the above forum thread "Except from the advertising data, you can also use the scan response data" - If I use scan response data, what was the maximum data that it can transfer? Is this still achievable in unconnected mode? I feel Scan Requests from Central device can come only in connected mode. Please correct me if my understanding is not correct.

    Yes, you are correct. In order to receive the Scan Response Data, the central must perform Active Scan and the peripheral device cannot be performing unconnected advertising. 
    The Scan Response data have the same size as the Advertising data, 31 bytes, but they do not need the 3 first bytes reserved for Flags. So if you are interested in undirected advertising you can save 28 bytes of data on the Advertising Data and another 31 bytes of information on the Scan Response data. 
    Keep in mind that in the Advertising/Scan Response data you will need to save the Device Name as well. 
    Please refer on our GitRepo examples for beacons' (unconnected advertising):
    1) BLE_SDK6_examples/connectivity/ibeacon at main · dialog-semiconductor/BLE_SDK6_examples · GitHub
    2) BLE_SDK6_examples/interfaces/wakeup_hibernation_ext_timer at main · dialog-semiconductor/BLE_SDK6_examples · GitHub
    3) BLE_SDK6_examples/connectivity/simple_beacon at main · dialog-semiconductor/BLE_SDK6_examples · GitHub
    4) BLE_SDK6_examples/connectivity/svc_data_beacon at main · dialog-semiconductor/BLE_SDK6_examples · GitHub
    Keep in mind that in unconnected advertising you are able to advertise 31 bytes of data but the Device Name can be saved on the Scan Response Data, no other data could be saved on the Scan Response Data.

    Harish said:
    The referred example describes with connected mode, however, I need unconnected mode. Is there any reference example available to send a large amount of data(over 500 bytes, or at least multiple chunks ) over unconnected mode, or any approach that you can suggest?

    Unfortunately, we do not have any example with unconnected advertising that can support over 500 bytes being transmitted in each advertising packet. 
    You will have to send 31 bytes of information on each advertising packet. 
    You could use undirected advertising in order to use the Scan Response Data as well and you could implement Security on your DA14531 so no central will be able to connect.  This way you will be able to send 28+31 (-Device Name bytes) for your advertising packets.

    Kind Regards,
    OV_Renesas

Children