View Single Post
      11-27-2021, 10:30 PM   #44
UncleWede
Long Time Admirer, First Time Owner
UncleWede's Avatar
United_States
17883
Rep
9,376
Posts

Drives: G01 X3 M40i Dark Graphite
Join Date: Jun 2005
Location: Oxnard, CA

iTrader: (0)

Quote:
Originally Posted by vreihen16 View Post
Uh, oh! The FL2 started throwing a scan error this morning:

Attachment 2752621


Restarting the app and rebooting the phone did not fix it, and both the NFC (scans) and Bluetooth (alerts) interfaces were offline. It recovered after an hour or so, and immediately sent an alert that my glucose was high.

From a web search of a few UK diabetic forums, it appears that the FL and FL2 have a built-in error prevention routine. If it detects an implausible reading such as a rapid rise or fall, it shuts down the interfaces for a while until the measurements stabilize. Better to report nothing than report flawed/dangerous information.

Long story short, it went offline in the 170's and climbing, and came back online in the high 200's and falling. It must have been a huge spike right after breakfast that triggered the error. There was a gap in the graph from the times that the sensor was offline.

I never saw this happen with the original 10-day or 14-day FL sensors, and will be keeping a closer eye on the FL2 to see if it goes offline again when I'm not looking.....
Dang, conspiracy theory now. 3:47 try again in 10 minutes. I'll be back asleep in ten minutes. Pee, try again, same message

7:05 scan, replace sensor. Checked manual and at 279.
__________________
I have romped on her and I giggled like a drunk infant the entire time. - Sedan_Clan
Appreciate 1
vreihen1614906.00