This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Connecting nRF51 with Windows 10 Bluetooth

We have a custom hardware device that uses the nRF51 and the S130 softdevices. We are able to connect our device to our app on iOS and Android and through a web-bluetooth application on Chrome OS and Mac.

We are not able to connect the nRF51 to Windows 10 through the Bluetooth System Settings. We can see the device advertising from the "Add a device" Windows tool. When we click to connect to our device we get the generic error message "Try connecting to your device again."

Is there a connection interval or other setting specific to Windows 10 that is different than all other platforms? We do not have any problems with iOS, Android, Chrome, and Mac on establishing connection, just Windows.

As a test, I used the nRF51 DK PCA10028 and the example BLE Power Profiling app to try to establish a Windows connection. I can connect to the nRF51 DK on my Mac and Android phone and discover services. When I try to connect on Windows 10 through the Bluetooth System Settings, I get the same "Try connecting to your device again" error message.

I then tried the "Experimental: BLE Blinky Application" and "Blood Pressure Application" example apps on the nRF51 DK and I was able to connect on Windows 10. What's the underlying difference?

Thanks for your help.

Parents
  • Bjorn- thanks for the help. I had seen those other link threads but I was not able to get any help from them. I understand a dongle is a nice to have, but we are developing a consumer product and we cannot include a dongle.

    Did you try the "Power Profiling" example and were you able to establish a BLE connection? What is different between the "Power Profiling" program and the other example programs that would prevent connection? Have you seen instances where a product/program will work with all other OSs (Android, iOS, Chrome, Mac) but cannot establish connection with Win 10? Thanks.

Reply
  • Bjorn- thanks for the help. I had seen those other link threads but I was not able to get any help from them. I understand a dongle is a nice to have, but we are developing a consumer product and we cannot include a dongle.

    Did you try the "Power Profiling" example and were you able to establish a BLE connection? What is different between the "Power Profiling" program and the other example programs that would prevent connection? Have you seen instances where a product/program will work with all other OSs (Android, iOS, Chrome, Mac) but cannot establish connection with Win 10? Thanks.

Children
No Data
Related