I have exactly the same issue:
Lots of problems with Pulse view and Siglent SDS1104X-E and latest Firmware 6.1.35R2

I have run Nightly and stable versions on a variety of platforms. Windows 10, Mac Mojave and Catalina, none of which are working properly and mostly just crashing.

PULSE VIEW ON MOJAVE AND CATALINA
- Latest nightly build of simply crashes when you try and select any driver in the device list.
- The Stable build 0.4.2 gets further but doesn't show a trace via USB connection. 
 With network connection it records 20ms of trace and then crashes.  "See Problem report #1" below.


PULSE VIEW ON WINDOWS10
- using WinUSB (v6.1.7600.16385) drive installed via Zadig.exe
- Stable release & Latest nightly build
  - runs and doesn't crash but doesn't show any traces and reports both
    - "sr: scpi_usbtmc: USBTMC invalid bulk in header."
    - "scpi_usbtmc: USBTMC bulk in transfer error: LIBUSB_ERROR_TIMEOUT." error in logging. See Problem report #2 below
  - could not get network interface to work.  Device was not recognised though I could browse on IE to the devices hosted webserver.

If any more info is required please let me know.

Thanks

Andy



PROBLEM REPORT #1
Date/Time:        2020-10-15 10:00:18 +0200
End time:         2020-10-15 10:02:38 +0200
OS Version:       Mac OS X 10.15.6 (Build 19G2021)
Architecture:     x86_64h
Report Version:   29

Data Source:      Stackshots
Shared Cache:     0x61e8000 5329506A-6EFD-362C-83DD-CC8ECAA8A5F9

Command:          pulseview.real
Path:             /Applications/PulseView.app/Contents/MacOS/pulseview.real
Version:          ??? (???)
Parent:           launchd [1]
PID:              1148

Event:            hang
Duration:         140.39s
Duration Sampled: 4.10s (process was unresponsive for 136 seconds before sampling)
Steps:            41 (100ms sampling interval)

Hardware model:   MacBookPro11,3
Active cpus:      8

Time Awake Since Boot: 2300s

Fan speed:        3387 rpm



PROBLEM REPORT #2
pv: "Note for device developers: Ignoring device configuration capability 'Number of horizontal divisions' as it is missing GET and/or SET"
pv: "Note for device developers: Ignoring device configuration capability 'Sample rate' as it is missing GET and/or SET"
pv: "Note for device developers: Ignoring device configuration capability 'Number of vertical divisions' as it is missing GET and/or SET"
pv: "Note for device developers: Ignoring device configuration capability 'Number of vertical divisions' as it is missing GET and/or SET"
pv: "Note for device developers: Ignoring device configuration capability 'Number of vertical divisions' as it is missing GET and/or SET"
pv: "Note for device developers: Ignoring device configuration capability 'Number of vertical divisions' as it is missing GET and/or SET"
pv: "Note for device developers: Ignoring device configuration capability 'Number of horizontal divisions' as it is missing GET and/or SET"
pv: "Note for device developers: Ignoring device configuration capability 'Sample rate' as it is missing GET and/or SET"
pv: "Note for device developers: Ignoring device configuration capability 'Number of vertical divisions' as it is missing GET and/or SET"
pv: "Note for device developers: Ignoring device configuration capability 'Number of vertical divisions' as it is missing GET and/or SET"
pv: "Note for device developers: Ignoring device configuration capability 'Number of vertical divisions' as it is missing GET and/or SET"
pv: "Note for device developers: Ignoring device configuration capability 'Number of vertical divisions' as it is missing GET and/or SET"
sr: scpi_usbtmc: USBTMC invalid bulk in header.
sr: scpi_usbtmc: USBTMC invalid bulk in header.
sr: scpi_usbtmc: USBTMC invalid bulk in header.
sr: scpi_usbtmc: USBTMC invalid bulk in header.
sr: scpi_usbtmc: USBTMC invalid bulk in header.
sr: scpi_usbtmc: USBTMC invalid bulk in header.
sr: scpi_usbtmc: USBTMC invalid bulk in header.
sr: scpi_usbtmc: USBTMC invalid bulk in header.
sr: scpi_usbtmc: USBTMC invalid bulk in header.
sr: scpi_usbtmc: USBTMC invalid bulk in header.
sr: scpi_usbtmc: USBTMC invalid bulk in header.
scpi_usbtmc: USBTMC bulk in transfer error: LIBUSB_ERROR_TIMEOUT.
scpi_usbtmc: USBTMC bulk in transfer error: LIBUSB_ERROR_TIMEOUT.
scpi_usbtmc: USBTMC bulk in transfer error: LIBUSB_ERROR_TIMEOUT.
scpi_usbtmc: USBTMC bulk in transfer error: LIBUSB_ERROR_TIMEOUT.
scpi_usbtmc: USBTMC bulk in transfer error: LIBUSB_ERROR_TIMEOUT.
scpi_usbtmc: USBTMC bulk in transfer error: LIBUSB_ERROR_TIMEOUT.
scpi_usbtmc: USBTMC bulk in transfer error: LIBUSB_ERROR_TIMEOUT.
scpi_usbtmc: USBTMC bulk in transfer error: LIBUSB_ERROR_TIMEOUT.

I downloaded the latest nightly build 18/11/2020 and the LIBUSB_ERROR_TIMEOUT error is gone.

However, still no data captured and selection of a device still crashes the program - only tested on Catalina

sr: scpi_usbtmc: Successfully sent SCPI command: 'SANU? C1 '.
sr: scpi: Got response: '3.50E+06', length 8.
sr: scpi_usbtmc: Successfully sent SCPI command: ':TDIV? '.
sr: scpi: Got response: '5.00E-04', length 8.
sr: siglent-sds: Current timebase: 0.0005.
sr: siglent-sds: Current samplerate: 500000000.000000.
sr: siglent-sds: Current memory depth: 3500000.
sr: hwdriver: sr_config_get(): key 30000 (samplerate) sdi 0x7f829e7f4270 cg NULL -> uint64 500000000
sr: session: Using thread-default main context.
sr: session: Starting.
sr: hwdriver: siglent-sds: Starting acquisition.
sr: scpi_usbtmc: Successfully sent SCPI command: 'SANU? C1 '.
sr: scpi: Got response: '3.50E+06', length 8.
sr: scpi_usbtmc: Successfully sent SCPI command: ':TDIV? '.
sr: scpi: Got response: '5.00E-04', length 8.
sr: siglent-sds: Current timebase: 0.0005.
sr: siglent-sds: Current samplerate: 500000000.000000.
sr: siglent-sds: Current memory depth: 3500000.
sr: session: bus: Received SR_DF_HEADER packet.
sr: siglent-sds: Starting data capture for active frameset 1 of 1
sr: scpi_usbtmc: Successfully sent SCPI command: 'ARM '.
sr: scpi_usbtmc: Successfully sent SCPI command: ':INR? '.
sr: scpi: Got response: '8192', length 4.
sr: session: bus: Received SR_DF_FRAME_BEGIN packet.
sr: session: Stopping.
sr: hwdriver: siglent-sds: Stopping acquisition.
sr: session: bus: Received SR_DF_END packet.
sr: usb: usb_source_finalize
sr: session: Stopped.
pv: Acquisition took 1.22 s

I'll try to take a look at this. Currently I'm working on fixing the tcp socket side for SDS1104X (and it seems to be working, so might as well try the USB next)

(In reply to voneiden from comment #3)
> I'll try to take a look at this. Currently I'm working on fixing the tcp
> socket side for SDS1104X (and it seems to be working, so might as well try
> the USB next)

Hi voneiden,

That's great news on the TCP issue.  Is this in the nightly build so I could test?  You efforts are much appreciated.  Thank you for also considering fixing the USB bug too.

Andy

Nothing in nightly yet. I have some workaround attempts that allow me to acquire signals but nothing that works reliably. I haven't quite understood so far what the root cause is for these issues, but it feels like the communication protocol simply gets out of sync, possibly due to unexpected response from the device. 

Anyway, I'm a hobbyist C programmer, unfamiliar with Sigrok and both SCPI and USBTMC protocols, so don't get too hopeful. :-)

(In reply to voneiden from comment #5)
> Nothing in nightly yet. I have some workaround attempts that allow me to
> acquire signals but nothing that works reliably. I haven't quite understood
> so far what the root cause is for these issues, but it feels like the
> communication protocol simply gets out of sync, possibly due to unexpected
> response from the device. 
> 
> Anyway, I'm a hobbyist C programmer, unfamiliar with Sigrok and both SCPI
> and USBTMC protocols, so don't get too hopeful. :-)

Understood, I appreciate the effort!

Good news, (significant) progress in resolving the issue has been made: I have USB acquisition in "Display" mode working.  "History" mode is still throwing an error which I need to investigate, but I imagine that should not be too hard to fix as it already works in TCP mode.

(In reply to voneiden from comment #7)
> Good news, (significant) progress in resolving the issue has been made: I
> have USB acquisition in "Display" mode working.  "History" mode is still
> throwing an error which I need to investigate, but I imagine that should not
> be too hard to fix as it already works in TCP mode.

Excellent news, well done!!

Not sure if the patch is going to make it to nightly anytime soon (or ever), so I've made my own pulseview win64 release, if you dare and want to try it out. Available at https://github.com/voneiden/libsigrok/releases/tag/siglent-xe-1

(In reply to voneiden from comment #9)
> Not sure if the patch is going to make it to nightly anytime soon (or ever),
> so I've made my own pulseview win64 release, if you dare and want to try it
> out. Available at
> https://github.com/voneiden/libsigrok/releases/tag/siglent-xe-1

Hey Voneiden,

Well done!! That is working on a Windows 10 VM for me with the USB interface!!

Andy

If you're constantly on the go, portability becomes a significant factor to consider. Laptops come in various sizes, from ultra-lightweight models to larger, more powerful ones. https://fitlaptops.com/best-laptops-under-600/