These can be extracted from the vendor's Windows drivers using a tool
from our 'sigrok-util' repository/project.
- - nexus-osciprime: The Nexus Computing OsciPrime PC oscilloscope needs
- firmware files. These are available from the vendor website.
+ - saleae-logic16: The Saleae Logic16 needs a firmware file for the
+ Cypress FX2 chip in the device, as well as two FPGA bitstream files.
+ These can be extracted from the vendor's Linux application using a tool
+ from our 'sigrok-util' repository/project.
The following drivers/devices do not need any firmware upload:
- agilent-dmm
- alsa
- brymen-dmm
+ - cem-dt-885x
+ - center-3xx
- chronovu-la8
- colead-slm
- demo
- fluke-dmm
+ - ikalogic-scanalogic2
+ - ikalogic-scanaplus
+ - kecheng-kc-330b
- lascar-el-usb
- link-mso19
- mic-985xx
+ - norma-dmm
- openbench-logic-sniffer
- - rigol-ds1xx2
+ - rigol-ds
- serial-dmm
+ - teleinfo
- tondaj-sl-814
- uni-t-dmm
+ - uni-t-ut32x
- victor-dmm
- zeroplus-logic-cube
- agilent-dmm
- brymen-dmm
+ - cem-dt-885x
+ - center-3xx
- colead-slm
- fluke-dmm
- link-mso19
- mic-985xx
- - nexus-osciprime
+ - norma-dmm
- openbench-logic-sniffer
- serial-dmm
+ - teleinfo
- tondaj-sl-814
The following drivers/devices do not require a serial port specification:
- demo
- fx2lafw
- hantek-dso
+ - ikalogic-scanalogic2
+ - ikalogic-scanaplus
+ - kecheng-kc-330b
- lascar-el-usb
- - rigol-ds1xx2
+ - rigol-ds
+ - saleae-logic16
- uni-t-dmm
+ - uni-t-ut32x
- victor-dmm
- zeroplus-logic-cube
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
done
+Enabling multimeter / data logger measurement output
+----------------------------------------------------
+
+Some multimeters or data loggers will not start outputting measurement data
+unless a certain action has been performed by the user beforehand. This is
+usually mentioned in the vendor manual of the respective device, but here's
+a short list for convenience:
+
+ - Digitek DT4000ZC: Briefly press the "RS232" button.
+ - PCE PCE-DM32: Briefly press the "RS232" button.
+ - RadioShack 22-812: Press and hold "SELECT" and "RANGE" together.
+ - TekPower TP4000ZC: Briefly press the "RS232" button.
+ - UNI-T UT61C: Press the "REL/RS232/USB" button for roughly 1 second.
+ - UNI-T UT61D: Press the "REL/RS232/USB" button for roughly 1 second.
+ - UNI-T UT325: Briefly press the "SEND" button (as per manual). However, it
+ appears that in practice you don't have to press the button (at least on
+ some versions of the device), simply connect the device via USB.
+ - V&A VA18B: Keep the "Hz/DUTY" key pressed while powering on the device.
+ - Victor 70C: Press the "REL/RS232" button for roughly 1 second.
+ - Victor 86C: Press the "REL/RS232" button for roughly 1 second.
+ - Voltcraft VC-830: Press the "REL/PC" button for roughly 2 seconds.
+
+
ALSA driver
-----------
$ sigrok-cli --driver ols:conn=/dev/ttyACM0 ...
-Rigol DS1xx2 oscilloscopes
---------------------------
+Rigol DS oscilloscopes
+----------------------
-The 'rigol-ds1xx2' driver (for the Rigol DS1052E and some other, similar DSOs)
-currently uses the Linux usbtmc kernel driver. This means it can currently
-only be built and used on Linux (i.e., it's non-portable).
+The 'rigol-ds' driver (for the Rigol DS series DSOs) currently uses the Linux
+usbtmc kernel driver. This means it can currently only be built and used on
+Linux (i.e., it's non-portable).
The use of a kernel module also means it is dependent on the kernel version
used, as well as on whether this specific module is available in the kernel.
We plan to change the driver to use the 'librevisa' user-space shared
library (which uses libusb) soon, which will fix all these issues and make
the driver portable at the same time.
-
projects / libsigrok.git / blobdiff