Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Please show example usage #9

Open
viq opened this issue Mar 3, 2017 · 6 comments
Open

Please show example usage #9

viq opened this issue Mar 3, 2017 · 6 comments

Comments

@viq
Copy link

viq commented Mar 3, 2017

The main part that's unclear to me is what it expects as <device>
@vokimon
Copy link

vokimon commented Mar 10, 2017 •
edited
Loading

It refers a linux device in /dev/. The trick i used is to run:

# disconnet the device
find /dev > devices-before
# connect the device
find /dev > devices-after
diff devices-before devices-after

This will show you the device files linux has created to support your glucometer (usually more than one). I tried with them until i found that for my device is /dev/hidraw2, but your milleage may vary.

And i agree that some guidelines on which kind of device you should peek for each glucometer would be nice.

@Flameeyes
Copy link
Collaborator

Sorry for the vagueness of the documentation, I'll try providing more details soon. There is another problem, that is at least one of the devices I'm looking at right now does not actually need a device since it uses libusb to access the raw USB device, making the whole --device parameter pointless for it.

FWIW right now it's /dev/hidrawX for all the Abbott meters except the Optium, /dev/ttyUSB{something} for the Optium, the OneTouch Ultra (2 and Mini) and the SD Codefree, and /dev/sdX for the Verio.

@Flameeyes
Copy link
Collaborator

A (late) update on this issue.

Since at least one (probably more) of the devices I"m looking at right now needs to use libusb so it cannot be given a device, so at the very least the device indication needs to become optional, as that driver wouldn't accept one.

So what I would like to have is a way to auto-detect the right HID or Serial device to use. Unfortunately I'm not sure how to do that easily on all operating systems, but I may be able to do that on Linux by default for now.

Flameeyes added a commit that referenced this issue Apr 17, 2017
@Flameeyes
Add support for a "help" action that prints the driver module's docst…
5ef9873 
…ring.

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.
Flameeyes added a commit that referenced this issue Apr 17, 2017
@Flameeyes
All drivers: move documentation of features from README to docstring.
46804ae 
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.
@vokimon
Copy link

vokimon commented Apr 18, 2017 •
edited
Loading

cool, nice commit

@Flameeyes
Copy link
Collaborator

I should have referenced thiss issue with 971de80.

This is a bit better, but not quite enough yet.

@Flameeyes
Copy link
Collaborator

Okay b8aa129 should be cleaner. Please let me know if I should fix something else or this issue can be closed :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Flameeyes @vokimon @viq