HOW to use direct advertising to connect the central successfully?

[liu_zhixiang]

I use nrf52832 board by fast advertising to connect the central(surface 4 Tablet).Then the board go to sleep.when I push the button the board use direct advertising to connect the central again,but it dont connect. I use the peer manager to get the central address,when the BLE_ADV_EVT_PEER_ADDR_REQUEST event of direct advertising happens.

SDK 14.2  Softdevice 132 .Can you give me some suggestions about direct advertising to connect previous central successfully.

[liu_zhixiang]

when first time  push button ,the board can connect the central by direct advertising.In connection state, application handles things completely, then the board and central disconnect .The board go to sleep. Next time(push button no matter how many times) the board can use direct advertising ,but cannt connect.I'm confused about this problem,How to solve this problem?

[Kenneth]

Hi, can you make sure that you first delete all bonds on the central and peripheral? 

[liu_zhixiang]

OK. I will try it.

[liu_zhixiang]

I program SDK 12.3 to nrf52.Then use it test with surface3. The phenomenon is the same as above.They cant reconnect with fast adv with whitelist.

[liu_zhixiang]

I don't find sdk v11 in official website. Our last project use sdk v9 ,s130 and nrf 51 chip. It can work with surface 3 or 4 normally.

[Hung Bui]

Hi again, 

 

You can find SDK v11 here: https://developer.nordicsemi.com/nRF5_SDK/nRF5_SDK_v11.x.x/

Please test with ble_app_hids_keyboard. 

[liu_zhixiang]

This SDK v11 can reconnect again with surface 3.I bonded with Surface 3, then I turned OFF and ON Bluetooth on Surface 3. The keyboard example would then reconnect .They can reconnect may by fast adv with whitelist. So ,I think it is right to use direct adv to reconnect again. 

The serial doesn't read any data.  Maybe some configuration not set. This SDK code doesn't like next SDKs that have config.h . SDK v11 is a watershed. After v11,the structure of code is changed.

Can you change code that after SDK v11 to make it reconnect with surface tablet successfully. If not ,I will use SDK v11 to realize my project.

[Hung Bui]

Hi, 

We are investigating the issue. We suspect a new update on Windows 10 causing this issue. We received several reports from other customers as well. 

SDK v11 is pretty old SDK but if you are ok with the features and need to get your project finish quickly you can use SDK v11. But I would suggest to wait for us for 1-2 weeks for our investigation. We are on reduced staff due to summer vacation. So the investigation is quite slow now. We will be back to full staff in 2 weeks. 

[liu_zhixiang]

OK. Thanks for your reply. I will wait 2 weeks. Then I hope you can tell me the results, because I use SDK v14.2 just leave this question.

[Kenneth]

Hi,

Still working on this issue, have ruled out a few possible differences without any change in behavior. New tests tomorrow.

Kenneth

[Kenneth]

Hi,

We have got feedback from Microsoft that they are aware of the issue:

"We have a patch that should be in flight for this issue. Are you able to get Windows insiders builds to validate that we have addressed the issue in question?"

Best regards,
Kenneth

[liu_zhixiang]

Hi. The link you give is latest windows feature and Install Windows 10 Insider Preview.  Its content is about PC setting mainly. Does Microsoft prompt which specific aspect may affect reconnection?