Pairing unsuccessful with phone

RE: Pairing unsuccessful with phone

vn2000 — Tue, 05 Nov 2019 08:41:45 GMT

Thank you for your assistance. The pairing issue was resolved!

RE: Pairing unsuccessful with phone

Hakon — Mon, 04 Nov 2019 14:58:57 GMT

[quote user="vn2000"]Should I open a new thread for the advertising time?[/quote]

Yes, please do. It will give you more dedicated support.

RE: Pairing unsuccessful with phone

vn2000 — Fri, 01 Nov 2019 17:05:29 GMT

The pairing issue is working now according to your suggestion.

However if I changed both APP_ADV_FAST_DURATION and APP_ADV_SLOW_DURATION to be 0 in order to have continuous advertising, the device no longer advertised.

So the pairing problem was resolved. Now this is a new issue regarding the advertising time.

Should I open a new thread for the advertising time?

RE: Pairing unsuccessful with phone

Hakon — Fri, 01 Nov 2019 15:53:16 GMT

What do you mean by "it no longer worked". Also, you need to delete the bonds on the central as well, when you erase bonds on the peripheral.

RE: Pairing unsuccessful with phone

vn2000 — Fri, 01 Nov 2019 02:08:49 GMT

I only changed the the advertising time APP_ADV_FAST_DURATION and APP_ADV_SLOW_DURATION to be longer. So I changed it back to 3000 and 18000, now it works.

The question I have now is that how do I make it continuously advertises. We have a product and we don't want it to advertise only a few minutes then stop.

I tried to change both APP_ADV_FAST_DURATION and APP_ADV_SLOW_DURATION to be 0 and it no longer worked.

RE: Pairing unsuccessful with phone

Hakon — Thu, 31 Oct 2019 12:22:02 GMT

What changes have you done to the original sample code?

RE: Pairing unsuccessful with phone

vn2000 — Thu, 31 Oct 2019 11:15:27 GMT

Yes I did erase and load the softdevice s132 and it has no effect.

RE: Pairing unsuccessful with phone

Hakon — Thu, 31 Oct 2019 09:39:14 GMT

Have you tried erasing the chip as I mentioned in a previous reply?

RE: Pairing unsuccessful with phone

vn2000 — Thu, 31 Oct 2019 05:14:39 GMT

I do have these statements in PM_EVT_CONN_SEC_CONFIG_REQ, even though it looks like:

conn_sec_config.allow_repairing = true;
pm_conn_sec_config_reply(p_evt->conn_handle, &conn_sec_config);

My PCB doesn't have button 2. So I used advertising_start(1) at reset. But pairing is still unsuccessful.

Since I'm displaying serial debug messages, I was following up some variables and I noticed that when the pairing is successful, the value of m_whitelist_peer_cnt to be 2 or 3. When the pairing is unsuccessful, m_whitelist_peer_cnt is always 1. This value is set by the function pm_peer_id_list, called by whitelist_set in advertising start.

I'm trying to trace further, but if you can give a suggestion that will help.

RE: Pairing unsuccessful with phone

Hakon — Wed, 30 Oct 2019 12:35:37 GMT

I think I know how to deal with the "Pairing Unsuccessful" problem now. What worked for me was adding

        case PM_EVT_CONN_SEC_CONFIG_REQ:
        {
            pm_conn_sec_config_t conn_sec_config = {.allow_repairing = true};
            pm_conn_sec_config_reply(p_evt->conn_handle, &conn_sec_config);
        } break;

to pm_evt_handler().

Also, every time you reset the device, press button 2, or if you don't want to press the button every time you reset you can change to advertising_start(1) as described below.

RE: Pairing unsuccessful with phone

Hakon — Wed, 30 Oct 2019 10:22:46 GMT

Ok, try erasing the chip then reprogram (and remember to flash the soft device). Do this everytime you try reconnecting.

RE: Pairing unsuccessful with phone

vn2000 — Tue, 29 Oct 2019 20:40:46 GMT

I changed to advertising_start(1) but still have the same issue: Pairing Unsuccessful.

When I used this new compiled firmware, the original nRF52DK can't pair either.

RE: Pairing unsuccessful with phone

Hakon — Tue, 29 Oct 2019 12:16:03 GMT

Change the line

advertising_start(erase_bonds);

in main.c to

advertising_start(1);

and see if you are able to pair every time.

RE: Pairing unsuccessful with phone

vn2000 — Mon, 28 Oct 2019 17:26:41 GMT

Interestingly, the ble_app_hids_keyboard can be paired with the iPhone only once. After that the pairing was mostly unsuccessful, just like the ble_app_hids_mouse.

The ble_app_hids_keyboard is not even seen by Android phone when I go to Settings->Bluetooth. At least with ble_app_hids_mouse I can see it in both Android and iPhone, even though pairing was unsuccessful.

What I can see here is that both ble_app_hids_mouse and ble_app_hids_keyboard were able to pair only once the first time the firmware was loaded into flash. Then after that the pairing was always unsuccessful. It looks like some variables were initialized correctly at first. Then after that they affected the subsequent pairing process that prevented it from being paired again.

RE: Pairing unsuccessful with phone

Hakon — Mon, 28 Oct 2019 10:04:27 GMT

Does it also happen with the ble_app_hids_keyboard example?

RE: Pairing unsuccessful with phone

vn2000 — Fri, 25 Oct 2019 15:46:38 GMT

Yes. First I want to see if the ble_app_hids_mouse example (unchanged) in sdk works on my PCB. I tried both V11 and V15. I also tried with a commercial unit, the Red Bear Nano BLE, and have the same problem. They don't work neither with V11 nor V15 ble_app_hids_mouse. But they still work with other non-hid app that don't require pairing.

However, The nRF52DK eval board works with V15 but not V11 (ble_app_hids_mouse).

We badly need Nordic nRF52 to work as a BLE HID device. That will be our main product.

RE: Pairing unsuccessful with phone

Hakon — Fri, 25 Oct 2019 13:22:08 GMT

Hello,

are you trying to make the ble_app_hids_mouse example in sdk 11 work on your custom board?