Abnormal connection update request PDU from slave

RE: Abnormal connection update request PDU from slave

Sigurd — Wed, 25 Jan 2017 08:52:45 GMT

Ok, I would then recommend that you summit your bug report as an issue on the GitHub repo where you found the code.

RE: Abnormal connection update request PDU from slave

Jusang Kim — Wed, 25 Jan 2017 01:16:05 GMT

I'm using a nrf52 DK in the central role and a arduino uno in the slave role with an BLE open-source from the github which means the nRF52 Dk does not make any problem. And the direction of the connection update req is the salve to the central when checking the direction with Ellisys BLE analyzer. I think that the BLE open-source that i'm using has a bug on this issue.

RE: Abnormal connection update request PDU from slave

Sigurd — Mon, 23 Jan 2017 11:20:18 GMT

Only the central should send the LL_CONNECTION_UPDATE_REQ. Are you sure that the slave/peripheral is sending the the LL_CONNECTION_UPDATE_REQUEST ? The direction is marked as "?". What devices are you using? is both nRF-devices?

RE: Abnormal connection update request PDU from slave

Jusang Kim — Sun, 22 Jan 2017 00:33:36 GMT

In the attached figure the packet number 193 is sent from master to slave. Howevrr the packet number 196 must be sent from salve to master. and then because the master has received the connection update request from the slave, it sent the unknown response to slave. Based on the specification, the slave shall not send the connection update request. It Can send only the connection parameter update request by using the L2CAP channel. This is what i curious about. . .

RE: Abnormal connection update request PDU from slave

Sigurd — Thu, 19 Jan 2017 13:40:54 GMT

Hi,

In the direction field you can see that the packet is sent from the master to the slave...( M -> S)