1 -------------------------------------------------------------------------------
3 -------------------------------------------------------------------------------
5 This README contains various notes for users of libsigrok (or frontends
6 that are based on libsigrok) about device- and/or driver-specific issues.
12 Some devices supported by libsigrok need a firmware to be uploaded every time
13 the device is connected to the PC (usually via USB), before it can be used.
15 The default locations where libsigrok expects the firmware files are:
17 $SIGROK_FIRMWARE_DIR (environment variable)
18 $HOME/.local/share/sigrok-firmware
19 $prefix/share/sigrok-firmware
20 /usr/local/share/sigrok-firmware
21 /usr/share/sigrok-firmware
23 ($prefix is usually /usr/local or /usr, depending on your ./configure options)
25 For further information see the section below and also:
27 http://sigrok.org/wiki/Firmware
30 Per-driver firmware requirements
31 --------------------------------
33 The following drivers/devices require a firmware upload upon connection:
35 - asix-omega-rtm-cli: There is no native sigrok support for ASIX OMEGA
36 devices. But the vendor's RTM CLI application can be used in streaming
37 mode, which transparently handles the device detection and firmware
38 download. The firmware ships with the vendor application. See below
39 for details how to make the vendor application available to the sigrok
42 - asix-sigma: The ASIX SIGMA and SIGMA2 require various firmware files,
43 depending on the settings used. These files are available from our
44 'sigrok-firmware' repository/project under a license which allows us
47 - dreamsourcelab-dslogic: The DreamSourceLab DSLogic/DSCope device series
48 requires various firmware files and FPGA bitstream files.
49 These can be extracted/downloaded from the vendor's GitHub repo using a
50 tool from our 'sigrok-util' repository/project.
52 - fx2lafw: Logic analyzers based on the Cypress FX2(LP) chip need the
53 firmware files from the 'sigrok-firmware-fx2lafw' repository/project.
54 The firmware is written from scratch and licensed under the GNU GPLv2+.
56 - hantek-6xxx: Certain oscilloscopes based on the Cypress FX2(LP) chip, such
57 as the Hantek 6022BE/6022BL, SainSmart DDS120, and Rocktech BM102, need the
58 firmware files from the 'sigrok-firmware-fx2lafw' repository/project.
59 The firmware is written from scratch and licensed under the GNU GPLv2+.
61 - hantek-dso: The Hantek DSO-2090 (and other supported models of the same
62 series of Hantek PC oscilloscopes) need firmware files.
63 These can be extracted from the vendor's Windows drivers using a tool
64 from our 'sigrok-util' repository/project.
66 - kingst-la2016: The Kingst LA series of logic analyzers needs MCU firmware
67 and FPGA netlists. The 'sigrok-util' repository contains a script to
68 extract these files from the vendor software.
70 - lecroy-logicstudio: The LeCroy LogicStudio requires FPGA bitstream files.
71 These can be extracted from the vendor's Windows software using a tool
72 from our 'sigrok-util' repository/project.
73 Additionally, it requires a Cypress FX2 firmware. This can be extracted
74 from the vendor's Windows software using another tool. Details:
76 http://sigrok.org/wiki/LeCroy_LogicStudio#Firmware
78 - saleae-logic16: The Saleae Logic16 needs a firmware file for the
79 Cypress FX2 chip in the device, as well as two FPGA bitstream files.
80 These can be extracted from the vendor's Linux application using a tool
81 from our 'sigrok-util' repository/project.
83 - saleae-logic-pro: The Saleae Logic Pro 16 needs a firmware file for the
84 Cypress FX3 chip in the device, as well as an FPGA bitstream file.
85 These can be extracted from the vendor's Linux application using a tool
86 from our 'sigrok-util' repository/project.
90 - The Sysclk LWLA1034 requires various bitstream files.
91 These files are available from our 'sigrok-firmware' repository/project
92 under a license which allows us to redistribute them.
94 - The Sysclk LWLA1016 requires various bitstream files.
95 These can be extracted from the vendor's Windows drivers using a tool
96 from our 'sigrok-util' repository/project.
98 - sysclk-sla5032: The Sysclk SLA5032 needs an FPGA bitstream file.
99 This file can be copied (and renamed) from the Windows vendor software
100 installation directory. Details:
102 https://sigrok.org/wiki/Sysclk_SLA5032#Firmware
104 The following drivers/devices do not need any firmware upload:
108 - arachnid-labs-re-load-pro
113 - center-3xx (including all subdrivers)
121 - gmc-mh-1x-2x (including all subdrivers)
128 - hung-chang-dso-2100
129 - ikalogic-scanalogic2
140 - mic-985xx (including all subdrivers)
145 - openbench-logic-sniffer
151 - rohde-schwarz-sme-0x
154 - serial-dmm (including all subdrivers)
155 - serial-lcr (including all subdrivers)
160 - uni-t-dmm (including all subdrivers)
163 - zeroplus-logic-cube
167 Specifying serial ports
168 -----------------------
170 Many devices supported by libsigrok use serial port based cables (real RS232
171 or USB-to-serial ones, CDC class) to connect to a PC. These serial cables are
172 supported by the libserialport library. Some vendors prefer to use HID chips
173 instead of CDC chips in their serial cables. These cables can get supported
174 by means of the hidapi library. Note that each chip type requires specific
175 support in the libsigrok library. Bluetooth connected devices may be supported
176 as well when they communicate by means of RFCOMM channels, or one of the
177 implemented BLE notification/indication approaches, and one of the Bluetooth
178 supporting platforms is used.
180 For all these devices, you need to specify the serial port they are connected
181 to (e.g. using the 'conn' option in sigrok-cli). It is not possible to scan
182 for such devices without specifying a serial port.
186 $ sigrok-cli --driver <somedriver>:conn=/dev/ttyUSB0 ...
187 $ sigrok-cli --driver <somedriver>:conn=hid/cp2110 ...
188 $ sigrok-cli --driver <somedriver>:conn=bt/rfcomm/01-23-45-67-89-ab ...
190 Formal syntax for serial communication:
192 - COM ports (RS232, USB CDC):
196 conn=hid[/<chip>]/usb=<bus>.<dev>[.<if>]
197 conn=hid[/<chip>]/raw=<path>
198 conn=hid[/<chip>]/sn=<serno>
199 conn=hid[/<chip>]/iokit=<path>
200 chip can be: bu86x, ch9325, cp2110, victor
201 path may contain slashes
202 path and serno are "greedy" (span to the end of the spec)
203 - Bluetooth Classic and Bluetooth Low Energy (BLE):
204 conn=bt/<conn>/<addr>
205 conn can be: rfcomm, ble122, nrf51, cc254x
206 addr can be "dense" or separated, bt/cc254x/0123456789ab or
207 bt/rfcomm/11-22-33-44-55-66 or bt/ble122/88:6b:12:34:56:78
208 (note that colons may not be available when the conn= spec is taken
209 from a string that separates fields by colon, e.g. in the "--driver
210 <name>:conn=<spec>" example, that is why the dense form and the use
211 of dashes for separation are supported)
213 Some of the drivers implement a default for the connection. Some of the
214 drivers can auto-detect USB connected devices.
216 Beyond strict serial communication over COM ports (discussed above), the
217 conn= property can also address specific USB devices, as well as specify TCP
218 or VXI communication parameters. See these examples:
220 $ sigrok-cli --driver <somedriver>:conn=<vid>.<pid> ...
221 $ sigrok-cli --driver <somedriver>:conn=tcp-raw/<ipaddr>/<port> ...
222 $ sigrok-cli --driver <somedriver>:conn=vxi/<ipaddr> ...
223 $ sigrok-cli --driver <somedriver>:conn=usbtmc/<bus>.<addr> ...
225 Individual device drivers _may_ implement additional semantics for the
226 conn= specification, which would not apply to other drivers, yet can be
227 rather useful for a given type of device.
229 $ sigrok-cli --driver <somedriver>:conn=sn=<serno>
232 Specifying serial port parameters
233 ---------------------------------
235 Every serial device's driver has default serial port parameters like baud
236 rate, number of data bits, stop bits and handshake status. If a device requires
237 different parameters, pass them as option "serialcomm" with the driver name.
238 See libsigrok docs for the function serial_set_paramstr() for complete specs.
242 $ sigrok-cli --driver <somedriver>:conn=<someconn>:serialcomm=9600/7n1/dtr=1
245 Permissions of serial port based devices
246 ----------------------------------------
248 When using devices supported by libsigrok that use serial port based cables
249 (real RS232 or USB-to-serial ones) to connect to a PC, you need to ensure
250 that the user running the libsigrok frontend has (read/write) permissions to
251 access the serial port device (e.g. /dev/ttyS0, /dev/ttyUSB0, and so on).
253 You can use 'chmod' to apply permissions as you see fit, and/or 'chown' to
254 change the owner of the serial port device to a certain user or group.
256 For USB-to-serial based devices, we recommended using our udev rules file
257 (see below for details).
260 Permissions for USB devices (udev rules files)
261 ----------------------------------------------
263 When using USB-based devices supported by libsigrok, the user running the
264 libsigrok frontend (e.g. sigrok-cli) has to have (read/write) permissions
265 for the respective USB device.
267 On Linux, this is accomplished using udev rules. libsigrok ships a rules
268 file containing all supported devices which can be detected reliably
269 (generic USB-to-serial converters are omitted, as these are used for a wide
270 range of devices, e.g. GPS receivers, which are not handled by libsigrok).
272 The file is available in contrib/60-libsigrok.rules. This file just contains
273 the list of devices and flags these devices with ID_SIGROK="1". Access is
274 granted by the 61-libsigrok-plugdev.rules or 61-libsigrok-uaccess.rules files,
275 allowing access to members of the plugdev group or to currently logged in
278 When using a libsigrok package from your favorite Linux distribution, the
279 files should already be installed in /usr/lib/udev/rules.d/, i.e.
280 60-libsigrok.rules and one of the access granting rules files. Use of
281 61-libsigrok-uaccess.rules is encouraged on systemd distributions.
283 The access policy can be locally overridden by placing appropriate rules in
284 /etc/udev/rules.d/, disabling or ammending the default policy. See the
285 udev documentation, e.g. man 7 udev, for details.
287 If you're building from source, you need to copy the file to the place
288 where udev will read these rules. Local rules should go to /etc/udev/rules.d.
289 Keep the file naming, otherwise interaction between the libsigrok rules and
290 rules shipped by the system will be broken.
292 Please consult the udev docs for details.
295 Assigning drivers to devices (Windows, Zadig)
296 ---------------------------------------------
298 On Windows systems it may be necessary to assign drivers to devices
299 before libusb based applications can access them. It may be necessary
300 to re-run this driver assignment after firmware upload in case the
301 device changes its USB identification as a consequence of loading the
304 The https://sigrok.org/wiki/Windows wiki page discusses this subject,
305 and other platform specific aspects.
308 Non-default drivers for commodity chips
309 ---------------------------------------
311 Some vendors include common USB chips in their products yet assign device
312 specific VID:PID pairs. Which results in the necessity for extra steps
313 before the serial port can be used:
315 - GW Instek VCP, found in GDM-8000 and probably other meters: Install the
316 vendors Windows driver to get access to a COM port. Or force the driver
319 # echo 2184 0030 > /sys/bus/usb-serial/drivers/cp210x/new_id
322 Cypress FX2 based devices
323 -------------------------
325 Devices using the Cypress FX2(LP) chip without any specific USB VID/PID will
326 be enumerated with VID/PID 04b4:8613 (the default for "unconfigured FX2").
327 These are usually "FX2 eval boards" (that can also be used as LAs, though).
329 On Linux, the 'usbtest' driver will usually grab such devices, and they will
330 thus not be usable by libsigrok (and frontends).
332 You can fix this by running 'rmmod usbtest' as root before using the device.
335 UNI-T DMM (and rebranded models) cables
336 ---------------------------------------
338 UNI-T multimeters (and rebranded devices, e.g. some Voltcraft models) can
339 ship with different PC connectivity cables:
341 - UT-D02 (RS232 cable)
342 - UT-D04 (USB/HID cable with Hoitek HE2325U chip, USB VID/PID 04fa:2490)
343 - UT-D04 (USB/HID cable with WCH CH9325 chip, USB VID/PID 1a86:e008)
344 - UT-D07 (Bluetooth adapter, ISSC BL79 BLETR chip)
345 - UT-D09 (USB/HID cable with SiL CP2110 chip, USB VID/PID 10c4:ea80)
347 The above cables are all physically compatible (same IR connector shape)
348 with all/most currently known UNI-T multimeters. For example, you can
349 use either of the UT-D04 USB/HID cables or the UT-D02 RS232 cable with
350 the UNI-T UT61D multimeter.
352 When using the UT-D02 RS232 cable with any of the supported UNI-T DMMs,
353 you have to use the respective driver with a '-ser' drivername suffix
354 (internally all of these models are handled by the 'serial-dmm' driver).
356 You also need to specify the serial port via the 'conn' option, e.g.
357 /dev/ttyUSB0 (attached via a USB-to-serial cable) or /dev/ttyS0 (actual
358 RS232 port) on Linux (see above).
360 Finally, the user running the frontend (e.g. sigrok-cli) also needs
361 permissions to access the respective serial port (see above).
363 Examples (sigrok-cli):
365 $ sigrok-cli --driver uni-t-ut61e-ser:conn=/dev/ttyUSB0 ...
366 $ sigrok-cli --driver voltcraft-vc820-ser:conn=/dev/ttyS0 ...
367 $ sigrok-cli --driver uni-t-ut61e-ser:conn=hid/cp2110
369 Using any of the UT-D04 et al USB/HID cables can be done in two different
370 ways: Use transparent serial over HID support in libsigrok, by giving the
371 -ser driver a conn=hid/... serial port spec. This re-uses the 'serial-dmm'
372 driver, results in better coverage of these code paths, and reduces
373 maintenance overhead. Or by running non-ser drivers and passing USB
374 specific connection details. When the driver _without_ the '-ser' suffix
375 is used, the models are handled by the 'uni-t-dmm' driver. These duplicate
376 drivers only exist for historical reasons, the redundancy may result in
377 differences of behaviour between the two implementations. When in doubt,
378 check if the '-ser' driver works for you.
380 In the USB specific driver case you need to specify the cable's vendor
381 and product IDs. Autodetection is not possible here, since various other
382 products use the USB VID/PID of those cables too, and there is no way to
383 distinguish them. The sigrok software errs on the safe side, and won't
384 communicate to serial ports unless explicitly instructed by the user.
386 The user running the frontend does also need to have permissions to
387 access the respective USB device (see above).
389 Examples (sigrok-cli):
391 $ sigrok-cli --driver uni-t-ut61e:conn=1a86.e008 ...
392 $ sigrok-cli --driver voltcraft-vc820:conn=04fa.2490 ...
395 UNI-T UT-D04 cable issue on Linux
396 ---------------------------------
398 The UNI-T UT-D04 cable with Hoitek HE2325U (or WCH CH9325) chip seems to have
399 a very specific problem on Linux. Apparently it requires to be put into
400 suspend (and woken up again) before it is usable. This seems to be a
401 Linux-only issue, Windows is not affected by this since apparently the
402 Windows kernel does this for every USB device, always.
404 Thus, if you want to use any of the UNI-T DMMs with this specific cable,
405 you'll have to run the following script (as root) once, every time you attach
406 the cable via USB. The script was written by Ralf Burger.
408 See also: http://erste.de/UT61/index.html
411 for dat in /sys/bus/usb/devices/*; do
412 if test -e $dat/manufacturer; then
413 grep "WCH.CN" $dat/manufacturer > /dev/null && echo auto > ${dat}/power/level && echo 0 > ${dat}/power/autosuspend
418 UNI-T UT-D04 cable issue on Windows
419 -----------------------------------
421 There have been reports that CH9325 based cables are not detected on
422 Windows out of the box when they are assigned to libwdi drivers. Though
423 they may be usable in that case when the USB address is manually specified.
424 This can happen when some "USB to serial" driver is assigned which does not
425 provide a genuine COM port that enumerates naturally. Manually assigning a
426 "USB input device" driver can improve HIDAPI compatibility and make the
427 cable show up in sigrok's serial port enumeration.
430 Enabling multimeter / data logger measurement output
431 ----------------------------------------------------
433 Some multimeters or data loggers will not start outputting measurement data
434 unless a certain action has been performed by the user beforehand. This is
435 usually mentioned in the vendor manual of the respective device, but here's
436 a short list for convenience:
438 - BBC Goertz Metrawatt M2110: Briefly press the "Start/Reset" button on the
439 interface panel on top.
440 - Brymen BM257s: Press HOLD during power-on.
441 - Digitek DT4000ZC: Briefly press the "RS232" button.
442 - EEVBlog 121GW: Hold "1ms PEAK" until the "BT" indicator is shown.
443 - ES51919 based LCR meters (DER EE DE-5000, PeakTech 2170, UNI-T UT612):
444 Press the button with the "RS232" or "USB" or "PC link" label (usually
445 the "up" cursor button).
446 - Gossen Metrawatt Metrahit 1x/2x devices, driver gmc-mh-1x-2x-rs232:
447 - Power on the device with the "DATA" button pressed.
448 - Metrahit 2x devices must be configured for the respective interface type.
449 - Gossen Metrawatt Metrahit 2x devices, driver gmc-mh-2x-bd232:
451 The multimeter must be configured for the respective interface type.
452 - 'SI232-II' interface ("PC Mode"):
453 The multimeter must be configured for interface type 'BD232' (all),
454 'SI232 online' (28-29S) or 'SI232 store' (22-26x). The interface must
455 be configured to the same baud rate as the host (default 9600).
456 Multimeter and interface must be configured to the same address.
457 - GW Instek GDM-397: Press the "REL/RS232C (USB)" button for roughly 1 second.
458 - GW Instek VCP: See the discussion on manual driver assignment to common
459 USB to UART chips with non-default USB identification.
460 - MASTECH MS6514: Press the "Setup/PC-Link" button for roughly 3 seconds.
461 - Meterman 38XR: Press the "RS232" button.
462 - Metrix MX56C: Press the PRINT button to have the meter send acquisition
463 data via IR. Hold the PRINT button to adjust the meter's transmission
465 - Norma DM950: If the interface doesn't work (e.g. USB-RS232 converter), power
466 on the device with "FUNC" pressed (to power the interface from the DMM).
467 - PCE PCE-DM32: Briefly press the "RS232" button.
468 - RadioShack 22-812: Press and hold "SELECT" and "RANGE" together.
469 - TekPower TP4000ZC: Briefly press the "RS232" button.
470 - Tenma 72-7750: Briefly press the "RS232C" button.
471 - UNI-T UT60G: Briefly press the "RS232C" button.
472 - UNI-T UT61B/C/D: Press the "REL/RS232/USB" button for roughly 1 second.
473 - UNI-T UT71x: Press the "SEND/-/MAXMIN" button for roughly 1 second.
474 Briefly pressing the "EXIT" button leaves this mode again.
475 - UNI-T UT181A: In the "SETUP" menu set "Communication" to "ON".
476 - UNI-T UT325: Briefly press the "SEND" button (as per manual). However, it
477 appears that in practice you don't have to press the button (at least on
478 some versions of the device), simply connect the device via USB.
479 - V&A VA18B/VA40B: Keep the "Hz/DUTY" key pressed while powering on the DMM.
480 - Victor 70C/86C: Press the "REL/RS232" button for roughly 1 second.
481 - Voltcraft VC-830: Press the "REL/PC" button for roughly 2 seconds.
482 - Voltcraft VC-870: Press the "REL/PC" button for roughly 1 second.
485 ASIX OMEGA in RTM CLI mode
486 --------------------------
488 The asix-sigma driver can detect the Omega devices' presence, but does
489 not support their protocol and emits a diagnostics message. The firmware
490 image is not available for distribution, and information on the protocol
491 is not available. That's why native support is in some distant future.
492 Yet basic operation of Omega devices is available by using the vendor's
493 command line application for real time mode (RTM CLI).
495 The vendor application targets Windows (on x86), but also executes on
496 Linux when 32bit libraries for FTDI communication are provided. The
497 user manual discusses the installation. The sigrok asix-omega-rtm-cli
498 driver uses the vendor provided omegartmcli.exe binary to configure the
499 device for streaming, and to acquire sample data.
501 Either make an "omegartmcli" executable available in PATH. This can be
502 the vendor's executable or some wrapper around it or a symlink to it.
503 Or specify the executable's location in the OMEGARTMCLI environment
504 variable. The sigrok driver accepts an optional serial number (six or
505 eight hex digits) to select one out of several connected devices.
508 $ export "OMEGARTMCLI=$HOME/.wine/drive_c/progx86/ASIX/SIGMA/omegartmcli.exe"
511 $ OMEGASN=":conn=sn=a6030123"
514 $ sigrok-cli -d asix-omega-rtm-cli${OMEGASN} --show
515 $ sigrok-cli -d asix-omega-rtm-cli${OMEGASN} -o capture.sr --time 10s
516 $ sigrok-cli -d asix-omega-rtm-cli${OMEGASN} -o capture.sr --samples 100m
517 $ pulseview -d asix-omega-rtm-cli${OMEGASN}
519 The RTM mode of operation samples 16 channels at a fixed rate of 200MHz.
520 Hardware triggers are not available in this mode. Glib should handle
521 platform specific details of external process execution, but the driver
522 was only tested on Linux so far. Acquisition start in sigrok applications
523 may take some time before sample data becomes available (roughly one
524 second here on a slow machine). This is an implementation detail of the
525 RTM CLI approach including execution under wine.
527 The reliability of that setup in the presence of fast changing input
528 signals is yet to get determined. It's assumed that slow input signals
529 are operational. It's essential that the _average_ rate of changes in
530 the input signal in combination with the hardware compression are such
531 that the FTDI FIFO can communicate all involved data via USB2.0 to the
532 application. Intermediate bursts of rapid changes shall not be an issue
533 given the Omega devices' deep memory which RTM uses for buffering.
535 Native support for the Asix Omega devices depends on the availability of
536 a protocol description and use of the protocol depends on the firmware's
537 availability at the user's site. Which then would allow to capture to
538 DRAM at high rates without the communication bottleneck, before the data
539 gets communicated to the PC after the acquisition has completed. Compare
540 the native sigrok support for Asix Sigma.
543 ChronoVu LA8/LA16 USB VID/PIDs
544 ------------------------------
546 The ChronoVu LA8/LA16 logic analyzer is available in two revisions. Previously,
547 the device shipped with a USB VID/PID of 0403:6001, which is the standard ID
548 for FTDI FT232 USB chips.
550 Since this made it hard to distinguish the LA8/LA16 from any other device
551 with this FTDI chip connected to the PC, the vendor later shipped the
552 device with a USB VID/PID of 0403:8867.
554 The 'chronovu-la' driver in libsigrok supports both VID/PID pairs and
555 automatically finds devices with either VID/PID pair.
561 The Dangerous Prototypes Openbench Logic Sniffer (OLS) logic analyzer
562 driver in libsigrok assumes a somewhat recent firmware has been flashed onto
563 the OLS (it doesn't need a firmware upload every time it's attached via USB,
564 since the firmware is stored in the device permanently).
566 The most recent firmware version that is tested is 3.07.
568 If you use any older firmware and your OLS is not found or is not working
569 properly, please upgrade to at least this firmware version. Check the
570 Dangerous Prototypes wiki for firmware upgrade instructions:
572 http://dangerousprototypes.com/docs/Logic_Sniffer_upgrade_procedure
574 Also, you need to specify a serial port for the OLS in the frontends, e.g.
575 using the 'conn' option in sigrok-cli, and you also need to have the
576 permissions to access the serial port (see above).
580 $ sigrok-cli --driver ols:conn=/dev/ttyACM0 ...
586 The Grand Idea Studio JTAGulator also implements the SUMP protocol and
587 thus is covered by the OLS driver. See the vendor's wiki on details how
588 to enable the Logic Analyzer mode of operation.
590 https://github.com/grandideastudio/jtagulator/wiki/Logic-Analyzer
596 The Mooshim Engineering Mooshimeter is controlled via Bluetooth Low Energy
597 (sometimes called Bluetooth 4.0), as such it requires a supported Bluetooth
598 interface available. The 'conn' option is required and must contain the
599 Bluetooth MAC address of the meter.
603 $ sigrok-cli --driver mooshimeter-dmm:conn=12-34-56-78-9A-BC ...
605 Since the Mooshimeter has no physical interface on the meter itself, the
606 channel configuration is set with the 'channel_config' option. The format
607 of this option is 'CH1,CH2' where each channel configuration has the form
608 'MODE:RANGE:ANALYSIS', with later parts being optional. In addition for
609 CLI compatibility, the ',' in the channels can also be a '/' and the ':' in
610 the individual configuration can be a ';'.
612 Available channel 1 modes:
614 - Current, A: Current in amps
615 - Temperature, T, K: Internal meter temperature in Kelvin
616 - Resistance, Ohm, W: Resistance in ohms
617 - Diode, D: Diode voltage
618 - Aux, LV: Auxiliary (W input) low voltage sensor (1.2V max)
620 Available channel 2 modes:
622 - Voltage, V: Voltage
623 - Temperature, T, K: Internal meter temperature in Kelvin
624 - Resistance, Ohm, W: Resistance in ohms
625 - Diode, D: Diode voltage
626 - Aux, LV: Auxiliary (W input) low voltage sensor (1.2V max)
628 Only one channel can use the shared inputs at a time (e.g. if CH1 is measuring
629 resistance, CH2 cannot measure low voltage). Temperature is excepted from
630 this, so the meter can measure internal temperature and low voltage at the
633 Additionally, the meter can calculate the real power of both channels. This
634 generally only makes sense when CH1 is set to current and CH2 is set to a
635 voltage and so it is disabled by default. It must be enabled by enabling the
636 'P' channel (the third channel).
638 The range of the channel specification sets the maximum input for that channel
639 and is rounded up to the next value the meter itself supports. For example,
640 specifying 50 for the voltage will result in the actual maximum of 60.
641 Specifying 61 would result in 600. If omitted, sigrok will perform
642 auto-ranging of the channel by selecting the next greater value than the
645 The analysis option sets how the meter reports its internal sampling buffer
648 - Mean, DC: The default is a simple arithmetic mean of the sample buffer
649 - RMS, AC: The root mean square of the sample buffer
650 - Buf, Buffer, Samples: Report the entire sample buffer to sigrok. This
651 results in packets that contain all the samples in the buffer instead
652 of a single output value.
654 The size of the sample buffer is set with the 'avg_samples' option, while
655 the sampling rate is set with the 'samplerate' option. So the update rate
656 is avg_samples/samplerate. Both are rounded up to the next supported value
661 $ sigrok-cli -c channel_config="Aux;0.1/T" --driver mooshimeter-dmm...
662 $ sigrok-cli -c channel_config="A;;AC/V;;AC" --driver mooshimeter-dmm...