Problem with direct advertising

RE: Problem with direct advertising

AndrzejB — Wed, 19 Oct 2016 13:24:36 GMT

I completely forgot there is no other info in Advertising Packet in direct mode. Now it's working in the way I want, Thanks

RE: Problem with direct advertising

Petter Myhre — Wed, 19 Oct 2016 10:45:30 GMT

Are you getting BLE_GAP_EVT_ADV_REPORT events when you do directed advertising? If you are, have you made changes to the criterias for which device you want to connect to? The directed advertising packets only include the peripherals address and the centrals address, please see Bluetooth Core Specification 4.2, Volume 6, Part B, Section 2.3.1.2. So if you look for a UUID or something like that the central will not connect. If you get a BLE_GAP_EVT_ADV_REPORT event you should check if the type is BLE_GAP_ADV_TYPE_ADV_DIRECT_IND, and then you should check if the peripherals address matches with peer_addr and call sd_ble_gap_connect().

RE: Problem with direct advertising

AndrzejB — Wed, 19 Oct 2016 08:11:20 GMT

My central is based on ble_app_hrs_c example, where I removed both of services and inserted my own service (based on ble_lbs_c).

RE: Problem with direct advertising

AndrzejB — Wed, 19 Oct 2016 07:46:04 GMT

I start direct advertising like in sequence chart available in Infocenter for Advertising Module and I get the BLE_ADV_EVT_DIRECTED event. After timeout I start direct advertising in low duty cycle and I get BLE_ADV_EVT_DIRECTED_SLOW event.