Directed Advertising not seen by the addressed device

Hi Armand

My apologies, I had back to back meetings today and didn't get time. I will do my best to test this tomorrow and get back to you. 

Best regards
Torbjørn

Ok Thanks Torbjørn

Hi Armand

I had a chat with Hung, a colleague of mine, who mentioned that he handled a similar case some time ago (with you possibly). 

He sent me some code that I could use to test this. 

I made some minor changes to his code, and was able to get extended directed advertising working. 

Please note that you have to find the local address of the scanner by looking at the log output, and update the advertiser code to use this address. 

Could you give this code a try and see if it works OK?

Best regards
Torbjørn

Hi 

Thanks for your reply. I have been going through the code and it is my understanding that it will detect any extended advertising but it does not discriminate for directed advertising. Please check the flags it is reading on the central_bas2 sample code:

static void scan_filter_no_match(struct bt_scan_device_info *device_info,
				 bool connectable)
{
	int err;
	uint8_t i;
	struct bt_conn *conn;
	char addr[BT_ADDR_LE_STR_LEN];
		bt_addr_le_to_str(device_info->recv_info->addr, addr,
				  sizeof(addr));
	if ((addr[0]=='F')&&(addr[1]=='6'))
	{
		printk("address %s\n",addr);	
		for (i=0;i<device_info->adv_data->len;i++)
		{
			printk("%x",device_info->adv_data->data[i]);
		}		  
		printk("\n");
	}
	if ((device_info->recv_info->adv_type == BT_GAP_ADV_TYPE_EXT_ADV) && 
		(device_info->recv_info->adv_props & BT_GAP_ADV_PROP_EXT_ADV)) {
		bt_addr_le_to_str(device_info->recv_info->addr, addr,
				  sizeof(addr));
		printk("Extended directed advertising received from %s\n", addr);
	}
}

The flags are specific to detect  devices that are performing extended advertising but not exclusively directed advertising:

if ((device_info->recv_info->adv_type == BT_GAP_ADV_TYPE_EXT_ADV) && 
		(device_info->recv_info->adv_props & BT_GAP_ADV_PROP_EXT_ADV))

Please check this out.

Hi Armand

This was something I had to add myself to make the directed advertising packets detected properly in the example. 

When doing extended advertising then the adv_type field will no longer indicate whether or not you are receiving a directed or undirected advertising packet, since adv_type is BT_GAP_ADV_TYPE_EXT_ADV for all extended advertising packets. 

Instead I had to check the adv_props field in order to figure out whether or not I was receiving an extended directed advertising packet from my advertiser, rather than some other advertise packet from other advertisers in the area. 

If you want to also be able to read normal directed advertising packets (not using extended advertising) then you need to add a separate check for this. 

Does that answer your question?

Best regards
Torbjørn