Can't calibrate after switching phones. Resetting calibrations stop collection #3884
Replies: 6 comments 3 replies
-
|
Switching phones should not be a problem when calibration is addressed remotely by an intelligence other than xDrip. But, I don't believe xDrip is written to handle calibrations when switching phones if xDrip itself is responsible for handling calibrations. I have no idea if anyone has put any thought into it. But, it doesn't sound like a very good idea. |
Beta Was this translation helpful? Give feedback.
-
|
Just running with that thought though, if the sensor isn't disconnected
just stopped from recieving data from Phone A, that has a populated
caliberation table for that sensor. Why would it fail once reconnected?
What's the difference between;
1) turning off Bluetooth on Phone A off for an hour, for whatever reason.
Going swimming and taking the MiaoMiao off, or putting the phone on flight
mode. etc.
2) turning the Bluetooth off on Phone A and connecting the MiaoMiao to
Phone B which has its own caliberation graph for that same sensor.
Xdrip shouldn't care should it? It has caliberations for the sensor, it's
recognising the sensor and can match it to the caliberations table even.
But something is stopping new caliberations. What's stopping the data from
being received at all if I follow the guidelines in the Xdrip docs for a
sensor that fails to apply caliberations and reset the caliberations.
Surely it should use those 3 readings and 2 startup caliberations to
continue displaying data using a fresh caliberation table.
…On Wed, 5 Feb 2025, 19:44 Navid, ***@***.***> wrote:
Switching phones should not be a problem when calibration is addressed
remotely by an intelligence other than xDrip.
But, I don't believe xDrip is written to handle calibrations when
switching phones if xDrip itself is responsible for handling calibrations.
I have no idea if anyone has put any thought into it. But, it doesn't
sound like a very good idea.
Imagine if we retain in the xDrip database all the calibration parameters
related to a sensor even after disconnecting from it. Now another xDrip
could connect and could create its own calibrations. Now, you will have two
different installations of xDrip both containing calibration parameters
associated with the same sensor. But, there would be no way to sync the cal
parameters between those two xDrip installations.
—
Reply to this email directly, view it on GitHub
<#3884 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUEHIJAB4MEZRH2DEUGTTT2OJSZTAVCNFSM6AAAAABWRZIHH6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBXGM4DQMY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
You may be right. It's been so long since I've used a device that was calibrated by xDrip. |
Beta Was this translation helpful? Give feedback.
-
|
So, maybe I'm just a bit stuck in the same routine. How exactly do you run
your tech? Do you use blood glucose check to calibrate your data at all? Or
do you just trust the incoming data from your Libre/Dexcom?
What do you do if it's wildly out?, I find that to be the most I portant
thing when running a loop with AAPS. I'm keen to avoid it aggressively
trying to bring my glucose in range and reading high, if my blood glucose
checks say I'm in range.
…On Wed, 5 Feb 2025, 20:07 Navid, ***@***.***> wrote:
You may be right. It's been so long since I've used a device that was
calibrated by xDrip.
—
Reply to this email directly, view it on GitHub
<#3884 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUEHILSOV5275RJ3NDJE632OJVQDAVCNFSM6AAAAABWRZIHH6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBXGQYDMNQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I didn't mean you should switch to my setup. I rarely have felt symptoms that disagreed with what G7 was showing. In that case, I have calibrated. But, this may happen once every 3 months. May be not even. |
Beta Was this translation helpful? Give feedback.
-
|
It's been ages since I took a look at the way I've set up Xdrip honestly.
It seemed like for ages, caliberation was just one of those things everyone
did. I guess I was just wondering if perspectives had shifted, it felt like
maybe it had since other OOP2 alternatives like Juggluco don't accept
caliberations at all.
It's not easy keeping up, and I somewhat consider myself pretty aware. 😂.
the MARD on Libres of 10% just doesn't seem to be that true, especially in
the first couple of days. And when those values are hooked up to a closed
loop artificial pancreas system. Well I've gotta say having those values
used for automatic treatment seems like a crazy idea without caliberation.
They can be hugely out of whack.
…On Wed, 5 Feb 2025, 21:22 Navid, ***@***.***> wrote:
Sorry, I didn't mean you should switch to my setup.
As it happens, I use Dexcom and I currently use G7.
I rarely have felt symptoms that disagreed with what G7 was showing. In
that case, I have calibrated. But, this may happen once every 3 months. May
be not even.
I don't feel that my CGM has to be exactly equal to my blood glucose meter
so that I can use it. For me, it is meant to keep me away from hypoglycemia
and extreme highs. If it is a little bit off, I am not going to worry.
—
Reply to this email directly, view it on GitHub
<#3884 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUEHIMEPCGWIIZ5FDETXF32OJ6JXAVCNFSM6AAAAABWRZIHH6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBXGQ3TINY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I would just bring to your attention that a blood glucose meter is not perfect and has its own sources of error and inaccuracy. There was a time when CGMs were really bad. That was when the impact of the immune system had to be addressed with calibration. |
Beta Was this translation helpful? Give feedback.
-
|
That log screenshot appears to show a load of bad data being received and tossed away. Is that still happening ? Does the OOP2 screen show data values when used with a MM3 and are you on the 31/5/24 version of OOP2 |
Beta Was this translation helpful? Give feedback.
-
|
I'm on the latest version, and oddly enough I don't get values reported in OOP2. I started a new sensor in the end, so I'm back to working but I'll be back to the same problem if I flip to another phone and back. I've just kept an eye on the log for my latest reading and even though things are fine and I'm recieving data that displays fine, I'm still getting those BG Timestamp errors. |
Beta Was this translation helpful? Give feedback.
-
I switch between two phones on occasion that both work as collectors in a MiaoMiao3 Libre2 setup using OOP2 running Xdrip version dfcbe80-2024.09.17
I find that switching phones is fine, I just disable Bluetooth on one phone and enable on the other.
but when I switch back to the original phone although I get readings I lose the ability to calibrate as I get repeated errors that stop the calibration.
I thought that perhaps resetting the caliberations might work, but that brings in only a few readings at which point any new data is rejected as there is too much data being received.
I tried stopping and restarting the sensor too, but that again only brings in the 3 readings used to allow me to set the caliberations and anything else is rejected.
Beta Was this translation helpful? Give feedback.
All reactions