• State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 87 subscribers
  • Views 2043 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 277115
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

【Chained Advertisement/Nordic 52832 or 52840】How to generate the chained advertisement with the nRF Connect SDK

xiaolongba

Hi Nordic experts,

Recently, I tested and found that I failed to start the advertisement with NCS 1.7.0  if the length of advertising data is greater than 251 Bytes, for instance, 500bytes, or 300 bytes.

the log system showed me the too big advertising data error information, I tried to debug and found that the root is caused by BT_HCI_LE_EXT_ADV_FRAG_MAX_LEN. However, I searched the answer here and it showed me that the NCS 1.7.0 (How to scan multiple tags that are sent periodic advertising in ncs v1.6.0? - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)) can support up to 1650bytes. so my question is :

1. How to generate the chained advertisement when the length of advertising data is greater than 251Bytes. is it possible at this moment?

Parents
  • 0

    Hi again

    Chained advertising will be used automatically if you advertise non-connectable with more than 245 bytes of data. The SoftDevice controller will split the data in two separate packets. Please note that the stack is currently limited to 255 bytes, so anything above this will return an error. For now you'll need to follow the workaround suggested by Hung for larger advertisements.

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hi @Simnor Bro,

    1. Thanks for your patient responses, as you said above, the max packet length is limit to 255Bytes at this moment. so users can only configure the length up to 255 bytes and then the controller can split these 255 bytes into two packets one is 245bytes, another is 10bytes? am I right?

    2. so users need to split their packet into 255bytes by themselves if the packet length is greater than 255bytes.

    3. as for 1650bytes, this feature will be supported in the future.

    the understanding above is correct?

    thanks again,

Reply
  • 0 in reply to Simonr

    Hi @Simnor Bro,

    1. Thanks for your patient responses, as you said above, the max packet length is limit to 255Bytes at this moment. so users can only configure the length up to 255 bytes and then the controller can split these 255 bytes into two packets one is 245bytes, another is 10bytes? am I right?

    2. so users need to split their packet into 255bytes by themselves if the packet length is greater than 255bytes.

    3. as for 1650bytes, this feature will be supported in the future.

    the understanding above is correct?

    thanks again,

Children
No Data
Related
Terms of service