Bug 1521 - Cannot connect to Rigol DS1054Z over USB connection
Summary: Cannot connect to Rigol DS1054Z over USB connection
Alias: None
Product: libsigrok
Classification: Unclassified
Component: Driver: rigol-ds (show other bugs)
Version: 0.5.2
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
Depends on:
Reported: 2020-03-19 18:46 CET by mrnuke
Modified: 2020-06-25 00:35 CEST (History)
3 users (show)

sigrok-cli log (3.20 KB, text/plain)
2020-03-19 18:46 CET, mrnuke

Note You need to log in before you can comment on or make changes to this bug.
Description mrnuke 2020-03-19 18:46:16 CET
Created attachment 612 [details]
sigrok-cli log

Pulseview is not able to connect to a Rigol 1054Z over USB, even though the USB device has +uaccess permissions.

Applicable release versions:

Fedora 31
libsigrok: 0.5.2
pulseview: 0.4.1
sigrok-cli: 0.7.1

Additional info:

sigrok-cli log shows a USB timeout error, then a degmentation fault (will attach log)
Comment 1 Martin Ling 2020-03-19 19:22:15 CET
This looks like the same problem as bug #1272.
Comment 2 Martin Ling 2020-03-19 19:28:18 CET
On the version that you have, I think you should also be able to work around this by adding "-d rigol-ds" to specify the driver.
Comment 3 Gerhard Sittig 2020-05-30 13:04:03 CEST
I understand this was reported against an older software version. Does it 
reproduce with recent software? Does the combination of -D and -d succeed 
as a workaround? The "ECHO-TEST" literals strongly suggests that the issue 
got fixed long ago.
Comment 4 Uwe Hermann 2020-06-25 00:35:16 CEST
Hi, please try to reproduce with git master as of today, a few fixes have been merged which might affect this. The segfault should be gone, and a simple "sigrok-cli --scan" works fine for me (DS1054Z, attached via USB) as well as a basic PulseView acquisition.

Partial log:
sr: [00:01.101954] hwdriver: Scan found 1 devices (rigol-ds).
sr: [00:01.101984] scpi_usbtmc: Found USBTMC device (VID:PID = 1ab1:04ce, bus.address = 1.16).
sr: [00:01.101993] scpi: Opening USBTMC device usbtmc/1.16.
sr: [00:01.102028] usb: Found USB device (VID:PID = 1ab1:04ce, bus.address = 1.16).
sr: [00:01.102037] usb: Trying to open USB device 1.16.
sr: [00:01.102054] usb: Opened USB device (VID:PID = 1ab1:04ce, bus.address = 1.16).
sr: [00:01.102059] scpi_usbtmc: Interface 0 configuration 1.
sr: [00:01.102062] scpi_usbtmc: Interrupt EP 1
sr: [00:01.102067] scpi_usbtmc: Bulk IN EP 2
sr: [00:01.102071] scpi_usbtmc: Bulk OUT EP 3
sr: [00:01.102553] scpi_usbtmc: Device capabilities: SCPI, L4, T6, SR1, RL1, DT1
sr: [00:01.102564] scpi_usbtmc: Locking out local control.
sr: [00:01.103363] scpi_usbtmc: Successfully sent SCPI command: ''.
sr: [00:01.103431] scpi_usbtmc: Successfully sent SCPI command: '*IDN?'.
sr: [00:01.125775] scpi: Got response: 'RIGOL TECHNOLOGIES,DS1054Z,DS1ZA195222846,00.04.04.SP3', length 54.
sr: [00:01.125818] scpi_usbtmc: Returning local control.
sr: [00:01.126766] usb: Closed USB device 1.16.
The following devices were found:
demo - Demo device with 13 channels: D0 D1 D2 D3 D4 D5 D6 D7 A0 A1 A2 A3 A4
rigol-ds - Rigol DS1054Z 00.04.04.SP3 [S/N: DS1ZA195222846] with 4 channels: CH1 CH2 CH3 CH4