Nordic_HRM unknown services and characteristics from Windows app

[Sebastor]

I started Heart Rate Monitor app "ble_app_hrs_pca10040_s132" on nRF52 evaluation kit (nRF52832). Everything work well when I connect with nRF evaluation kit from Android devices.

When I tried to connect from Windows app for example"Bluetooth LE Lab", received information about unknown services and characteristics. On PC side I use BCM20702 BLE usb dongle. With the same dongle and windows app I can properly communicate with other BLE devices, services and characteristics are read without any errors. Tried on Windows7 and 10.

Please find below print screen from windows app.

[Bjørn Kvaale]

Hi,

Which SDK version are you using and which example are you currently running? It looks like you are using the NUS base UUID under the first unknown service:

#define NUS_BASE_UUID                  {{0x9E, 0xCA, 0xDC, 0x24, 0x0E, 0xE5, 0xA9, 0xE0, 0x93, 0xF3, 0xA3, 0xB5, 0x00, 0x00, 0x40, 0x6E}}

This is defined in ble_nus.c file in the ble_app_uart example located in SDKfolder\examples\ble_peripheral\ble_app_uart\

Which app are you using when you connect the nrf52DK to your android devices? nrf connect or nrf toolbox? When you say it works, do you mean that you can see the heart rate & battery services, as well as device information?

Kind Regards,

Bjørn Kvaale

[Sebastor]

Hi,

I use most recent SDK version 14. Yes it looks like NUS but i have no idea why.

I use nrf toolbox ->HRM app, and yes I can see heart rate&battery services, as well as device information. Please see attached screenshot.

Hardware is Rigado BDM-300 series evaluation board.

Regards

Sebastian

[Bjørn Kvaale]

I talked to another application engineer who said that it definitely won't work if you use windows 7 because there is a problem with the bluetooth drivers. If you use windows 10 with the fall creators update or later, it might work. The issue could be that you need to bond the devices via the bluetooth devices in windows 10 before you start the Bluetooth LE Lab app. Then, it might work.

My guess is that the sdk example has to be set up correctly, since everything works fine when you connect the DK to nrf connect or nrf toolbox for mobile. Generally speaking, we recommend using an nrf51 or nrf52840 dongle or a nrf51 or nrf52 DK on the PC side & using nrf connect to read characteristics & services. You could try talking to microsoft support or the Bluetooth LE Lab support group. They might have other suggestions. It might also be useful to take a look at the characteristics & services tutorials we have on Devzone.

Kind Regards,

Bjørn Kvaale

[Sebastor]

Hi

The problem was with BCM20702 BLE usb dongle. I replaced the dongle and now everything works well under windows. Can you please provide me with names of any small size, confirmed or "certified" usb dongles compatibile with nRF chips as well as with Windows systems ?

Regards

[Bjørn Kvaale]

The nrf51 & nrf52840 dongles are compatible with nRF chips & windows when used with nrf connect for windows. When you say small size, do you mean small as in a wireless mouse dongle?