Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Possible to fetch some statistical information about a BLE connection?

Hi,

is it possible to get some statistical information about a BLE connection?

Background is, that I'm experiencing connection problems (degrading throughput, stuttering connection) if more than one packet/event is used.  With one packet/event connections are (more) constant, nevertheless performance could be better.  So I want to autodetect, if there is a connection problem and then as a consequence reduce the packets/event to one in such a case.

Hardy

PS: happens on S13x V2

Parents
  • Hi,

    Unfortunately, there is no autodetect to see if there is a connection problem. But you can get some statistical information by setting up a timer to see how long it takes from you queue a packet until it is sent. You can see how many connection intervals it takes before the packet is sent, this way you find out if there are any packet loss.

  • Thanks for the suggestion.  BTW: I did not expect that there is a buildin autodetect feature.  I want to implement this on my own.  My idea was to get a total packet count and a transmission retry count from the softdevice, because it is hard to get this from the outside of the blackbox softdevice (e.g. one cannot distinguish between a packet simply not sent to the central because the central is not ready with a transmission retry).  And if you are not expecting a continuous data stream it is even more difficult.

Reply
  • Thanks for the suggestion.  BTW: I did not expect that there is a buildin autodetect feature.  I want to implement this on my own.  My idea was to get a total packet count and a transmission retry count from the softdevice, because it is hard to get this from the outside of the blackbox softdevice (e.g. one cannot distinguish between a packet simply not sent to the central because the central is not ready with a transmission retry).  And if you are not expecting a continuous data stream it is even more difficult.

Children
No Data
Related