About extended advertising

[Junichi]

I am considering software that uses nRF52840, where one side will send advertisements and the other side will scan
and obtain data from advertisements.

I am considering a method of sending advertisements by adding the data I want to communicate to MANUFACTURER SPECIFIC DATA and obtaining values ​​from the advertisement data obtained by the scan side.

I would like to use extended advertising because I want to send about 26 bytes of data and 6 bytes of device name.

The SDK I am using is 16.0.0 for the sender and 17.0.0 for the receiver.

Please tell me how to set up sending and receiving with extended advertising.

I am also considering connecting both sides with an NUS connection to exchange data.

Please let me know if there is any impact on the NUS connection when using extended advertising.

[Simonr]

Hi

I don't think extended advertising would be necessary here. You can also use scan response data to transmit an additional 31 bytes after the initial advertisement where you can add these 26 bytes of data if you want, but that would be entirely up to you. Please note that nRF5 SDK v17.0.0 should not be used, and SDK v17.0.2 was released as a patch for this SDK version to fix some crucial issues with the 17.0.0 release.

Extended advertising should not affect a NUS connection at all. You can use the function ble_adv_extended_enabled to enable extended advertising and refer to the Bluetooth advertising module for general guidance.

Best regards,

Simon