Missed GATTC Write Response

RE: Missed GATTC Write Response

ejoyce — Wed, 19 Dec 2018 22:01:02 GMT

Thanks for the response. The connection interval was 30 ms so it's likely that the scan window was causing missed connection events. I modified the scan interval, scan window, connection interval, and connection event length to better suit my application.

RE: Missed GATTC Write Response

bjorn-spockeli — Tue, 18 Dec 2018 15:26:57 GMT

Q1: What kind of connection interval are you using? How many connections is running concurrently? If the scan window is much larger than the connection interval, then some connection events may be dropped, see S132 SDS v6.1 Chapter 15.4.1 Primary channel scanner timing.

Q2: The SoftDevice scheduler will schedule the connection events before the scanner events as shown in the above screenshot from the S132 v6.1 PS. Given that the scan window is not to long.

Q3: No, if the peer never replies to the Write Request, then the BLE_GATTC_EVT_TIMEOUT event will be generated and the link is considered lost and reconnection is required.

Best regards

Bjørn

RE: Missed GATTC Write Response

ejoyce — Mon, 17 Dec 2018 17:36:10 GMT

Forgot to mention scan interval is 160 * 0.625 ms.