Missing connect requests

RE: Missing connect requests

Karl Ylvisaker — Fri, 28 Feb 2020 14:45:30 GMT

No problem at all, I am glad to help!

You are correct, the sniffer will sometime be able to receive packages that other devices does not, and vice versa - depending largely on its position relative to sender, but also on the general interference on the 2.4 GHz frequency and obstacles in the path of the signal.

Best regards,
Karl

RE: Missing connect requests

MKJ — Fri, 28 Feb 2020 14:37:04 GMT

Ok, thanks - it was just that I could see the connect request on Wireshark but of course that device is in a different position to the peripheral under test.

RE: Missing connect requests

Karl Ylvisaker — Fri, 28 Feb 2020 14:03:07 GMT

I could not find anything unusual in your log, regarding the missed connection request.

Missing one in ten connection requests however does sound normal, depending on local interference(not just from other Bluetooth communication, but everything on the 2.4 GHz frequency). Normally the central will assume connection after a connection request, but when it falls through you can just send another connection request immediately.

Best regards,
Karl

RE: Missing connect requests

MKJ — Fri, 28 Feb 2020 10:01:13 GMT

devzone.nordicsemi.com/.../ConnectFail.pcapng

Here's the wireshark log the peripheral device address is F9:45:36:CE:2C:3B

Occasionally - one in ten

RE: Missing connect requests

Karl Ylvisaker — Fri, 28 Feb 2020 09:40:23 GMT

Hi,

Could you be more specific with what you mean when you say "occasionally", how often is this roughly occurring?
It is possible for a packet to be corrupted from interference, even when the amount of possible interference sources seems minimal.
Could you provide the Sniffer log from Wireshark, so I may take a look at it?

Best regards,
Karl