non connectable advertise get error in SDK9.0.0

RE: non connectable advertise get error in SDK9.0.0

vinod kumar — Mon, 29 Oct 2018 10:07:00 GMT

Hi,

The Bluetooth Core spec 5.0 says this. Does it mean that it should not be discoverable when it is advertising in Non-discoverable mode. The question i am asking is about BLE not BR/EDR.

9.2.2 Non-Discoverable Mode
9.2.2.1 Description
A device configured in non-discoverable mode will not be discovered by any
device that is performing either the general discovery procedure or the limited
discovery procedure.

Thanks

vinod kumar

RE: non connectable advertise get error in SDK9.0.0

qoboty — Wed, 16 Dec 2015 10:18:58 GMT

Thank you very much!!

RE: non connectable advertise get error in SDK9.0.0

Anders Strand — Wed, 16 Dec 2015 10:13:22 GMT

Discoverability modes are described in Part C, Section 4.1 of the Bluetooth Core spec.

The limited discoverable mode should be used by devices that need to be
discoverable only for a limited period of time, during temporary conditions, or
for a specific event.

This is why you cannot advertise forever in limited mode. I think our documention should be improved here, as this is not clear.

BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED means that classic bluetooth (Basic rate, enhanced data rate) is not supported.

RE: non connectable advertise get error in SDK9.0.0

qoboty — Wed, 16 Dec 2015 03:59:00 GMT

By the way. I saw the description of GAP adv flag like below:

#define BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED   (0x04)
BR/EDR not supported.

the decription is short and blur for me.Is there a detail description ? Thanks !

RE: non connectable advertise get error in SDK9.0.0

qoboty — Wed, 16 Dec 2015 03:28:37 GMT

I use advdata.flags=BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE in the function advertising_init(...) After I change to advdata.flags=BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED and adv_params.type=BLE_GAP_ADV_TYPE_ADV_SCAN_IND in the function advertising_nonConnect_init(...). The device can advertise and I can get scan request. Thank you!

RE: non connectable advertise get error in SDK9.0.0

Anders Strand — Tue, 15 Dec 2015 13:24:50 GMT

Are you using BLE_GAP_ADV_FLAG_LE_LIMITED_DISC_MODE as a flag in the advdata? Try changing to BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED

RE: non connectable advertise get error in SDK9.0.0

Anders Strand — Tue, 15 Dec 2015 13:15:04 GMT

Weird. Can you post your code? Try to erase the entire chip with nRFgo studio. Flash the softdevice and application again and see if that helps

RE: non connectable advertise get error in SDK9.0.0

qoboty — Tue, 15 Dec 2015 12:39:48 GMT

static void advertising_nonConnect_init(void){
uint32_t err_code;
ble_gap_adv_params_t adv_params;
memset(&adv_params, 0, sizeof(ble_gap_adv_params_t));
adv_params.type        =BLE_GAP_ADV_TYPE_ADV_NONCONN_IND ;
adv_params.p_peer_addr = NULL;
adv_params.fp          = BLE_GAP_ADV_FP_ANY;
adv_params.interval    = 160 ;
adv_params.timeout     = 0;
adv_params.p_whitelist =NULL;
err_code = sd_ble_gap_adv_start(&adv_params);
APP_ERROR_CHECK(err_code);

I still get err_code=0x00000007, I use SoftDevice 8.0.0 SDK9.0.0 what should I do to fix it ?

RE: non connectable advertise get error in SDK9.0.0

Anders Strand — Tue, 15 Dec 2015 10:29:11 GMT

If you want nonconnectible, advertising, use BLE_GAP_ADV_TYPE_ADV_NONCONN_IND. Like this:

memset(&adv_params, 0, sizeof(m_adv_params));
adv_params.type        = BLE_GAP_ADV_TYPE_ADV_NONCONN_IND;
adv_params.p_peer_addr = NULL;                             
adv_params.fp          = BLE_GAP_ADV_FP_ANY;
adv_params.interval    = NON_CONNECTABLE_ADV_INTERVAL;
adv_params.timeout     = 0;

RE: non connectable advertise get error in SDK9.0.0

qoboty — Tue, 15 Dec 2015 09:41:37 GMT

Hi, I want to non-connectable advertise answered by here

I got err_code is 0x00000007 if set adv_params.timeout=0 whether adv_params.interval is zero or not. So how to non-connectable-advertise forever ? Thank you !

RE: non connectable advertise get error in SDK9.0.0

Anders Strand — Tue, 15 Dec 2015 09:24:32 GMT

You cannot have 0 as a interval with the type BLE_GAP_ADV_TYPE_ADV_SCAN_IND. Please see the documentation of ble_gap_adv_params_t

RE: non connectable advertise get error in SDK9.0.0

qoboty — Tue, 15 Dec 2015 08:58:18 GMT

if I set adv_params.interval = 0; adv_params.timeout = 0; err_code = sd_ble_gap_adv_start(&adv_params); I still got err_code is 0x00000007 I want to non-connectable advertise forever.what I need to do ?

RE: non connectable advertise get error in SDK9.0.0

Anders Strand — Tue, 15 Dec 2015 08:36:04 GMT

If the device resets, you should try to find out why. See this post.

RE: non connectable advertise get error in SDK9.0.0

qoboty — Tue, 15 Dec 2015 07:19:52 GMT

Function advertising_nonConnect_init are called when get connected event . After I set adv_params.timeout =0; when I connect to device.It will reset.If I set adv_params.timeout=64; it will go to sleep after 64 seconds.But I want to advertise forever.what I need to do ?

RE: non connectable advertise get error in SDK9.0.0

Anders Strand — Thu, 10 Dec 2015 14:46:31 GMT

Hey.

The maximum timeout is 180s. You can set it to 0 to advertise forever

RE: non connectable advertise get error in SDK9.0.0

qoboty — Thu, 10 Dec 2015 12:02:10 GMT

I did not change the softdevice. SoftDevice is 8.0.0

RE: non connectable advertise get error in SDK9.0.0

Anders Strand — Thu, 10 Dec 2015 11:38:28 GMT

Hi. Did you also change softdevice version?