nRF8001 and Windows 10 connectivity

RE: nRF8001 and Windows 10 connectivity

David Edwin — Thu, 30 Aug 2018 12:05:26 GMT

I finally had time to verify in on the new Windows 10 version 1803 (OS build 17134.167) , and the nRF8001 worked exactly as expected and the nRF8001 will work both in an open link (ACI Connect) or in a bonded link (ACI bond). I would suggest that the version 1803 be the recommended version.

RE: nRF8001 and Windows 10 connectivity

Charles GORAND — Tue, 28 Nov 2017 08:55:16 GMT

It's an integrated module : www.insightsip.com/.../isp091201

ISP091201D
1503
FCCID : 2AAQS - ISP091201
IC : 1130IA - ISP091201

RE: nRF8001 and Windows 10 connectivity

David Edwin — Tue, 28 Nov 2017 08:02:51 GMT

apologies for the delay, I have tested it on the Win 10 version you have and do see some unexpected behaviour. Can you also provide the IC markings on the nRF8001.

RE: nRF8001 and Windows 10 connectivity

Charles GORAND — Wed, 22 Nov 2017 13:47:24 GMT

Version 1703 : 15063.726

RE: nRF8001 and Windows 10 connectivity

David Edwin — Wed, 22 Nov 2017 13:42:26 GMT

Unexpected behavior on Win10. I expected a re-connect. Can you provide the Win 10 OS version/build number to see if I can re-produce it.

RE: nRF8001 and Windows 10 connectivity

Charles GORAND — Wed, 22 Nov 2017 12:58:52 GMT

Thank you David for your answer. I already use Windows 10 button to pair/bond the device. If I don't use it, It's not possible to initiate transaction with BLE device.

The Windows stack behavior is very strange as it handles connect and disconnection without desktop application consent.

RE: nRF8001 and Windows 10 connectivity

David Edwin — Wed, 22 Nov 2017 12:54:38 GMT

hmmm. I see the error code in the DISCONNECT event for AciStatus is 0x03 and BtLeStatus is 0x13, which is "0x13 Remote User Terminated Connection" according to the Bluetooth spec, which means Windows 10 initated this disconnect.

Action requested on your side: Can you use the "add bluetooth device" screen in Win 10 to add the nRF8001 device to Win 10. Take care to delete previous bonding attempts.

RE: nRF8001 and Windows 10 connectivity

Charles GORAND — Wed, 22 Nov 2017 12:49:44 GMT

And the embedded application works perfectly with an Android or a Linux remote peer.

RE: nRF8001 and Windows 10 connectivity

Charles GORAND — Wed, 22 Nov 2017 12:44:24 GMT

Bond is handled by application, "BOND error : 0x01" means ACI_BOND_STATUS_FAILED and next byte is BondStatusSource indicates 0x02 : Remote Peer error (not local), it's windows failure.

RE: nRF8001 and Windows 10 connectivity

Charles GORAND — Wed, 22 Nov 2017 12:41:27 GMT

It's already done. As soon as I get the DISCONNECT (0x86) I send a bond (0x10) :

HEXDUMP : IN  : 03 86 03 13 01 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 46 14 03 02 00 
HEXDUMP : OUT : 00 10 B4 00 A0 00 D8 00 00 00 00 00 00 F3 A3 B5 00 00 40 6E 00 0B 00 0C 00 02 02 00 08 04 00 0E 
LOG     : nrf8001_handleInData : OPCODE_DISCONNECT_EVT
LOG     : Disconnected
HEXDUMP : IN  : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 46 14 03 02 00 
HEXDUMP : OUT : 05 10 B4 00 A0 00 D8 00 00 00 00 00 00 F3 A3 B5 00 00 40 6E 00 0B 00 0C 00 02 02 00 08 04 00 0E

I mean, is it correct ? From documentation "Bond starts advertising with the intent of setting up a trusted relationship with a peer device" so that's correct behavior ?

The main issue is that nRF8001 works perfectly with Linux and Android and not with Windows.

RE: nRF8001 and Windows 10 connectivity

David Edwin — Wed, 22 Nov 2017 12:36:44 GMT

What is your action on the application after the DISCONNECT event arrives ? I would recommend that you re-enter the advertising state, the Win10 should re-connect as soon as it disconnects (this is the expected behaviour - i.e. reconnect after disconnect).

RE: nRF8001 and Windows 10 connectivity

Hung Bui — Wed, 22 Nov 2017 11:55:33 GMT

Hi Charles,

Windows 10 requires peripheral to be bonded with the device. Do you handle bonding in your application ?

The log showed "BOND error : 0x01" meaning bonding was failed.