Peripheral disconnects when discovering services from a Windows central

RE: Peripheral disconnects when discovering services from a Windows central

dingari — Tue, 28 Feb 2017 09:26:59 GMT

Erm, I may have figured this one out. And it's kind of embarrassing.

My application was advertising random temporary 16-bit UUID services over the BLE base we were using to get a proof-of-concept product. Removing these UUIDs from the advertisement packet I can successfully pair the device with my Linux central now (which I couldn't do before), I've yet to try it on Windows. The centrals were maybe trying to resolve these UUIDs, hit a wall and disconnected.

And it seems like my Android phone has trouble pairing with any BLE device.

I'll update this as an answer as soon as I can verify it with Windows.

RE: Peripheral disconnects when discovering services from a Windows central

Petter Myhre — Thu, 02 Feb 2017 07:23:11 GMT

ble_app_hrm should support pairing out of the box. I'm not sure if it can be used, nRF Sniffer is meant to be used with either nRF51822 Evaluation Kit (PCA10001) or nRF51822 Dongle (PCA10000).

RE: Peripheral disconnects when discovering services from a Windows central

dingari — Wed, 01 Feb 2017 21:15:06 GMT

I'm using SDK v11 and S130 v2.0.1.

It's a custom project that we've built on top of the HRM peripheral example.

As for sniffing, I've not gone so far since I haven't got any devices for that handy. Could I use a BLE Nano module from RedBearLabs as a sniffer? It's an nRF51 based module and it has UART->USB (I think?).

RE: Peripheral disconnects when discovering services from a Windows central

Petter Myhre — Wed, 01 Feb 2017 17:41:06 GMT

What SDK and SoftDevice version are you using? What example? Have you sniffed what is happening on the air? A sniffer log will probably explain alot.