ok, so the installed version of libsigrok is too old and you'll have to use the AppImage for the time being. I'm assuming the device /dev/ttyUSB0 isn't accessible.
Does /dev/ttyUSB0 exist? Is it accessible by your user? You can check dmesg to see what device node is created when you plug in the device. Regards, -Soeren On Tue, 2020-03-24 at 12:25 +0000, Richard Andrews wrote: > > $ sigrok-cli --driver serial-lcr:conn=/dev/ttyUSB0 --scan > Driver serial-lcr not found. > > I tried the appimage and same problems. The program is listing ftdi- > la and not seeing past that to the meter. > > On Tuesday, March 24, 2020, 07:47:09 AM EDT, Soeren Apel < > soe...@apelpie.net> wrote: > > > ok, so it's a serial device, which I forgot to check before. > Serial devices are never discovered by --scan, so the device > node must be specified on the command line. > > https://sigrok.org/wiki/Voltcraft_4080 states the driver is serial- > lcr. > > Looking at https://sigrok.org/wiki/Getting_started_with_a_multimeter > , > I'd try this: > > sigrok-cli --driver serial-lcr:conn=/dev/ttyUSB0 --scan > > Assuming you're on Linux, that is, and the device node is as given. > > Regards > -Soeren > > > On Tue, 2020-03-24 at 11:09 +0000, Richard Andrews wrote: > > Thanks for trying to help. Here's what you asked for. > > > > $ sigrok-cli --version > > sigrok-cli 0.7.0 > > > > Libraries and features: > > - libsigrok 0.5.0/4:0:0 (rt: 0.5.0/4:0:0). > > - Libs: > > - glib 2.54.1 (rt: 2.56.4/5604:4) > > - libzip 1.1.2 > > - libserialport 0.1.1/1:0:1 (rt: 0.1.1/1:0:1) > > - libusb-1.0 1.0.21.11156 > > - libftdi 1.3 > > - Host: i686-pc-linux-gnu, little-endian. > > - SCPI backends: TCP, RPC, serial, USBTMC. > > - libsigrokdecode 0.5.0/4:0:0 (rt: 0.5.0/4:0:0). > > - Libs: > > - glib 2.54.1 (rt: 2.56.4/5604:4) > > - Python 3.6.3 / 0x30603f0 (API 1013, ABI 3) > > - Host: i686-pc-linux-gnu, little-endian. > > > > > > > > $ sigrok-cli --scan -l 5 > > sr: [00:00.000002] log: libsigrok loglevel set to 5. > > sr: [00:00.000046] backend: libsigrok 0.5.0/4:0:0 (rt: > 0.5.0/4:0:0). > > sr: [00:00.000102] backend: Libs: glib 2.54.1 (rt: 2.56.4/5604:4), > > libzip 1.1.2, libserialport 0.1.1/1:0:1 (rt: 0.1.1/1:0:1), libusb- > > 1.0 > > 1.0.21.11156, libftdi 1.3. > > sr: [00:00.000137] backend: Host: i686-pc-linux-gnu, little-endian. > > sr: [00:00.000180] backend: SCPI backends: TCP, RPC, serial, > USBTMC. > > sr: [00:00.000241] backend: Sanity-checking all drivers. > > sr: [00:00.000258] backend: Sanity-checking all input modules. > > sr: [00:00.000274] backend: Sanity-checking all output modules. > > sr: [00:00.000289] backend: Sanity-checking all transform modules. > > srd: libsigrokdecode loglevel set to 5. > > sr: [00:00.011603] hwdriver: Scan of 'agilent-dmm' found 0 devices. > > sr: [00:00.011622] hwdriver: Scan of 'appa-55ii' found 0 devices. > > sr: [00:00.011633] hwdriver: Scan of 'arachnid-labs-re-load-pro' > > found 0 devices. > > sr: [00:00.020048] hwdriver: Scan of 'asix-sigma' found 0 devices. > > sr: [00:00.020062] hwdriver: Scan of 'atten-pps3203' found 0 > devices. > > sr: [00:00.020153] baylibre-acme: Name for probe 1 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-0040/name”: No > > such file or directory > > sr: [00:00.020181] baylibre-acme: Name for probe 2 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-0041/name”: No > > such file or directory > > sr: [00:00.020209] baylibre-acme: Name for probe 3 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-0044/name”: No > > such file or directory > > sr: [00:00.020241] baylibre-acme: Name for probe 4 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-0045/name”: No > > such file or directory > > sr: [00:00.020273] baylibre-acme: Name for probe 5 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-0042/name”: No > > such file or directory > > sr: [00:00.020300] baylibre-acme: Name for probe 5 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-004c/name”: No > > such file or directory > > sr: [00:00.020328] baylibre-acme: Name for probe 6 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-0043/name”: No > > such file or directory > > sr: [00:00.020354] baylibre-acme: Name for probe 6 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-0049/name”: No > > such file or directory > > sr: [00:00.020381] baylibre-acme: Name for probe 7 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-0046/name”: No > > such file or directory > > sr: [00:00.020408] baylibre-acme: Name for probe 7 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-004f/name”: No > > such file or directory > > sr: [00:00.020435] baylibre-acme: Name for probe 8 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-0047/name”: No > > such file or directory > > sr: [00:00.020462] baylibre-acme: Name for probe 8 can't be read: > > Failed to open file “/sys/class/i2c-adapter/i2c-1/1-004b/name”: No > > such file or directory > > sr: [00:00.020475] hwdriver: Scan of 'baylibre-acme' found 0 > devices. > > sr: [00:00.020491] hwdriver: Scan of 'beaglelogic' found 0 devices. > > sr: [00:00.020543] usb: Trying to find USB device with VID:PID = > > 0820:0001. > > sr: [00:00.020564] usb: Found 0 device(s). > > sr: [00:00.020576] hwdriver: Scan of 'brymen-bm86x' found 0 > devices. > > sr: [00:00.020587] hwdriver: Scan of 'brymen-bm857' found 0 > devices. > > sr: [00:00.020605] hwdriver: Scan of 'cem-dt-885x' found 0 devices. > > sr: [00:00.020622] hwdriver: Scan of 'voltcraft-k204' found 0 > > devices. > > sr: [00:00.020638] hwdriver: Scan of 'center-309' found 0 devices. > > sr: [00:00.021571] la8/la16: Unknown iProduct string 'LM-X210APM'. > > sr: [00:00.033667] la8/la16: Unknown iProduct string 'FT232R USB > > UART'. > > sr: [00:00.033772] hwdriver: Scan of 'chronovu-la' found 0 devices. > > sr: [00:00.033788] hwdriver: Scan of 'colead-slm' found 0 devices. > > sr: [00:00.033797] hwdriver: Scan of 'conrad-digi-35-cpu' found 0 > > devices. > > sr: [00:00.033852] hwdriver: Scan of 'demo' found 1 devices. > > sr: [00:00.033864] hwdriver: Scan of 'fluke-dmm' found 0 devices. > > sr: [00:00.045528] ftdi-la: Number of FTDI devices found: 1 > > sr: [00:00.060677] ftdi-la: Found an FTDI device: FT232R USB UART. > > sr: [00:00.060828] hwdriver: Scan of 'ftdi-la' found 1 devices. > > sr: [00:00.060967] hwdriver: Scan of 'fx2lafw' found 0 devices. > > sr: [00:00.061035] gmc-mh-1x-2x: scan_2x_bd232() called! > > sr: [00:00.061141] hwdriver: Scan of 'gmc-mh-2x-bd232' found 0 > > devices. > > sr: [00:00.061249] gmc-mh-1x-2x: scan_1x_2x_rs232() called! > > sr: [00:00.061357] hwdriver: Scan of 'gmc-mh-1x-2x-rs232' found 0 > > devices. > > sr: [00:00.061581] scpi_usbtmc: Found 0 device(s). > > sr: [00:00.067757] hwdriver: Scan of 'gwinstek-gds-800' found 0 > > devices. > > sr: [00:00.067869] scpi_usbtmc: Found 0 device(s). > > sr: [00:00.073464] hwdriver: Scan of 'hameg-hmo' found 0 devices. > > sr: [00:00.073500] hwdriver: Scan of 'hantek-6xxx' found 0 devices. > > sr: [00:00.073537] hwdriver: Scan of 'hantek-dso' found 0 devices. > > sr: [00:00.073615] scpi_usbtmc: Found 0 device(s). > > sr: [00:00.079317] hwdriver: Scan of 'hp-3457a' found 0 devices. > > sr: [00:00.079334] hwdriver: Scan of 'hung-chang-dso-2100' found 0 > > devices. > > sr: [00:00.079379] usb: Trying to find USB device with VID:PID = > > 20a0:4123. > > sr: [00:00.079401] usb: Found 0 device(s). > > sr: [00:00.079412] hwdriver: Scan of 'ikalogic-scanalogic2' found 0 > > devices. > > sr: [00:00.088689] hwdriver: Scan of 'ikalogic-scanaplus' found 0 > > devices. > > sr: [00:00.088866] usb: Trying to find USB device with VID:PID = > > 1041:8101. > > sr: [00:00.088988] usb: Found 0 device(s). > > sr: [00:00.089098] hwdriver: Scan of 'kecheng-kc-330b' found 0 > > devices. > > sr: [00:00.089207] hwdriver: Scan of 'kern-ew-6200-2nm' found 0 > > devices. > > sr: [00:00.089324] hwdriver: Scan of 'korad-kaxxxxp' found 0 > devices. > > sr: [00:00.089370] hwdriver: Scan of 'lascar-el-usb' found 0 > devices. > > sr: [00:00.089384] hwdriver: Scan of 'lecroy-logicstudio' found 0 > > devices. > > sr: [00:00.090374] scpi_usbtmc: Found 0 device(s). > > sr: [00:00.093339] hwdriver: Scan of 'lecroy-xstream' found 0 > > devices. > > sr: [00:00.093354] hwdriver: Scan of 'manson-hcs-3xxx' found 0 > > devices. > > sr: [00:00.093383] hwdriver: Scan of 'maynuo-m97' found 0 devices. > > sr: [00:00.093395] hwdriver: Scan of 'mic-98583' found 0 devices. > > sr: [00:00.093405] hwdriver: Scan of 'mic-98581' found 0 devices. > > sr: [00:00.093416] motech-lps-30x: scan() called! > > sr: [00:00.093433] serial: No serial device specified. > > sr: [00:00.093443] hwdriver: Scan of 'motech-lps-301' found 0 > > devices. > > sr: [00:00.093454] hwdriver: Scan of 'siemens-b102x' found 0 > devices. > > sr: [00:00.093464] hwdriver: Scan of 'norma-dmm' found 0 devices. > > sr: [00:00.093475] hwdriver: Scan of 'ols' found 0 devices. > > sr: [00:00.093486] hwdriver: Scan of 'pce-322a' found 0 devices. > > sr: [00:00.102994] p-ols: FTDI chip interface B set successfully. > > sr: [00:00.103055] hwdriver: Scan of 'p-ols' found 0 devices. > > sr: [00:00.103306] scpi_usbtmc: Found 0 device(s). > > sr: [00:00.106190] hwdriver: Scan of 'rigol-ds' found 0 devices. > > sr: [00:00.106248] scpi_usbtmc: Found 0 device(s). > > sr: [00:00.109064] hwdriver: Scan of 'rohde-schwarz-sme-0x' found 0 > > devices. > > sr: [00:00.109094] hwdriver: Scan of 'saleae-logic16' found 0 > > devices. > > sr: [00:00.109144] scpi_usbtmc: Found 0 device(s). > > sr: [00:00.112075] hwdriver: Scan of 'hpib-pps' found 0 devices. > > sr: [00:00.112132] scpi_usbtmc: Found 0 device(s). > > sr: [00:00.115056] hwdriver: Scan of 'scpi-pps' found 0 devices. > > sr: [00:00.115072] hwdriver: Scan of 'metrix-mx56c' found 0 > devices. > > sr: [00:00.115084] hwdriver: Scan of 'brymen-bm25x' found 0 > devices. > > sr: [00:00.115095] hwdriver: Scan of 'peaktech-3415' found 0 > devices. > > sr: [00:00.115124] hwdriver: Scan of 'velleman-dvm4100' found 0 > > devices. > > sr: [00:00.115135] hwdriver: Scan of 'iso-tech-idm103n' found 0 > > devices. > > sr: [00:00.115146] hwdriver: Scan of 'tenma-72-7750-ser' found 0 > > devices. > > sr: [00:00.115157] hwdriver: Scan of 'uni-t-ut60g-ser' found 0 > > devices. > > sr: [00:00.115167] hwdriver: Scan of 'uni-t-ut61e-ser' found 0 > > devices. > > sr: [00:00.115178] hwdriver: Scan of 'digitek-dt4000zc' found 0 > > devices. > > sr: [00:00.115189] hwdriver: Scan of 'mastech-ms8250b' found 0 > > devices. > > sr: [00:00.115199] hwdriver: Scan of 'pce-pce-dm32' found 0 > devices. > > sr: [00:00.115210] hwdriver: Scan of 'peaktech-3330' found 0 > devices. > > sr: [00:00.115221] hwdriver: Scan of 'tecpel-dmm-8061-ser' found 0 > > devices. > > sr: [00:00.115232] hwdriver: Scan of 'tekpower-tp4000ZC' found 0 > > devices. > > sr: [00:00.115243] hwdriver: Scan of 'tenma-72-7745-ser' found 0 > > devices. > > sr: [00:00.115253] hwdriver: Scan of 'uni-t-ut60a-ser' found 0 > > devices. > > sr: [00:00.115264] hwdriver: Scan of 'uni-t-ut60e-ser' found 0 > > devices. > > sr: [00:00.115275] hwdriver: Scan of 'va-va18b' found 0 devices. > > sr: [00:00.115286] hwdriver: Scan of 'va-va40b' found 0 devices. > > sr: [00:00.115296] hwdriver: Scan of 'voltcraft-vc820-ser' found 0 > > devices. > > sr: [00:00.115307] hwdriver: Scan of 'voltcraft-vc840-ser' found 0 > > devices. > > sr: [00:00.115317] hwdriver: Scan of 'uni-t-ut61b-ser' found 0 > > devices. > > sr: [00:00.115328] hwdriver: Scan of 'uni-t-ut61c-ser' found 0 > > devices. > > sr: [00:00.115339] hwdriver: Scan of 'uni-t-ut61d-ser' found 0 > > devices. > > sr: [00:00.115350] hwdriver: Scan of 'voltcraft-vc830-ser' found 0 > > devices. > > sr: [00:00.115360] hwdriver: Scan of 'bbcgm-2010' found 0 devices. > > sr: [00:00.115371] hwdriver: Scan of 'mastech-mas345' found 0 > > devices. > > sr: [00:00.115382] hwdriver: Scan of 'metex-m3640d' found 0 > devices. > > sr: [00:00.115392] hwdriver: Scan of 'metex-m4650cr' found 0 > devices. > > sr: [00:00.115403] hwdriver: Scan of 'metex-me31' found 0 devices. > > sr: [00:00.115414] hwdriver: Scan of 'peaktech-3410' found 0 > devices. > > sr: [00:00.115424] hwdriver: Scan of 'peaktech-4370' found 0 > devices. > > sr: [00:00.115434] hwdriver: Scan of 'radioshack-22-168' found 0 > > devices. > > sr: [00:00.115445] hwdriver: Scan of 'radioshack-22-805' found 0 > > devices. > > sr: [00:00.115456] hwdriver: Scan of 'voltcraft-m3650cr' found 0 > > devices. > > sr: [00:00.115467] hwdriver: Scan of 'voltcraft-m3650d' found 0 > > devices. > > sr: [00:00.115477] hwdriver: Scan of 'voltcraft-m4650cr' found 0 > > devices. > > sr: [00:00.115488] hwdriver: Scan of 'voltcraft-me42' found 0 > > devices. > > sr: [00:00.115498] hwdriver: Scan of 'radioshack-22-812' found 0 > > devices. > > sr: [00:00.115509] hwdriver: Scan of 'tenma-72-7730-ser' found 0 > > devices. > > sr: [00:00.115520] hwdriver: Scan of 'tenma-72-7732-ser' found 0 > > devices. > > sr: [00:00.115531] hwdriver: Scan of 'tenma-72-9380a-ser' found 0 > > devices. > > sr: [00:00.115541] hwdriver: Scan of 'uni-t-ut71a-ser' found 0 > > devices. > > sr: [00:00.115552] hwdriver: Scan of 'uni-t-ut71b-ser' found 0 > > devices. > > sr: [00:00.115562] hwdriver: Scan of 'uni-t-ut71c-ser' found 0 > > devices. > > sr: [00:00.115573] hwdriver: Scan of 'uni-t-ut71d-ser' found 0 > > devices. > > sr: [00:00.115584] hwdriver: Scan of 'uni-t-ut71e-ser' found 0 > > devices. > > sr: [00:00.115594] hwdriver: Scan of 'voltcraft-vc920-ser' found 0 > > devices. > > sr: [00:00.115605] hwdriver: Scan of 'voltcraft-vc940-ser' found 0 > > devices. > > sr: [00:00.115615] hwdriver: Scan of 'voltcraft-vc960-ser' found 0 > > devices. > > sr: [00:00.115626] hwdriver: Scan of 'voltcraft-vc870-ser' found 0 > > devices. > > sr: [00:00.115637] hwdriver: Scan of 'deree-de5000' found 0 > devices. > > sr: [00:00.115648] hwdriver: Scan of 'peaktech-2170' found 0 > devices. > > sr: [00:00.115668] hwdriver: Scan of 'sysclk-lwla' found 0 devices. > > sr: [00:00.115680] hwdriver: Scan of 'teleinfo' found 0 devices. > > sr: [00:00.127728] hwdriver: Scan of 'testo' found 0 devices. > > sr: [00:00.127748] hwdriver: Scan of 'tondaj-sl-814' found 0 > devices. > > sr: [00:00.127759] hwdriver: Scan of 'tecpel-dmm-8061' found 0 > > devices. > > sr: [00:00.127830] hwdriver: Scan of 'uni-t-ut372' found 0 devices. > > sr: [00:00.127841] hwdriver: Scan of 'uni-t-ut60a' found 0 devices. > > sr: [00:00.127903] hwdriver: Scan of 'uni-t-ut60e' found 0 devices. > > sr: [00:00.127914] hwdriver: Scan of 'uni-t-ut60g' found 0 devices. > > sr: [00:00.127975] hwdriver: Scan of 'uni-t-ut61b' found 0 devices. > > sr: [00:00.128085] hwdriver: Scan of 'uni-t-ut61c' found 0 devices. > > sr: [00:00.128194] hwdriver: Scan of 'uni-t-ut61d' found 0 devices. > > sr: [00:00.128303] hwdriver: Scan of 'uni-t-ut61e' found 0 devices. > > sr: [00:00.128412] hwdriver: Scan of 'uni-t-ut71a' found 0 devices. > > sr: [00:00.128522] hwdriver: Scan of 'uni-t-ut71b' found 0 devices. > > sr: [00:00.128640] hwdriver: Scan of 'uni-t-ut71c' found 0 devices. > > sr: [00:00.128750] hwdriver: Scan of 'uni-t-ut71d' found 0 devices. > > sr: [00:00.131070] hwdriver: Scan of 'uni-t-ut71e' found 0 devices. > > sr: [00:00.131243] hwdriver: Scan of 'voltcraft-vc820' found 0 > > devices. > > sr: [00:00.131371] hwdriver: Scan of 'voltcraft-vc830' found 0 > > devices. > > sr: [00:00.131497] hwdriver: Scan of 'voltcraft-vc840' found 0 > > devices. > > sr: [00:00.131623] hwdriver: Scan of 'voltcraft-vc870' found 0 > > devices. > > sr: [00:00.131840] hwdriver: Scan of 'voltcraft-vc920' found 0 > > devices. > > sr: [00:00.132044] hwdriver: Scan of 'voltcraft-vc940' found 0 > > devices. > > sr: [00:00.132249] hwdriver: Scan of 'voltcraft-vc960' found 0 > > devices. > > sr: [00:00.132467] hwdriver: Scan of 'tenma-72-7730' found 0 > devices. > > sr: [00:00.132681] hwdriver: Scan of 'tenma-72-7732' found 0 > devices. > > sr: [00:00.132718] hwdriver: Scan of 'tenma-72-9380a' found 0 > > devices. > > sr: [00:00.132753] hwdriver: Scan of 'tenma-72-7745' found 0 > devices. > > sr: [00:00.132779] hwdriver: Scan of 'tenma-72-7750' found 0 > devices. > > sr: [00:00.132806] hwdriver: Scan of 'uni-t-ut32x' found 0 devices. > > sr: [00:00.132859] hwdriver: Scan of 'victor-dmm' found 0 devices. > > sr: [00:00.133005] scpi_usbtmc: Found 0 device(s). > > sr: [00:00.139820] hwdriver: Scan of 'yokogawa-dlm' found 0 > devices. > > sr: [00:00.144735] hwdriver: Scan of 'zeroplus-logic-cube' found 0 > > devices. > > The following devices were found: > > demo - Demo device with 12 channels: D0 D1 D2 D3 D4 D5 D6 D7 A0 A1 > A2 > > A3 > > ftdi-la - FTDI FT232R USB UART with 8 channels: TXD RXD RTS# CTS# > > DTR# DSR# DCD# RI# > > On Tuesday, March 24, 2020, 05:10:59 AM EDT, Soeren Apel < > > soe...@apelpie.net> wrote: > > > > > > Hello Richard, > > > > Which libsigrok version does "sigrok-cli -V" report? This lib > > contains > > the drivers. > > > > Please try connecting with the nightly AppImage: > > https://sigrok.org/wiki/Downloads#Linux_AppImage_binaries > > > > If that still doesn't work, you can run "sigrok-cli --scan -l 5" > > and attach the log output to the mail. > > > > Regards > > -Soeren > > > > > > On Mon, 2020-03-23 at 20:06 +0000, Richard Andrews via sigrok-devel > > wrote: > > > Hello, > > > > > > I have an Extech 380193 lcr meter. It looks similar to the > > > Voltcraft 4080 and the Peaktech 2165. > > > > > > I ran "sigrok-cli -L" and none of those meters drivers were > listed. > > > I ran "sigrok-cli --scan" and only demo and ftdi-la drivers were > > > listed. > > > > > > I installed everything from Ubuntu Mate bionic. > > > > > > How do I get the drivers for the meters? > > > > > > > > > _______________________________________________ > > > sigrok-devel mailing list > > > sigrok-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
