I thought the difference was that it forced a restart after 10 days instead of the current 7 days.
Ditto. We get a minimum of 14 day use… Some change out periods go as long as 20 days for us. So if there is a ten day hard stop, we won’t be upgrading. Liam already had getting it changed every 14 - 20 days so not going to put him through more shots of I can avoid it.
If that were true that would be great! If this is only referring to when the sensor session has to be restarted (10 days vs 7), and then if you can go for another 10 day session… Then we would upgrade.
1 Like
Ok, it turns out that the FDA approval letter states quite clearly that “(5) The device must include
appropriate measures to ensure that disposable sensors cannot be used beyond its claimed
sensor wear period.”
That’s from https://www.accessdata.fda.gov/cdrh_docs/pdf17/DEN170088.pdf which is quite an interesting document in its entirety (6 pages.) It’s possible that a work-around can be hacked, but there isn’t any kind of “wink-wink and we’ll look the other way” in the FDA’s statement of that requirement. And the revised 14-day wear approval isn’t expected until 2019.
Helpful reviews of the G6 are at https://www.healthline.com/diabetesmine/newsflash-fda-oks-dexcom-g6-cgm and http://www.diabettech.com/wearenotwaiting/dexcoms-g6-has-arrived-how-might-it-work-for-wearenotwaiting-users/ The latter raises questions and considers implications for looping systems.
2 Likes
How would the transmitter “know” what particular sensor is attached. Is there data stored on the sensor itself or attached in a way that requires a removal of transmitter before it can initiate restart? Just thinking out loud…
Though there is much conjecture on how it works, the most likely method is a much simpler solution
Adding electronics to the sensor would increase sensor manufacturing cost and complexity significantly. A “protocol change” only could be bypassed easily. If they relied on the removal and breaking of the sensor, or just an electrical disconnect/reconnect with the sensor, there would be no reason to require scanning a code on the bottom of the sensor.
It is most likely that the transmitter stores the id of the last scanned sensor in a list of the last X scanned sensors and disallows a restart with an id that is already in the list.
1 Like
Which is why I believe that it is just a firmware thing. It is cheap, it relies on the existing hardware, and is easy to update later. They already do the logging, store a bunch of other data, and have the available NV memory. The code to implement this already exists, requires very little modification, and is bypass proof.
I just came across Dexcom’s FAQ on the G6 https://www.dexcom.com/faq/g6
According to the USA device compatibility list, unlike the G5 app, the G6 app doesn’t run on iPads or iPhone4S or iPhone 5 or 5C. It does run on iPhone 5S and newer. Similarly, the app doesn’t run on some of the older android phones that work for the G5. The full compatibility list is available (US and international) via http://www.dexcom.com/compatibility
2 Likes
Not a problem for me, I still use G4 receiver, no smart phone.
I worry that this is less common now, and may lead Dexcom to discontinue G4. But it is the lowest cost option, getting over 1 year use per G4 transmitter, and 10-20+ days per sensor. For the cost savings G4 is accurate enough.
2 Likes
Man, they are really setting the bar high here, aren’t they?
https://www.accessdata.fda.gov/cdrh_docs/pdf17/DEN170088.pdf
(H) When iCGM values are less than 70 mg/dL, no corresponding blood glucose value shall read above 180 mg/dL.
(I) When iCGM values are greater than 180 mg/dL, no corresponding blood glucose value shall read less than 70 mg/dL.
1 Like
Actually, I’m quite happy to see those particular requirements. This is the first time they’ve stated that for a BG measuring device, if it says even once that you are low when you are actually high (and the reverse), the device fails and will not be approved. In the past they were willing to tolerate the rare error that falls into Clarke error grid region E. Now, it is never ok for the device to say you need insulin when you actually need glucose (roughly speaking.) That’s important for hybrid AP, where the user is less likely to get suspicious and take an investigatory fingerstick.
Of course we’d all like tighter tolerances, but this is a requirement for a loose kind of perfection, and that’s a big step in a good direction.
Hmm, the forum software has just warned me that I’m monopolizing this discussion, so let me step back and let others get a few words in edgewise.
5 Likes
Ignore that. You’re contributing interesting and relevant information. 
5 Likes
Agreed. I enjoy reading your posts, @bkh. I suppose no software is perfect. 
4 Likes
According to Dexcom the old receiver can be upgraded with a software patch to communicate with the G6. Also there is a new app for smart phones and the g6.
1 Like
Ok so we got our G6 this week. Good news: the new inserter is miles better, my son willingly did it himself (he absolutely would not with the G5) and said it didn’t hurt at all going in but “felt wierd” for a few minutes after. It has a lower profile for sure. And the new touch screen receiver is nice by our standards --it is bigger and sturdier looking, but we always managed to break/step on/drop the old small one so that’s a plus. Also you can pair to both the receiver AND a smart device simultaneously (instead of just one at a time) which is much more convenient.
The bad news: the g6 smart device apps are not compatible with ANY of our old grandma smart devices (two Motorola phones and an itouch). So we suddenly can’t transmit to follow app. We needed to replace one of our phones anyway so that will slightly help…but my son always used the itouch to pair with the sensor for when he was at school etc. Groan.
Ideally I’d love to get him a standalone smartwatch that was compatible with g6, to get a wearable that also paired with the transmitter, no phone required. But from the list of compatible devices on dexcom site, I can’t see any standalone watches. Apple watch doesn’t work with itouch, or at least not ancient itouches, I believe.
Anyone more tech savvy than me have experience with this issue? Or is there a more recent string sharing experiences with the g6?
Glad you’re liking the G6! The disk pairing was possible with previous versions also though! My wife and I use the G5 and we both also use the G5 mobile app as well.
If you want standalone watch reception at this point you’ll have to go with xDrip+. I have been using watch for almost a year with no problem.
Which watch works as a Standalone again? Maybe I can buy that for my son and steal his iwatch
Sony SW3 works right out of the box and can stand alone as a collector.
2 Likes