nRF51822 Beacon Scan Request Package settings

Nordic company do have ibeacon board and SDK, few people have this SDK, I recently in a friend that also got one, but there is no time to see.

Now we use the Common SDK comes with the Beacon routine to do development, the development of the trust many people are like this: buy someone else has done a good job, get back to operate a few, with NRF MCP debugging, began to modify the SDK.

That's what I do, honestly, and then you get all sorts of problems.

1. How do I set up a scan request package on the beacon that comes with the SDK?

In fact, there is a place to compare the key, is to write M_adv_params.type ble_gap_adv_type_adv_ind, otherwise you how to set, MCP are not swept to the request package.

1  0 sizeof (M_adv_params)); 2 3     M_adv_params.type        = ble_gap_adv_type_adv_ind; 4     M_ADV_PARAMS.P_PEER_ADDR = NULL;                              5     M_ADV_PARAMS.FP           = ble_gap_adv_fp_any; 6     M_adv_params.interval   =non_connectable_adv_interval; 7     M_adv_params.timeout  =app_cfg_non_conn_adv_timeout;

2. Why can't ios MCP scan for advdata.p_manuf_specific_data?

Oh. This believes that many people will not develop the APP is a very headache, and for a long time all the hen shaking is what happened.

Ibeacon requirements Manuf_specific_data.company_identifier value is 0x004c, so shake to shake to get. This value is Apple's, Nordic Company's is 0x0059.

The MCP of IOS system will filter the 0X004C, so if you want to use MCP or lightblue other debugging tools to scan, can not get advdata.p_manuf_specific_data, how to do?

Will manuf_specific_data.company_identifier avoid 0x004c? But shaking a shake does not work, how to do?

Find a way, I can only tell you, 0x004c is not swept.

nRF51822 Beacon Scan Request Package settings