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

non-connectable undirected advertising

Hello

I enable BT advertising with the option  BT_GAP_ADV_TYPE_ADV_NONCONN_IND

#define BT_LE_ADV_NCONN_IND BT_LE_ADV_PARAM(BT_GAP_ADV_TYPE_ADV_NONCONN_IND, \
                         BT_GAP_ADV_FAST_INT_MIN_2, \
                         BT_GAP_ADV_FAST_INT_MAX_2, \
                         NULL)
const struct bt_data scan_resp[] = {
        BT_DATA(BT_DATA_NAME_COMPLETE, beacon_name, strlen(beacon_name)),
    };
err = bt_le_adv_start(BT_LE_ADV_NCONN_IND,adv, ARRAY_SIZE(adv),scan_resp, ARRAY_SIZE(adv));
This works but the device appears as "connectable undirected" in the BT scanner tool
What options should I use for the device to appear as "non-connectable undirected" ?
Thank you
Parents
  • Hi

    What Bluetooth scanner tool are you using exactly, and how can we reproduce this with a DK for example? This might be a bug on our side, but I'd like to reproduce it before reporting internally.

    Best regards,

    Simon

  • I was using nrf Connect app 

    To reproduce use the code above or manually set the param.options to  BT_GAP_ADV_TYPE_ADV_NONCONN_IND
    This is an enumeration and resolves to 3 but the code in adv.c:  bt_le_adv_start_legacy() function  treats  params.options as a bitfield (line 970 and down)

Reply
  • I was using nrf Connect app 

    To reproduce use the code above or manually set the param.options to  BT_GAP_ADV_TYPE_ADV_NONCONN_IND
    This is an enumeration and resolves to 3 but the code in adv.c:  bt_le_adv_start_legacy() function  treats  params.options as a bitfield (line 970 and down)

Children
No Data
Related