Whether you use the code or not is solely up to you. If you had used it, the G6 wouldn’t have required 2 calibrations every day. A lot of us take a picture of that code so we can reference it again in 10, 20, etc… days.
Unfortunately the calibration code is outdated when you restart, and the data will come back terribly high. You can gently walk it down in several partial calibrations, spaced at least 15 minutes apart and then not be forced to do anymore calibrations for the rest of that session. OR, you can skip entering the code altogether and enter routine calibrations every day. It will ask for a calibration right after warmup, I think 2 hours later (I’ve never actually done this, so this may it may not be true), and then twice a day for the rest of the session.
I’m currently on day 23. I don’t usually do a 3rd restart, but if I make it to 30, I think I’m going to try the “no code” method, just to see if I like it. I test a few things a day anyway late in a sensor’s life.
[ OR, you can skip entering the code altogether and enter routine calibrations every day. ]
Ahh! ! That’s the confusing thing… I did not use the code on the 1st sensor install; and in my ignorance, did 2 calibrations within the 1st 48hrs after it came onLine ( Time Sensor started: 19Oct, 21:07; Last Calibration: 21Oct.06:21 ). I have not had to do a calibration since then, contrary to what I’m reading here about calibs every day? Does that make sense?
LOL. That’s a hilarious way to think of it. Yes, the sensor can start to stray at the end of life, but can usually be bullied back into line with more calibrations. In my experience, it doesn’t “turn” as disasterously as spoiled milk. That’s not the most reliable way to observe end of life, though…
Your CGM graph doesn’t actually show you the raw data, but rather uses an algorithm based on previous data and the new raw data it just collected to smooth out and pretty up the displayed graph. As an Android user, I’m fortunate enough to be able to see that raw data in the Xdrip app. At the end of a sensor’s life, the raw data strays farther and farther away from the displayed point. It looks completely erratic, rather than following a smooth line. This can lead to some variation from a fingerstick, but what you’ll really see most often is failed data collection. I think on the Dexcom app and receiver it just looks like missing spots on the graph that are never backfilled. On my t-slim pump, it will also show missing dots on the graph, but it will also display “- - -” or “???” on the screen… Which literally just means Dexcom is confused by erratic data.
When you start missing big chunks of data, it’s time for a new sensor. Or, if you feel you can’t trust it anymore, it’s definitely time for a new sensor.
Sorry for the going heck and forth, we keep writing at the same time.
Did the Dexcom MAKE you calibrate, or did you just choose to calibrate that first day? Freedom what I understand:
No Sensor Code sessions : A sensor session that was begun by choosing the “No code” option will ask for 2 initial calibration BGs after warmup. After that, the session will prompt the user for a calibration point 12 hours later. If that calibration is not given, the prompt will reappear until it is given. Inputting a calibration point resets that timer and you won’t be bothered for another 12-24 hours for a calibration.
So that doesn’t seem normal to enter two calibrations the first day and then never again, unless you did so voluntarily.
Occasionally though, Dexcom will actually request a calibration, even if you used a code.
If you didn’t actually enter the code, is it possible you scanned it with your phone via the phone app?
If you do 2 exact calibrations right in a row, it takes the second number as gospel and will not ask for repeated calibrations. It’s also a way to get rid of repeated requests for calibrations.
Mine is not connected to a pump though.
I always stop sensor or let it expire on both my phone and reader and enter my code into both devices when restarting.
Mine almost always lets me know it’s going by losing connection or missing data on my graphs. Mine like to last about 25 days. But a couple have lasted only 15 days or they were never as good in the first place and I changed them out. I’ve had a couple go past 40 days and regularly go past 30 days.
@Robyn_H, thank-you. I recall I chose the “no code” option, and absolutely certain there was no accidental scan via phone option. I then chose to do a calibration after the warmup; it seemed to me to be a good baseline idea. It was not prompted by Dexcom. I manually did two, within 12hrs of the initial installation: (20 Oct, and 21 Oct.06:21hrs). I have not been prompted to do any further.
I think in hindsite, that is correct operation: 2 calibs within 12 hrs of install.
I should have read the manual!
It’s very easy actually - thanks to a lot of people here who have given well advice. I was worried about the sequencing of steps initially but everything just fell into place. I used a guitar pick to dislodge my sensor transmitter, its a brilliant idea that @Terry4 posted in one of the other older threads. Was super easy to get out.
I refrained from touching my phone app (didn’t even use it to stop the sensor or restart it), everything eventually sync’ed up after maybe 10-20 mins. Did everything on the pump as suggested by other people in the earlier replies.
I did enter the sensor code at the restart on the pump rather than selecting the no code option. You will be prompted so don’t worry you will know what to do when the prompts come up.
I think this is good advice. Based on my experience with previous CGMS experience with medtronic sensors, they are super picky about fluctuations and being out of range. So I assumed the same for the dexcom as well and tried to get my sugars reasonably in good range BEFORE the restart so it’s stable during the 2 hour warm up session. I don’t know whether it does make a difference. Its hard because my sugars are usually a bit all over the place after a meal. And as @Robyn_H pointed out to be in good range at the start of the first data point.
I’m almost on my 3rd day after sensor restart and things seems to have calmed down a bit by middle of day 2. Its still not exactly the same reading as the meter (which I got at one point for a short while on my first 10 days) but close enough to deem it still accurate. I think it needs one more calibration to line up but the difference hasn’t been greater than 20% (close though) so I left it alone for now.
One more thing, I actually stopped my sensor rather than having it expire. This was a last minute decision that I didn’t anticipate to do. The reason I did this was i wanted to end my sensor when my sugar was in range and not fluctuating to give it a better chance of accuracy on restart. Again all related to sensor stability. I think its perfectly fine to let it expire too but I was in a good range at the time and didn’t want to screw it up in the lead up to the sensor ending. My theory is leave it in a good place and it will resume in a good place . Not sure it makes any difference but as you can see I go out of the way to be super nice to my sensor and stroke it’s ego a bit at this time.
Thanks for the detailed G6 restart instructions! Just did my first successful restart, seemed to go smoothly. I used my 15 minutes after pulling the transmitter to reinforce/overtape my sensor.
I still don’t get why we are doing it though.
I tried it and was successful. However the transmitter goes belly up after the 9th sensor so then you have extra sensors w no way to use them.
For me anyway every quarter I get a 9 sensors and a transmitter.
I had 2 extra sensors this round but I don’t see the point to restart anymore now that we can’t reset the transmitters. Why has no one created a third party transmitter I wonder
Back when I started on G5 my insurance did not cover, I went about a year as a cash payer for G5 sensors and transmitters and extended both as long as possible to save money. That got me in the habit of stretching everything as long as possible. Now on G6 I want to extend sensor life so I can save a few sensors for a rainy day…my copay (private insurance) is about $40 per sensor. Maybe some day I can save some dough by not buying 3 sensors per month for a few months? Only possible if many sensors are extended before the rainy day.
Plus I always bring 2 spare sensors in my travel bag, not possible if I use them as fast as I buy them (3 per 30 days).
I don’t think that’s true, though. I start WAY more than 9 sessions in a month, even if most of them are restarts. The transmitter doesn’t know that, though. I think you just had bad luck that your first one died exactly at 90 days. The only hard limit I know of is that the transmitter wont let you start a new session after day 100. If you start (or restart) by day 100, though, you can get up to 110 days of use. The reality is that it depends on how long the battery holds out, though.
The reason most of us restart is because supplies are difficult and unreliable to get ahold of. Some of us just because of the prohibitive price, and others because the insurance nightmare makes timely deliveries nearly impossible.
So those “extras” you refer to do indeed get used and are appreciated when your next delivery doesn’t show up on time, or your sensor fails prematurely, or gets ripped off, or gets stuck in the inserter, or…
It’s especially an issue for those on Medicare. I’ve only heard of 1 or 2 companies that will do 3-month shipments, because Medicare doesn’t allow 3-month billing for DME. The ones that do are essentially lending 2 months of Medicare billing to the patient, and billing Medicare monthly in the background. For everyone else on Medicare, the DME provider can’t even bill/ship until the next month, and there’s no padding for shipping delays. Building up an extra stash is the only way to ensure seamless supply coverage
Yeah, all those real life events that suppliers and payers dismiss when they employ a “just in time” logistics model. I love the peace of mind that a few (or even several!) spares give me in this time of uncertainty. I can count on my diabetes showing up every day. The timely dependability of my diabetes supplies, not so much.
I was able to get a cushion of G4s, and when started G6 delivery, while I continued to use G4 cushion. G6 makes this a bit more challenging due to shorter transmitter life. My first G6 supplier shipped 2 transmitters with first order, but only 90 day sensors. So 2nd transmitter died before its 90 day warranty, and had to get replaced from dexcom.
Now I get G6 transmitter at Costco, every 90 days, no worries about shipment times. But insurance only allows 30 day supply sensors when done at pharmacy.
I don’t pay for them and I have a good sized stash, and I never have to worry about any shipments arriving. That’s because of restarts. But I like the less of a hassle of a restarted sensor. Calibrate a restart a few times and I pretty much ignore testing except to check every 5 days just to make sure it’s doing good or if I get suspicious.
I think a restart is less of a hassle in my case. No new area to put one on, no constant checks to see what it’s doing, no fine tuning with calibrations the days after insertion, (I like them within 5 points) it’s just easier.
I just want to check something re the no code option in case I have to use it next time.
The manual says:
2 hours after you start the sensor session, the CALIBRATE CGM screen will appear, letting you know that 2 separate BG values from your meter must be entered. You will not see sensor glucose readings until the pump accepts the BG values.
Is there are time frame between when the first and second BG must be entered? If so, any guidelines as to when to take the second one?
Or are you supposed to take reading from two seperate fingers and enter it one after another?
Dexcom knows that the meters have a big possible margin of error. It basically wants two different readings from the same sample, so it can average them out. Just squeeze a new drop of blood out of the same fingerstick, and repeat the test as soon as possible.
I take blood samples from two different fingers and two samples from the same blood drop like @Robyn_H also works. I think the system expects two readings within minutes of each other. I’ve never extended the second reading with with the G6 or G4.
I just restarted a sensor yesterday and I input my two meter BG numbers. On the first day of a no-code sensor session, whether first-start or restart, it does prompt for another fingerstick 12 hours later but continues to display readings.
Essentially, any fingerstick readings required after the first two are what I would call a "soft requirement’ in that the system continues to work and display and will not sound any alarms. But Dexcom warns that failing to give the system a meter reading at the time it asks for it risks inaccurate readings.
This is nice since my 12-hour meter reading occurred at 1:00 a.m. I put it off until I got up and everything is working well as this morning as my meter read 74 and the G6 read 76.
I’m not averse to fingersticks, so using the no-code option is not burdensome to me. My new habit is to enter the sensor code for the initial session and then no-code for the second one as suggested by @MM1.
I haven’t actually done a no code restart yet, so this is very good to know. I don’t have any issue calibrating the first restart, and find the sensor still works incredibly for me and thus rarely ever test between days 1-20 anymore. It’s the second restart that gets problematic. I think going forward, I’m try the no code method for days 20+.
And FYI, for those wanting to know what a end-of-life sensor looks like, this is what my data looked like last night.
I usually flat-line at 100-110 all night long, thanks to Control-IQ. Last night was crazy, though. If you look at that data, you’ll see tiny “raw data” points (the smaller pink dots, the bold pink dots are the numbers the Dexcom algorithm displays) that are scattered about everywhere, not lining up with the graph. That leads to erroneous CGM data, since Dexcom uses recent data to eliminate “noise” on the graph. Despite that smoothing, the final displayed data still jumps around like crazy. You’ll also see big patches of missing data altogether.
I used to consistently get 30 days out of a sensor, but recently it seems more like 25. This is yet another day 25 death. Technically, I could probably limp it along a little farther, but I don’t trust another night to this erratic data.
. Not sure it makes any difference but as you can see I go out of the way to be super nice to my sensor and stroke it’s ego a bit at this time. 
