Bug 119

Summary:	uni-t-dmm based drivers: scan should only return actually connected/enabled devices as found
Product:	libsigrok	Reporter:	Uwe Hermann <uwe>
Component:	Driver: uni-t-dmm	Assignee:	Uwe Hermann <uwe>
Status:	CONFIRMED ---
Severity:	normal
Priority:	Normal
Version:	unreleased development snapshot
Target Milestone:	---
Hardware:	All
OS:	All

Description Uwe Hermann 2013-05-03 13:50:15 CEST

Currently a scan for devices using the uni-t-dmm driver will return all DMMs which that driver supports as "detected", which is incorrect. The driver cannot know beforehand which DMM is connected to the USB/HID/IR cable. It should only report actually selected and connected devices. E.g. if invoked as "sigrok-cli --scan" is should return an empty list, "sigrok-cli --scan --driver uni-t-ut61d" should return the UT61D only (if the cable is found).

Comment 1 Uwe Hermann 2014-01-06 19:28:00 CET

This issue is partly obsolete, the uni-t-dmm based drivers now require a USB VID/PID to be supplied, and a --scan will no longer return all devices:

  $ sigrok-cli --scan --driver voltcraft-vc820:conn=1a86.e008
  voltcraft-vc820 - Voltcraft VC-820 with 1 probe: P1

However, a minor issue remains. The driver currently reports the device as "found" based on the drivername, regardless of whether it's actually attached via USB and/or enabled at all. That should still be fixed.