Thursday, May 22, 2014

Calibration Data Part 2

Accidentally deleted the other post, when I tried to update the formatting.  Here's another go, this time with a 7 day old sensor, transitioning to a 0 day old sensor :).  Interesting here to see how the Intercept doesn't change.  Slope was 906 before recalibration, SAME intercept.  This sensor has had other intercept values, most recently 27626.

                                                                                                                -rc (02 2D)--
01 16 02 01 87 06 00 00 03 00 00 00 05 02 2D 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 EA 57
----date---- -- date ---  --slope=767  ----------  
FD C9 1F  0A 94 92 1F 0A  4B 4B 4B 4B 4B FB 87 40  
Intercept=30000--------
00 00 00 00 00 4C DD 40   00 00 00 00 00 00 F0 3F  03 06 00 00 00 00 00 00 00 00 00 02

 -- Date---  --gluc--    --counts-   --date ----
D4 C9 1F 0A 88 00 00 00 E0 0C 02 00 67 C9 1F 0A 00
DE C9 1F 0A 88 00 00 00 E0 0C 02 00 67 C9 1F 0A 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 BD B4

With two more calibration data points, slope is at 820, intercept continues to be unchanged.


Posted by at

6 comments:

  1. AdCMay 22, 2014 at 2:21 PM

    Hi Don. that record has 2 sub-records in it, It also has the bootstrap intercept value of 30000. I think you'd find the previous cal record has intercept of 0. Otherwise the receiver would need some way of identifying the sensor in order to tell the difference between a new sensor and a restarted sensor. I don't believe it can tell the difference, so just boot-straps again.

    ReplyDelete
  2. IJune 13, 2014 at 2:00 PM

    This comment has been removed by the author.

    ReplyDelete
  3. IJune 13, 2014 at 2:04 PM

    Hi,
    Unfortunately I can't help but I reeeeeeally appreciate what you're doing.
    The only way I could help you is providing the electronics of an animas vibe. Would it be in any way useful? It should be working and I have pictures I took during dismounting.
    Regards

    Fivepointfive

    ReplyDelete
  4. Cuzin BSeptember 26, 2014 at 9:14 PM

    Hi!
    Just a quick question, sorry if you answered already: are you aware of the NightScout #wearenotwaiting project? It has a similar scope to your project, but takes a different approach...using an android phone that is connected to the dexcom receiver and it uploads the CGM data to the internet. Maybe, at least, you could take a look on how they hacked the data readings...
    http://nightscout.info/wiki/welcome

    Best wishes,
    B

    ReplyDelete
  5. tv1751October 2, 2014 at 10:31 AM

    Don, I know you've used meta-watch due to its waterproof-ness. Just thought i'd link you to the dev sight for Garmin. They recently announced that they are opening an SDK for their wearables and claim once you write the SW it will be easily portable between compatible units. http://developer.garmin.com/connect-iq/overview/

    Also I'm looking to replicate your work for a similar device for myself on either a Pebble or Garmin watch. Any sw, code etc that you would be willing to provide would be appreciated as well as more info on the hw in your dexcom cradle/mount you showed in your 1yr aniversary post. Thanks for all your work!

    Taylor

    ReplyDelete
  6. DonOctober 4, 2014 at 9:57 AM

    See today's update. The Metawatch was good on many counts. Most of these other devices require (or will require) a device that can do a BLE Central role. I've just picked up a board for this(and it's beta), but I'm not very optimistic.
    I don't want to have to rely on a phone for this to work, so it's the Metawatch for now.

    ReplyDelete

Subscribe to: Post Comments (Atom)