To the kind Nordic support team,
I have got a nRF52833 based Raytac module I'm using to develop before using a custom board.
I'm using Microsoft Bluetooth Virtual Sniffer (https://techcommunity.microsoft.com/t5/microsoft-bluetooth-blog/introducing-bluetooth-virtual-sniffer-btvs-exe/ba-p/2113478)
so to monitor ble disconnections. I left this test system on from 19:00 in the evening to about 9:00 in the morning. I'd like to repeat this thing more and I'll be updating this post.
What I found is that I'm not apparently experiencing random disconnections, but they seem to follow a very regular pattern.
What could it mean theoretically, in your opinion? You think I could act on connection parameters whatsoever to improve this (never get disconnections)? At this point I'm not sure if these disconnections are due to RC internal source (there is no external 32.768 kHz clock) or to some problem inside the firmware.
My application is always sleeping, but ble event can wake up the app, just to serve ble events. So there is always a background active communication and my prototype is always listed in Windows as Connected and never as Paired. After this Disconnections, the advertising is immediately triggered and the re-connection is done in about a second. Let me please know if need any other detail so to discuss at least theoretically this thing.
Best regards
21:18 (Rcvd Disconnection) ---> 1h21
22:40 (Rcvd Disconnection) ---> 1h22
00:01 (Rcvd Disconnection) ---> 1h21
01:22 (Rcvd Disconnection) ---> 1h21
02:44 (Rcvd Disconnection) ---> 1h22
04:05 (Rcvd Disconnection) ---> 1h21
05:26 (Rcvd Disconnection) ---> 1h21
06:47 (Rcvd Disconnection) ---> 1h21
08:08 (Rcvd Disconnection) ---> 1h21
