You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the cgm page decoding algorithm detects that a page doesn't have a reliable sensor timestamp for forward looking offset, it needs to send a command to add a sensor timestamp to the glucose history page. Something in that code is incorrectly setting a new timestamp repeatedly in some circumstances. This causes glucose history pages to fill up more quickly and adds more page fetching that lessens battery life and reliability.
When the cgm page decoding algorithm detects that a page doesn't have a reliable sensor timestamp for forward looking offset, it needs to send a command to add a sensor timestamp to the glucose history page. Something in that code is incorrectly setting a new timestamp repeatedly in some circumstances. This causes glucose history pages to fill up more quickly and adds more page fetching that lessens battery life and reliability.
An example of the problem: https://diagcare.herokuapp.com/cgm_pages/DE0B68E27914E6EC8E211624D3C00CE6456164E8
The text was updated successfully, but these errors were encountered: