Please show example usage

[viq]

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

[vokimon]

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]

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]

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.

[vokimon]

cool, nice commit

[Flameeyes]

I should have referenced thiss issue with 971de801e08de42b63a834744587803e5b391136.

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

[Flameeyes]

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