Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

more than 31 bytes in advertsing and scanning #1027

Closed
swapkada opened this issue Apr 15, 2018 · 2 comments
Closed

more than 31 bytes in advertsing and scanning #1027

swapkada opened this issue Apr 15, 2018 · 2 comments

Comments

@swapkada
Copy link

hello, I am using btshell and trying to send more than 31 bytes but not able to send. it shows invalid mfg_data.. but if I put less than 31 bytes in mfg_data it accepts. is there any alternative way to send more than 31 bytes? is there anything which I am missing?
Thank you in advance

@SharanIoT
Copy link

@swapkada Advertising or Scan Response data length is max 31 Octets as per the Bluetooth Core Spec 4.2

@sjanc
Copy link
Contributor

sjanc commented May 16, 2018

Hi,

You can use Advertising Extensions which allows for up to 1650 bytes of data. Check BLE_EXT_ADV and BLE_EXT_ADV_MAX_SIZE syscfg values.

You need scanner that supports extended advertising to be able to see those, NimBLE supports it. Also some latest top Android Phones (eg Sony Xperia XZ2) support those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants