This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Delay between notification value and logged value, nRF Connect

I use nRF Connect to debug some latency in logging data on my Android app.

On nRF Connect, the latency for the notification value (in the characteristic itself) is negligible.

Strangely, when I open the nRF Connect log, I see noticeable delay in logging the same value. What is the reason behind this ?

Parents
  • Hi,

    The reason for the delay is that the nRF Connect when notified collects the logs in memory with timestamp and then only flush the logger every +second, even if notifications comes more often. This is to avoid being unusable when the notifications come too often. But the timestamps should be the same even though there is delay.

    Best regards

    Jared 

Reply
  • Hi,

    The reason for the delay is that the nRF Connect when notified collects the logs in memory with timestamp and then only flush the logger every +second, even if notifications comes more often. This is to avoid being unusable when the notifications come too often. But the timestamps should be the same even though there is delay.

    Best regards

    Jared 

Children
Related