- lascar-el-usb
- link-mso19
- mic-985xx
+ - norma-dmm
- openbench-logic-sniffer
- rigol-ds1xx2
- serial-dmm
+ - teleinfo
- tondaj-sl-814
- uni-t-dmm
- uni-t-ut32x
- fluke-dmm
- link-mso19
- mic-985xx
+ - norma-dmm
- openbench-logic-sniffer
- serial-dmm
+ - teleinfo
- tondaj-sl-814
The following drivers/devices do not require a serial port specification:
driver _without_ the '-ser' drivername suffix (internally all of these models
are handled by the 'uni-t-dmm' driver).
+You also need to specify the USB vendor/device IDs of the cable.
+Autodetection is not possible here, since various other products use the
+USB VID/PID of those cables too, and there is no way to distinguish them.
+
Since the UT-D04 cables are USB based (but don't use a USB-to-serial chip)
there is no need to specify a serial port via 'conn', of course.
However, the user running the frontend does also need to have permissions
Examples (sigrok-cli):
- $ sigrok-cli --driver uni-t-ut61e ...
- $ sigrok-cli --driver voltcraft-vc820 ...
+ $ sigrok-cli --driver uni-t-ut61e:conn=1a86.e008 ...
+ $ sigrok-cli --driver voltcraft-vc820:conn=04fa.2490 ...
UNI-T UT-D04 cable issue on Linux