Win 10 BLE stacks, acting as a central, problems accepting BLE connection parameter changes.

RE: Win 10 BLE stacks, acting as a central, problems accepting BLE connection parameter changes.

David Edwin — Mon, 20 Nov 2017 09:00:40 GMT

Typically we need to check the timing at which the updates are being pushed out and relax it or modify it so it works with the different BTLE stacks on the PC. More information is best shared if there is a sniffer trace to act on, it is easier to share information on specific chipsets in the one on one support portal. www.nordicsemi.com/.../Contact-Support-Team

RE: Win 10 BLE stacks, acting as a central, problems accepting BLE connection parameter changes.

ianm — Sun, 19 Nov 2017 02:14:03 GMT

hi David, I did download the NRFReadyDescktop2 source code and compared it to ours our code calls Nordic ble_conn_Params_change_conn_parms(), which in turn calls Nordic sd_ble_gap_conn_params_update() the NRFReadyDesckTop2 source code calls Nordic sd_ble_gap_conn_params_update()... so from a code compare point of view, using the same Nordic calls to set connection parameters. this confirms our theory in that the problem is with the BLE stack we have in our Dell laptop. According to dell, the BLE chip is an "Intel WiFi Link 8265 2x2 802.11ac + BT 4.2", with the BLE stack from intel. do have any knowledge of BLE stacks associated with this chipset?

RE: Win 10 BLE stacks, acting as a central, problems accepting BLE connection parameter changes.

David Edwin — Fri, 17 Nov 2017 11:01:53 GMT

could not get the frontline sodera viewer to view the .scap file, can you provide a .cfa from fromtline or a .pcap saved from wireshark.

RE: Win 10 BLE stacks, acting as a central, problems accepting BLE connection parameter changes.

ianm — Fri, 17 Nov 2017 01:33:17 GMT

hi David, I updated my post with attachments.

RE: Win 10 BLE stacks, acting as a central, problems accepting BLE connection parameter changes.

David Edwin — Tue, 14 Nov 2017 11:14:15 GMT

I would definitely want to you to take a look at the Desktop 2 code for the connection parameters update.

RE: Win 10 BLE stacks, acting as a central, problems accepting BLE connection parameter changes.

David Edwin — Tue, 14 Nov 2017 11:10:06 GMT

You can attach files to your question or answer. The should be "clip" like icon that can be used to add attachments.

RE: Win 10 BLE stacks, acting as a central, problems accepting BLE connection parameter changes.

ianm — Tue, 14 Nov 2017 01:42:49 GMT

Hi david,

I have re-done my 'set connection parameters' via the PPCP (Preferred Peripheral Connection Parameter) Characteristics using the same software running on a Nordic nrf52 development board running as a BLE peripheral, but with 2 different BLE centrals, an Android phone, and an Win 10 Dell Laptop.

short answer:

o with the Android phone as a central, no problem setting connection parameter intervals see L2CAP 'Connection Parameter Update Request', and 'Connection Parameter Update Response (accepted)' pair, along with LE LL 'LL_CPNNECTION_UPDATE_IND' o with Win 10 device as central, initial connection is at 20 ms (using range of 7.5 ms to 500 ms), when attempt to set to 20 ms, 640 ms, yes I see the L2CAP pair 'Connection Parameter Update 'Connection Parameter Update Request', and 'Connection Parameter Update Response (accepted)' pair, along with LE LL 'LL_CPNNECTION_UPDATE_IND' and the connection interval stays at 20 ms o with WIn 20 device as central, when I attempt to set connection intervals 40 ms, 40ms, the L2CAP pair 'Connection Parameter Update 'Connection Parameter Update Request', and 'Connection Parameter Update Response (accepted)' pair appears 3 times in my Sodera LE logs, but a LE LL 'LL_CPNNECTION_UPDATE_IND' never follows... and the connection interval stays unchanged at 20 ms. I don't see a way to send any attachments here, I will see if I can do this with a private message.

hi David, following your 'clip' instructions I will attach my Sodera LE files for my android and win 10 experiments.

android experiments: see ConnectionParameters.Android.Exp.doc, and _153851. files win 10 experements: see Connection Parameters.Win10BLe4_2Exp.AfterDellUpdate.doc, and _165038. filesConnectionParameters.Android.Exp.doc(/attachment/10e80f2163ed8c98bf9c2a29fb993f2e)(/attachment/85a3a7bc13049eb50c7925e6be6cd650)(/attachmen/afe27087918e3df3c0b4ab41d8af7198)(/attachment/c288201f7a99e6ac8b23c6defc735da1)ConnectionParameters.Win10Ble4_2.Exp.AfterDellUpdate.doc(/attachment/de738b64ada022afd71e624da0c48bbb)

RE: Win 10 BLE stacks, acting as a central, problems accepting BLE connection parameter changes.

David Edwin — Fri, 10 Nov 2017 08:50:28 GMT

Typically Win10 is quite flexible in the connection parameter update process and does not have restrictions beyond those of BTLE. This means that you need to familiarize yourself with the BTLE connection update process which recommends that you do not send the connection parameter update request more frequently than 30 seconds.

In addition Win10 typically tends to respect the PPCP (Preferred Peripheral Connection Parameter) Characteristic and is a good way to communicate the connection parameter preferences to the Win10.

In addition you will need to watch the Sleep Clock accuracy of the BTLE chipset being used on the Win10 central. This will create restrictions on the slave latency settings that will work on the link.

The Nordicsemi nRFready Desktop 2 keyboard reference firmware provides a better understanding of Win10. (Note: This is for a HID Keyboard so the rules are a bit more special, but the general guidelines remain the same). Unfortunately the code is under a product key and available only on purchase of the kit. www.nordicsemi.com/.../nRFready-Desktop-2-Reference-Design

Please post the sniffer trace in addition so I can help you better.