Bug 1242 - Siglent SDS 1104X-E unable to connect
Summary: Siglent SDS 1104X-E unable to connect
Status: IN_PROGRESS
Alias: None
Product: libsigrok
Classification: Unclassified
Component: Driver: siglent-sds (show other bugs)
Version: 0.5.0
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: marchelh
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-01 13:43 CEST by Julian
Modified: 2018-10-15 07:36 CEST (History)
2 users (show)


Attachments
DeviceFound (50.92 KB, image/png)
2018-07-01 13:43 CEST, Julian 		Details
Failed to open (27.66 KB, image/png)
2018-07-01 13:43 CEST, Julian 		Details
FoundViaLan (33.81 KB, image/png)
2018-07-01 13:44 CEST, Julian 		Details
Freeze (34.23 KB, image/png)
2018-07-01 13:44 CEST, Julian 		Details
Nmap Scan (27.33 KB, image/png)
2018-07-01 13:45 CEST, Julian 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Julian 2018-07-01 13:43:11 CEST 
Created attachment 438 [details]
DeviceFound

I use the Scope Siglent SDS 1104X-E (SW Version: 7.1.6.25 R2)
I already installed the WinUSB drivers via Zadig (WinUSB Version 6.1.7600.16385)

Pulse View is able to find the scope via USB (DeviceFound.PNG). 
But if i try to connect to the scope PV spits out an error(FailedToOpen.PNG).

As an alternative i tried to connect to the scope via TCP/IP.
PV is also able to detect the scope with the scope's IP and the Port 5025 (FoundViaLan.PNG).
If i try to connect to the scope this way PV freezes (freeze.png).

With Nmap i found all the ports corresponding to the scope's IP(NmapScan.PNG).
If i try any other combination of ports and VXI enabled/disabled i either get no result or PV freezes.

I am able to connect to the scope if i type the IP into my browser. And the Siglent Software EasyScopeX also is able to connect to the scope.

Best Regards
Julian
Comment 1 Julian 2018-07-01 13:43:51 CEST 
Created attachment 439 [details]
Failed to open
Comment 2 Julian 2018-07-01 13:44:11 CEST 
Created attachment 440 [details]
FoundViaLan
Comment 3 Julian 2018-07-01 13:44:39 CEST 
Created attachment 441 [details]
Freeze
Comment 4 Julian 2018-07-01 13:45:00 CEST 
Created attachment 442 [details]
Nmap Scan
Comment 5 marchelh 2018-07-01 22:18:48 CEST 
Hi to all,

This is indeed a problem where I'm currently working on. Siglent has changed a lot on the API for this device especially the later firmware.
Comment 6 Uwe Hermann 2018-10-14 14:51:51 CEST 
Hi, a first set of changes by marchelh is now merged as c90065a9499768f1663771136da10ee05e641677, please test. I've done *some* quick testing on my devices, but there still seem to be some USB issues left, will report details later.
Comment 7 Julian 2018-10-14 18:20:10 CEST 
nothing has changed for me. i still cant connect and the above mentioned errors are exactly the same again. is the Windows Version on your website the one i should test or did you made a specific version for this?
Comment 8 marchelh 2018-10-15 07:33:33 CEST 
All,

I know there is still a issue with the USB implementation regarding the new E series devices. I'm currently working on the issue. Its a problem with the transport layer, where only 64 bytes are returned from the transport, where I request either the full buffer or at least the size of the header block.
Comment 9 marchelh 2018-10-15 07:36:54 CEST 
(In reply to Julian from comment #7)
> nothing has changed for me. i still cant connect and the above mentioned
> errors are exactly the same again. is the Windows Version on your website
> the one i should test or did you made a specific version for this?

The driver does work on a network connection, however the current build of LibSigrok does not support network on Windows builds.