| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
This removes the wholly complicated _Packet() object and replace it with
more readable construct.
Unfortunately this appears to reduce performance because of the serial
stream buffering, needed to calculate the checksum. It's unfortunate, but
it at least avoids a significant amount of custom code.
|
| |
|
|
|
|
|
| |
This replaces the use of manual structures with well-defined construct
entries; it also give consistency to packet vs message.
Log input and output messages, to be clearer.
|
| |
|
|
|
|
|
|
| |
This simplifies the code and enforces the validation within the format
documentation too.
construct can handle the full package verification, including dealing with
padding.
|
| |
|
|
|
|
|
|
| |
This should address Issue 5 (theoretically some of the dependencies are
OS-specific but that's a longer problem).
Also partially addresses Issue 9 because now we have an easy to understand
"install and try out" option.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
| |
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 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.
|
| |
|
|
|
|
|
|
|
|
| |
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 driver supports SD Codefree readers, that are sold in the UK by
HomeHealth UK.
|
| |
|
|
|
|
|
|
|
| |
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 should provide more information on the devices themselves,
particularly now that different levels of features are available.
|
| |
|
|
|
|
|
|
| |
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 update copyright year.
|
| | |
|
| |
|
|
|
| |
The driver is fully functional but requires proper documentation and
testing.
|
| | |
|
| |
|
|
|
| |
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.
|
| | |
|
| |
|
