nRF51822 does not work with Windows 8.1

RE: nRF51822 does not work with Windows 8.1

Peter Myerscough-Jackopson — Thu, 26 Jan 2017 16:05:34 GMT

I found that I had not set up my Nordic stack to remember bonding information, and the windows side did not report this, it just behaves differently (and correctly) when connecting with a device that it has bonded with. I would check that you are saving bonding information, but I don't know where or what. I have currently disabled bonding on my device because bonding means that the device should remember the state of its CCCDs between connections which was something I was not doing, and so when reconnecting windows would not re-enable the notification CCCD bit because it believed my node should remember this. So my guess is that you need to ensure your Nordic stack is remembering it is already bonded with the Windows host, and that should do something in terms of being able to reuse authentication tokens between connections. Good luck.

RE: nRF51822 does not work with Windows 8.1

felkar123 — Thu, 26 Jan 2017 15:56:44 GMT

Hi, I know this is an old thread, but I run in to problem using Nordic trying to connect with Windows 10 laptop using Bluetooth Low Energy. When I'm paring and insert the PIN, communication works fine through my program. At this point, devices are bonded. If I disconnect them and then reconnect so that there is no need to insert the PIN my program gets service, characteristic and descriptor, but when I want to enable Descriptor notifications, function BluetoothGATTSetDescriptorValue returns an error saying "0x80650005: The attribute requires authentication before it can be read or written". I don't know If there is something on the Nordic side or at the Windows Stack side. Have you any ideas about this?

RE: nRF51822 does not work with Windows 8.1

Gilson — Wed, 20 Aug 2014 13:22:46 GMT

Hello Peter, I think my issue above was because when I was trying to set the descriptor to "subscribe to notification" via BluetoothGATTSetDescriptorValue my code was incorrect. I noticed that my device CCCD does not offer 'Notify' but 'Indicate' so the following settings would cause the issue:

	newValue.ClientCharacteristicConfiguration.IsSubscribeToNotification = TRUE;

but the following settings fixed the issue:

	newValue.ClientCharacteristicConfiguration.IsSubscribeToIndication = TRUE;

RE: nRF51822 does not work with Windows 8.1

Peter Myerscough-Jackopson — Wed, 20 Aug 2014 08:20:03 GMT

In your Nordic code, you must have set the HRM attribute to require authentication. This is in the security settings for read permissions ".read_perm" I think?. I have yet to enable security in my development, but if you disable this it should work. (I have been able to read unsecured/open attributes with the given code.)

RE: nRF51822 does not work with Windows 8.1

Gilson — Tue, 19 Aug 2014 17:19:29 GMT

Hi Peter,

Thank you for your help. It looks like CreateFile() works I found the code you pointed to me and implemented on my Win 8.1 I have one problem though. When I call hr = BluetoothGATTSetDescriptorValue( hBLEDevice, currGattDescriptor, &newValue, BLUETOOTH_GATT_FLAG_NONE);

I get error code 0x80650005 - The attribute requires authentication before it can be read or written

Do you have any idea what this means? In my case Win 8.1 is paired with my device so I'm not sure about this error. Looks like CreateFile is working because I only get this error when trying to set the descriptor value.

I appreciate your time and help. Cheers,

RE: nRF51822 does not work with Windows 8.1

Gilson — Tue, 19 Aug 2014 13:07:29 GMT

Hello Peter, I think I did not make myself clear. I'm very interested in the CreateFile() solution and if I can make it work I will NOT implement WinRT/Metro application. So if you may share that code would be awesome. thank you.

RE: nRF51822 does not work with Windows 8.1

Peter Myerscough-Jackopson — Tue, 19 Aug 2014 07:20:53 GMT

Sorry Gilson, the CreateFile() source is for the non WinRT/Metro style application, so if you are targeting that, then it is of no use.

RE: nRF51822 does not work with Windows 8.1

Gilson — Mon, 18 Aug 2014 17:46:50 GMT

Hi Peter,

Thank you for your comment. Would be possible for you to share the CreateFile() source if it is non-proprietary?

I'm having an issue finding documentation on how to use WinRT/Metro Style application model.

Please let me know. Thanks, Gil

RE: nRF51822 does not work with Windows 8.1

Peter Myerscough-Jackopson — Mon, 18 Aug 2014 10:40:09 GMT

I haven't used the BluetoothLEHealthProfiles, but I have managed to get code working in Win8.1 Desktop using the CreateFile() method, rather than the Modern/WinRT function calls.

Have a look at :

social.msdn.microsoft.com/.../how-to-retrive-gatt-attributes-using-bluetooth-le-apis-in-win32-console-application

and

msdn.microsoft.com/.../jj159880(v=vs.85).aspx

Using the above code and the corrected HRM example it should be possible to connect and retrieve data from the device.

As an aside, I haven't found a way to associate different services offered by the same device with each other in Windows. For example, heart rate and battery are separate services, but if you have two devices I don't know how to tell which battery service matches with which heart rate service. I am currently making a custom service with all my desired characteristics together. This is not how Bluetooth SIG designed it, but it is how I feel I must currently work with Windows.

Good luck

Edit

The two links that got me going were these:

social.msdn.microsoft.com/.../erroraccessdenied-error-when-trying-to-receive-data-from-bluetooth-low-energy-devices

social.msdn.microsoft.com/.../is-there-a-simple-example-desktop-programming-c-for-bluetooth-low-energy-devices

Particularly the second one.

Sadly my code is now very much refined to a non-generic device, a long way from the standard heart rate monitor. The above links however contain code that should get you going with a HRM and contain a lot of explanation.