| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This was mixing up the units in the conversion. While fixing the bug,
remove the confusing two-parameter form of convert_glucose_unit.
|
|
|
|
| |
This makes the code more idiomatic and less brittle.
|
|
|
|
| |
This makes the code more idiomatic and less brittle.
|
|
|
|
| |
This makes the code more idiomatic and less brittle.
|
|
|
|
|
|
|
| |
This was meant to be lifescan_common, and then renamed to just lifescan,
but clearly I forgot that.
Addresses part of Issue #29.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This change also remove the meal field from the _ReadingBase class and
moves it only where it belongs, i.e. in the GlucoseReading class.
|
|
|
|
| |
This renaming prepares for the ketone class introduction.
|
|
|
|
|
| |
This new measure_method stores origin of the measure (either blood
sample or from a CGM sensor).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
One of the professional options allows to choose the insulin increment
step between 1 and 0.5 unit.
This explains why the insulin dose values with no decimal part seems
doubled in memory.
This change adjusts the formating and computation when displaying these
data.
|
|
|
|
| |
The unpacked value is an integer, not a byte array anymore.
|
|
|
|
|
| |
While Verio 2015 does not appear to expose this information, Select Plus
devices do, and the mapping is very simple.
|
|
|
|
|
|
| |
The reading value is only 16-bit long, not 32-bit. The following byte is a
meal indicator (not implemented in Verio), followed by a (likely) constant
0x00.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This restores the original behaviour, that seems to be necessary for the
FreeStyle devices.
|
|
|
|
|
| |
This is important for a meter I'm working on right now, as there is no
obvious way to tell whether to wait for new packets or not.
|
|
|
|
| |
This is a semantics difference between hidraw and HIDAPI, cover for it.
|
|
|
|
|
| |
I'm currently implementing a separate HID-based driver that does not use
the Abbott protocol, so this makes my life easier.
|
|
|
|
|
|
|
|
|
| |
This allows these drivers to be used on operating systems other than Linux,
as hidapi abstracts away the access. The interface is similar enough to
using hidraw that the actual code only needed minimal changes.
Maintain the ability to access the devices with the hidraw path too,
without forcing the dependency.
|
|\
| |
| | |
Fix encoding info and add missing __init__.py file
|
| | |
|
|/
|
|
| |
even if rapid-acting-flag is set double-rapid-acting-insulin record does not always exist, so make it optional and provide a default value
|
|
|
|
|
|
|
|
| |
This allows the drivers to keep up to date with what they support and
need. Should make Issue #9 easier to solve.
Also merge the dependency list with the list of supported devices, so that
you don't have to join the two tables in your head.
|
|
|
|
|
|
|
|
| |
This allows the drivers to provide information on what they support
directly, rather than relying on the README file. It also allows to provide
further information for the quirkier devices.
This is again trying to resolve Issue #9.
|
|
|
|
|
|
| |
This allows the serial support class to open the serial port without each
driver having to pass the same long list of parameters, given that
effectively all the meters use the same parameters, except few.
|
| |
|
|
|
|
|
|
|
|
| |
pyserial makes it very easy to look for a serial port based on VID/PID
pairs, so use those when possible. Unfortunately serial drivers are also
the least reliable as all of the cables but Abbott's use generic IDs.
This keeps in the direction of solving Issue 9.
|
| |
|
|
|
|
|
|
|
|
| |
This requires the drivers to validate their device, but also means they can
provide a more explicit error message for the user as to what should be
passed.
This is a first step to help solving Issue 9.
|
|
|
|
|
| |
This adds some very free-form comments to note where the reading comes from
and to convert the flags into something that the user can use.
|
|
|
|
|
|
|
|
| |
This is the first (draft) version of the driver, that only downloads the
automatic sensor readings, marking them as (Sensor) in the comments.
I'll follow up with downloading of the scans and blood tests, but wanted to
have this pushed first.
|
| |
|
|
|
|
|
|
|
|
|
| |
Opening the device with read+write permissions is necessary to send write10 SCSI
commands. The error message I was receiving was "SG_IO ioctl error; Operation
not permitted" when running as non-root.
http://sg.danny.cz/sg/sg_io.html describes SCSI permissions in greater depth and
helped illuminate the nature of the permissions problem.
|
|
|
|
| |
This avoids creating a binary file when running the tool as root (bad Flameeyes).
|
|
|
|
|
|
|
|
|
|
| |
This is based off the fsprecisionneo driver, as the two share an almost
identical protocol. The readings format is different between them, but
otherwise the commands are compatible.
There are a number of higher-level commands that differ between them,
though, so it might be necessary to specialize the drivers further in the
future.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
There are shared commands that allow settings the date and time of the
device, implement those in the freestyle support module, so that they can
be re-used in implementation of the same base protocol.
|
| |
|
|
|
|
|
| |
This driver uses the HID-based protocol which is shared among different
devices.
|
|
|
|
|
| |
The number of freestyle devices drivers will soon skyrocket, use the same
shortening as the OneTouch ones.
|
|
|
|
|
| |
This makes it easier to figure out which files represent drivers, and which
ones are per-vendor support modules.
|
| |
|
|
|
|
|
|
| |
This matches the gdef MeterInfo message, and produces a similar (though not
identical) string as before. Importantly, it allows providing semantic
information.
|
| |
|
|
|
|
|
| |
Since there is no way to expose non-glucose readings right now (I might
work on that in the future), filter β-ketones results out from the dump.
|
|
|
|
| |
Not sure how this ever worked.
|
| |
|
|
|
|
|
| |
This driver supports SD Codefree readers, that are sold in the UK by
HomeHealth UK.
|
| |
|
|
|
|
|
| |
I managed to get my hands on an US-edition of the device, and I can confirm
this behaves in a similar way to the otultraeasy.
|
| |
|
|
|
|
|
| |
Most glucometers have *some* sort of checksum, so there is no reason to
implement this on a per-driver basis.
|
|
|
|
|
|
|
|
|
| |
The default USB connection provides a USB storage device with a CSV
datafile. This driver works by looking for that file and importing it.
This does not support setting the time, nor reading the actual device
time, but it is at least a good way to import data from different meters
under the same format.
|
|
|
|
| |
This will lead the way to providing meal information with future drivers.
|
|
|
|
|
|
|
|
| |
This should be working for OneTouch Select Plus devices, too. It currently
does not support reporting in the native unit of the device.
As of today, you'll also need my forked repository of python-scsi, as the
current upstream one does not have working SGIO for Linux.
|
| |
|
|
|
|
|
| |
Also make the exception more general, so that it can be used in the
verio2015 driver.
|
|
|
|
|
| |
The same CRC-CCITT function is used in Verio 2015 devices, so prepare to
reuse it by moving it to the common module.
|
|
|
|
| |
Also update copyright year.
|
|
|
|
|
| |
This should ensure more integrity of the results, and matches the behaviour
on the lifescan devices.
|
|
|
|
|
| |
This driver supports dumping of (glucose) readings and reading/setting the
clock.
|
|
|
|
| |
It seems like the device is very sensible to the reset command.
|
|
|
|
|
| |
The function is not shared with the Ultra Easy and likely not with
other devices either.
|
|
|
|
|
| |
The driver is fully functional but requires proper documentation and
testing.
|
|
|
|
| |
The otultraeasy does not provide comments or meal indications.
|
|
|
|
|
| |
The otultraeasy requires explicit connect/disconnect so implementing
this before is helpful.
|
| |
|
|
|
|
|
| |
This changes the dump output for otultra2 devices as they would dump data in
record format, last reading first.
|
|
|
|
|
|
| |
While mmol/L is the international standard unit, at least LifeScan uses mg/dL in
all their devices, and since they are the ones for which we have protocols for,
we might as well use the same.
|
|
|
|
|
| |
While not all readers implement before/after meal notes, it's possible
to implement an heuristics for that.
|
|
|
|
|
| |
Idea by Jim Sifferle, implemented in a slightly different way as I
noticed I forgot to quote it properly.
|
|
|
|
|
| |
If any exception is thrown by the library, print an error statement and return a
non-zero exit value.
|
|
|
|
| |
This allows to get the serial number, as well as other details about the glucometer once it's installed.
|
| |
|
|
|
|
| |
This also dumps the comment with the dump command.
|
|
|
|
|
| |
The Reading object will be extended to cater for flags, comments and
other device-specific information.
|
|
|
|
|
| |
There is no reason for me to use GPLv3 now that I'm not using the
CRC32-Sick code, so I'll go with the most liberal license out there.
|
|
|
|
|
|
|
| |
Unlike what I though, OneTouch2 does not use CRC32 Sick algorithm, but
a very stupid full 16-bit modulo sum of the bytes in the reply.
This is very simple and does not require GPLv3 code at all.
|
|
|
|
|
|
|
| |
This introduced some changes in the Exception class to simplify the
code, and at the same time it adds a module for multiple lifescan
drivers to share code (multiple OneTouch protocols share the same
checksum for instance).
|
| |
|
| |
|
| |
|
|
|