nRF Connect issue under Windows

RE: nRF Connect issue under Windows

run_ar — Fri, 31 Mar 2017 10:33:29 GMT

Thank you for the update, glad you figured it out.

RE: nRF Connect issue under Windows

oneguy — Fri, 31 Mar 2017 09:49:41 GMT

Sorry I clicked on the wrong button... This here is the answer:

We added the following line to static void on_ble_evt(ble_evt_t * p_ble_evt)

rc = sd_ble_gap_sec_params_reply (mConnHandle, BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP, NULL, NULL);

Now everything works fine.

Thank you for your help.

RE: nRF Connect issue under Windows

run_ar — Fri, 31 Mar 2017 09:16:22 GMT

Could you capture a sniffer trace so we can see what is happening?
There might be a discovery timeout. Could you wait for at least 30 seconds before you do the write to see if you get a timeout?

RE: nRF Connect issue under Windows

oneguy — Thu, 16 Mar 2017 09:45:26 GMT

Hi run_ar,

We have tested the SDK example "ble_app_hids_keyboard" -> nRF Connect (PC version) fails to discover services Note again, that connecting nRF Connect (PC version) succeeds when connecting to a BLE113 module

By the way, we're using Windows 7 Enterprise.

RE: nRF Connect issue under Windows

run_ar — Wed, 15 Mar 2017 10:38:23 GMT

nRF connect for Android and iOS cannot really be compared to the PC version as they are quite different. Are you able to recreate this with any of our SDK examples? or can you share your firmware so I can try to recreate the issue here?

RE: nRF Connect issue under Windows

oneguy — Mon, 13 Mar 2017 13:50:25 GMT

Hi run_ar,

any ideas yet?

RE: nRF Connect issue under Windows

oneguy — Mon, 06 Mar 2017 12:13:34 GMT

We're connecting to a nRF52/S132 device. Regarding the nRF52/S132 device: it is based on a SDK example but has come quite a long way since. Regarding HW: our own board, but based on Nordic's 10040 kit.

We're puzzled because nRF Connect (Android and iOS) does not seem to suffer from the same issue.

RE: nRF Connect issue under Windows

run_ar — Fri, 03 Mar 2017 10:28:19 GMT

I'm sorry, looking at the log it looks like that only take a few seconds, and you try to write almost 20 seconds later. What kind of device are you trying to connect to? is this an SDK example so I can try to recreate the behavior here? Which version of nRF connect are you using? and what board are you using for connecting?

RE: nRF Connect issue under Windows

oneguy — Thu, 02 Mar 2017 14:38:30 GMT

Thanks for your reply. How do we know when device discovery is done?

RE: nRF Connect issue under Windows

run_ar — Thu, 02 Mar 2017 14:31:54 GMT

Looks like you are trying to do a write while the service dsicovery is still ongoing. Unfortunately we do not currently have a protection against that in nRF connect. Could you try waiting with the write until the service discovery procedure is finished and see if that helps? Thanks.

RE: nRF Connect issue under Windows

oneguy — Wed, 01 Mar 2017 14:33:18 GMT

Ok, I have uploaded the file

Thanks

RE: nRF Connect issue under Windows

run_ar — Wed, 01 Mar 2017 14:08:48 GMT

You can edit your question and attach the log there.

RE: nRF Connect issue under Windows

oneguy — Wed, 01 Mar 2017 12:36:16 GMT

Hi run_ar,

I'm happy to send you the error log. How do I do this as I cannot attach a file to this comment.

RE: nRF Connect issue under Windows

run_ar — Wed, 01 Mar 2017 11:42:30 GMT

Can you please elaborate on what timeout error you are getting? Could you provide an error code and error log?