| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
This in turn allows wrapping the FreeStyle access in its own session class,
which the freestyle_hid_console can use without dirty tricks, and without
triggering the now-abstract class.
|
| |
|
|
|
|
|
|
|
|
|
| |
The f-strings formatted strings are generally simpler to write, read and
debug, with a few exceptions.
Keep the logging strings lazy, keep the CSV-building with %-formatting, as
it makes it more readable.
In fsoptium, keep `'$%s\r\n'` as a %-format, to avoid making it
`f'${command}\r\n'` that would make it easy to mistake for a Shell variable.
|
| | |
|
| |
|
|
|
|
|
| |
Message type 0x22 is a keepalive message, which has usually one 0x05 or
0x03 byte. But don't expect a certain value, just ignore the message.
This fixes issue #73.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
While the Libre 2 protocol is still not usable, this makes it possible to
at least send messages to it and get a translation of what the mistake was
in the first place.
|
| |
|
|
|
| |
This includes both the classic "unknown message type" error, and the Libre
2 encryption error state.
|
| |
|
|
|
|
| |
This is not a sequence, but rather a single initialization command. Remove
the loop and the long comment that no longer applies (serial numbers and
all.)
|
| |
|
|
|
|
|
|
| |
This has been tested on fslibre and fsprecisionneo, but please report if
this does not work with other FreeStyle devices (Insulinx?)
It appears the 0x04/0x05/0x15 dance is only needed by the Abbott software
to identify which model (and software version) it is talking with.
|
| |
|
|
| |
Since Python 3.4 is no longer supported, there's no reason for typing not to be there.
|
| |
|
|
| |
() is not a valid Iterator[List[Text]]
|
| |
|
|
|
| |
The multi-record format returns "Log Empty" if there's no entry in the
device, catch that.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This was brought up in issue #60. While the devices don't appear to care
much for patient names, and can't be expected to support UTF-8 (the Windows
software don't appear to allow that), it's worth protecting against this
and just replacing the non-ASCII characters.
To make this easier, the decoding is pushed down to the end of the
processing of the multi-packet response, rather than being done per-packet.
|
| |
|
|
|
|
| |
This includes the command line extensions to include the get/set patient
name, as well as the driver support for all FreeStyle devices with the
shared HID protocol, although not all will support this properly.
|
| |
|
|
|
| |
This includes extension of the base info command to report this when asked
on the command line.
|
| |
|
|
|
|
|
|
| |
At least the FreeStyle Precision Neo appears to be able to report an invalid
date/time (255/255/255 255:255), probably when the RTC is lost (see issue #58).
This returns a more precise output than N/A, and should suggest to confirm the
date and time setting instead.
|
| |
|
|
|
|
| |
The FreeStyle Optimum Neo reports ketones in using the same unit as FreeStyle
Libre. Move the conversion function from fslibre.py to freestyle.py to
facilitate sharing and do the right conversion in fsprecisionneo.py.
|
| |
|
|
| |
Also add a test so that we don't break this again in the future.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Most of the epydoc metadata (author, copyright, email) is duplicate in
the package's setup.py or README. These copies are more likely to get out
of date, and increase the amount of work to keep them in line.
The license information should rather be provided with an SPDX identifier,
which is more similar to what the Linux kernel and other projects, such as
pyserial, do.
|
| |
|
|
|
|
|
|
| |
Due to EURid threatening to suspend my domain, make sure that the
references are updated to point at the right stable domain.
This includes changes to the files as well as a mailmap to update the
author references in the log.
|
| |
|
|
| |
Again, this is not ready for CI yet unfortunately :(
|
| | |
|
| |
|
|
|
| |
This cannot currently be added to CI because the lack of `construct` stubs,
which cause "unsupported left operands" for /-constructed structs.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This simplifies the code and enforces the validation within the format
documentation too.
construct can handle the full package verification, including dealing with
padding.
|
| | |
|
| |
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
| |
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 avoids creating a binary file when running the tool as root (bad Flameeyes).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
