Hi @mringwal … another question we are experiencing, in case it can be related to an issue on the BTstack and report it if you consider. we have implemented a central and a peripheral device on DUO devices from BTstack in order to check the max available throughput … in all cases, the peripheral request an update of the connection parameters to the central device, in one case to set a connection inteval of 30ms, and the another one to set a value of 100ms. In this last case, everything works as expected (at least, we expected), but in case we try to update the connection interval to 30ms (despite it is the default initial value), the central accepts the request, but a bad behavioral is seen when notifications are enabled and sent, since there are a lot of packets aparently resent (because unexp. NESN), and and abnormal number of packets sent per connection event. this behavioral is almost the same in case we try to set the connection interval to other low values, and as we increase the connection interval, i.e. to 80ms, the observed behavioral gets “better”. does it make sense?. Attached you can find the captured data from a ble sniffer. wewould greatly appreciate any help oin this issue … and we thanks your support, as always. thanks
EDIT(1). FYI we are not using recent versions of BTStack.
EDIT(2). when we try to update the connection interval to 30ms, at first it works ok, but after a while, the unexpected NESN errors appear and retransmissios begin … @mringwal, can it be a problem related to the reception buffer at the central device? how can i check that?