Replies: 3 comments 24 replies
-
Would you please post a screenshot of the system status page so that we can see the firmware number? If it is really 2.27.2.108, we will need to update xDrip. |
Beta Was this translation helpful? Give feedback.
-
SUCCESS --- finally!! :-) Calibrating -49 mg/dl (maybe 50 delta is the limit?!)! Still running on 2022-03-11. I checked my History and must admit, that I don't have many examples where I had over 50 delta after a restart. This seems to be an extreme case with an extreme "restart delta". Usually I had always ~30-40 mg/dl delta values which I always successfully calibrated with the "1-shot calibration" in the past. I never calibrated twice, honestly. By the way, this "confused calibration" error you're mentioning in the FAQ I only remember from the days with the old 80x transmitters. Have never seen this error with a Firefly. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Have recently updated from xDrip+ 2022-03-11 to 2022-06-20. I've been calibrating "restarted G6 sensors" many, many times without this issue: Calibrating "down" as needed when restarting G6 does not work properly any more. The transmitter accepts calibrations but only calibrates approx. 1/3 of the way down.
See screenshot below: At 1st attempt reading was 202 and I calibrated to 105 -> xDrip only got it down to 176 ! Next attempt 10 mins later had "no effect at all" (probably calibrating too fast? but still, transmitter in log saying "calibration accepted" which is obviously untrue). I already had the same effect 10 days ago - it took me approx. 5 calibrations in 2 hours to finally bring readings down to the right level. In the past with the older nightlies I always calibrated "1-step" down without an issue. I never needed multiple attempts... Has anything changed in xDrip+ calibration code or is this caused by a new transmitter firmware? I currently have an "8U" tx rev. 2.27.2.108. Thanks for any hints.
By the way: Error message "Received backfill packet out of sequence" in the logs I think is normal - at least this also always appeared in the older version. Not sure what this means, does anybody know? Is this relevant at all?
Beta Was this translation helpful? Give feedback.
All reactions