bewest

is animas data buggy?

It appears to be missing extended bolus information!?

$ cat examples/Insulin-use-and-carbs.csv | cut -d',' -f 3,4,5,6,7,9 | grep -E "Volume|unknown" | head
Bolus Type,Bolus Volume (U),Immediate Volume (U),Extended Volume (U),Duration (min),Notes
Combination,0.900,,,60,Combination unknown
Combination,0.550,,,30,Combination unknown
Combination,1.500,,,30,Combination unknown
Combination,1.500,,,30,Combination unknown
Combination,0.350,,,30,Combination unknown

bewest

bewest

https://gist.github.com/bewest/9458012#file-ftdi-info-plist-L454-L475

		<key>Asante Porter</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.FTDI.driver.FTDIUSBSerialDriver</string>
			<key>ConfigData</key>

bewest

Howdy,

I'm using a Medtronic Carelink usb stick (to download my insulin pump data).
With usb 2.0 ports, it works very well thanks to the usbserial module.
I noticed newer kernels discourage users from doing something like:
     modprobe usbserial vendor=0x0a21 product=0x8001
There is a notice printed to contact the linux kernel developers.
I expected the serial device to be created silently, are more than just the
vendor/product ids needed?

bewest

A21

Unexpected restart, a cold reset was performed. (Return to factory defaults).

A17

On second occurrence replace pump.

bewest

From 82bf3dcd649af33d8f41aa2098bd61bfa94cbc04 Mon Sep 17 00:00:00 2001
From: Ben West <bewest@gmail.com>
Date: Wed, 19 Mar 2014 20:34:33 -0700
Subject: [PATCH] Add AsantePorter PID 0x7F38 to FTDI list

This patch allows the ftdi usb serial module to create a device when
an Asante Porter usb data cable is plugged in.

Signed-off-by: Ben West <bewest@gmail.com>
---

bewest

Medtronic comlink RF

Here are some captures. All sample rates are at 1.0 Msps.

These were created:

bewest@patient:~/src/meter-pump-link$ history | grep rx
 505 uhd_rx_cfile --help

bewest

I thought I had enabled debugging.
My boot config has
* CONFIG_USB_DEBUG=y
* CONFIG_USB_SERIAL_DEBUG=m
and several other relevant looking items set to y, perhaps I simply
need to dynamically enable debug by setting something in sysfs?

I've been playing with this this (v3.14-rc7) extensively over the past
few weeks.

bewest

do stuff with an insulin pump over RF

using Namespace(begin=None, bytesPerRecord=None, command='tweak', descr=None, dryrun=False, effectTime=None, end=None, init=False, maxRecords=None, name=None, no_postlude=False, no_prelude=False, no_rf_prelude=False, other='ReadGlucoseHistory', page=82, params=None, port='', postfix=None, prefix=None, prefix_path='', save=True, saveall=False, serial='665455', verbose=None)

bewest

FOUND 2003-05-19T06:39:38 @ 0 0x000000

previous

0000   0x66 0x66 0x67 0x66 0x13 0x13              ffgf..

datetime

0000   0x66 0x67 0x66 0x13 0x13                   fgf..

FOUND 2006-05-19T19:38:39 @ 1 0x000001

previous

0000 0x66 f