The DS1102Z based on the DS1000Z Serie with 2Channel with all Options allready activated. I tried different Version of Pulseview and sigrok-cli but I couldn't establish a connection over USBTMC and Network with the DS1102Z-E Firmware 00.06.02 I got the following response from the Network (*IDN?) 'RIGOL TECHNOLOGIES,DS1102Z-E,DS1ZE224310098,00.06.02' Here the Log from the sigrok-cli command sr: [00:00.000000] log: libsigrok loglevel set to 5. sr: [00:00.001000] backend: libsigrok 0.6.0-git-3cc9e21/4:0:0. sr: [00:00.003000] backend: Libs: glib 2.44.1 (rt: 2.44.1/4401:1), libzip 1.5.2, libserialport 0.1.1/1:0:1 (rt: 0.1.1/1:0:1), libusb-1.0 1.0.20.11003-rc3 API 0x01000104, hidapi 0.8.0-rc1, libftdi 1.4. sr: [00:00.004000] backend: Host: x86_64-w64-mingw32.static.posix, little-endian. sr: [00:00.004000] backend: SCPI backends: TCP, serial, USBTMC. ..... srd: libsigrokdecode loglevel set to 5. sr: [00:00.187000] scpi_usbtmc: Found USBTMC device (VID:PID = 1ab1:0517, bus.address = 2.10). sr: [00:00.189000] scpi: Opening USBTMC device usbtmc/2.10. sr: [00:00.208000] usb: Found USB device (VID:PID = 1ab1:0517, bus.address = 2.10). sr: [00:00.210000] usb: Trying to open USB device 2.10. sr: [00:00.226000] usb: Failed to open device: LIBUSB_ERROR_NOT_SUPPORTED. sr: [00:00.227000] scpi: Couldn't open SCPI device. sr: [00:00.399000] hwdriver: Scan found 0 devices (rigol-ds). Over IP i get this log: sigrok-cli -d rigol-ds:conn=tcp-raw/172.17.58.94/5555 --scan -l 5 sr: [00:00.000000] log: libsigrok loglevel set to 5. sr: [00:00.000000] backend: libsigrok 0.6.0-git-3cc9e21/4:0:0. sr: [00:00.001000] backend: Libs: glib 2.44.1 (rt: 2.44.1/4401:1), libzip 1.5.2, libserialport 0.1.1/1:0:1 (rt: 0.1.1/1:0:1), libusb-1.0 1.0.20.11003-rc3 API 0x01000104, hidapi 0.8.0-rc1, libftdi 1.4. sr: [00:00.001000] backend: Host: x86_64-w64-mingw32.static.posix, little-endian. sr: [00:00.002000] backend: SCPI backends: TCP, serial, USBTMC. .... srd: libsigrokdecode loglevel set to 5. sr: [00:00.034000] hwdriver: sr_config_list(): key 2147418112 (NULL) sdi 0000000000000000 cg NULL -> [uint32 20000, 20001] sr: [00:00.035000] scpi: Opening RAW TCP device tcp-raw/172.17.58.94/5555. sr: [00:00.038000] scpi_tcp: Successfully sent SCPI command: '*IDN?'. sr: [00:00.045000] scpi: Got response: 'RIGOL TECHNOLOGIES,DS1102Z-E,DS1ZE224310098,00.06.02', length 52. sr: [00:00.045000] hwdriver: Scan found 0 devices (rigol-ds). It would nice the recongnition Problem could be solved.
Update 31.01.2021 after i apply the folling row in rigol-ds api.c {SERIES(DS1000Z), "DS1102Z-E", {2, 1000000000}, CH_INFO(2, false), std_cmd}, the TCP Connection worked, after recompiled with the Crosscompiler MX2. But the USBTMC seems still not to work under windows10 Version 10.0.19042 Build 19042.
Created attachment 724 [details] Patch for udev rules to include USB PID for DS1102Z-E The changes for api.c seems to have been merged with this commit: https://sigrok.org/gitweb/?p=libsigrok.git;a=commit;h=0f5dcee6cea4288a429876d0c38e429dded4b75e For USB to work on Linux for unprivileged users there’s also a patch for the udev rules necessary as the DS1102Z-E has a new USB product id: Bus 001 Device 018: ID 1ab1:0517 Rigol Technologies DS1000Z Series With the current git master and the udev rules patch the device works fine, using USB connections as well as over network. (Though not at the same time, and the device's network stack seems to have problems. If USB was connected before, I had to restart the device to be able to use network.)