Last night, I started trialing a sensor with the new 630G pump. And I ended up having a night from hell. I started off low. After correcting the low, the sensor kept insisting I stayed low. This went on all night long (does this sound familiar? This exact scenario happened back in November, too). As part of the trial, I had the low suspend turned on. Part way through the night I had to turn it off because I wasn't able to sleep worrying about my insulin being turned off on me. Then I also had to turn the alarms off so I could sleep.
Oh, I didn't realize the 630G would insist on a calibration 6 hours after the first one. I did a calibration an hour earlier than that, thinking that would be fine. Apparently it wasn't. An hour later the pump woke me up insisting on a new calibration.
So then I woke up around 11am this morning and did a calibration (the pump was still insisting I was super low when I definitely wasn't). The pump refused to accept the calibration. Around this time I turned the sensor off and reconnected it, then did the second calibration (with a new glucose reading). That one failed, too. But this time the pump also told me to change out the sensor. So I phoned Medtronic right away to troubleshoot. We ended up pulling the sensor; it had a slight bend to it. Apparently the calibrations also fail when the number is something the pump isn't expecting (so quite a bit higher or lower than the pump/sensor/transmitter all think it should be).
So now I'm starting a new sensor. Hopefully this one will work better. As a precaution, I used the sensor inserter-thingy that I got with the VEO rather than the one with the 630G. They're very similar (and the one with the 630G is honestly easier to use, requiring less steps), but I'm worried that when I used it (and was confused because I didn't realize it needed less steps), something went wrong on insertion. This insertion seemed to hurt a bit less than yesterday's, so hopefully this is a good sign for the week!
Saturday, 13 May 2017
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment