New Sigrok/PulseView hardware support (Siglent SDS HD, Rigol DHO...)

[Spike]

Any chance this could be merged to master?

Done !
@Spike if you have working Mac build, maybe you could share it here ?

Sure, here's something:

https://www.dropbox.com/scl/fo/7fp3toladqj5fz16ugp8w/AImd1yuWyACIZ1nnTrm9-rk?rlkey=be64qo1o3ppvu24sbm05s8rxu&dl=0

The dmg doesn't explicitly say it but the arm64 will only run on Sonoma and the x86_64 is for Ventura.

[fredo_]

You can find the log result of few unsuccessful attempt below.

Thanks for that Frex! I just sent you a PM to investigate your problem.

https://www.dropbox.com/scl/fo/7fp3toladqj5fz16ugp8w/AImd1yuWyACIZ1nnTrm9-rk?rlkey=be64qo1o3ppvu24sbm05s8rxu&dl=0
The dmg doesn't explicitly say it but the arm64 will only run on Sonoma and the x86_64 is for Ventura.

Great ! I'll add the link to OP if it's OK for you.
Have you been able to test this Mac version with your scope ?

[Spike]

You can find the log result of few unsuccessful attempt below.

Thanks for that Frex! I just sent you a PM to investigate your problem.

https://www.dropbox.com/scl/fo/7fp3toladqj5fz16ugp8w/AImd1yuWyACIZ1nnTrm9-rk?rlkey=be64qo1o3ppvu24sbm05s8rxu&dl=0
The dmg doesn't explicitly say it but the arm64 will only run on Sonoma and the x86_64 is for Ventura.

Great ! I'll add the link to OP if it's OK for you.
Have you been able to test this Mac version with your scope ?

Nope.  I just learned that my scope will be delayed a further 6 weeks; I won’t see it until mid-September.  I’ve been providing these builds to kripton2035 from this thread, and rosenrot who reached out to me privately.  You’d have to ask them if there are issues.

[Furna]

Hi guys,

I just updated the patch with the following changes:
07/27/2024 Update
Siglent SDS :
- Fixed acquisition for memory depth > 4 Mpts

Working OK on SDS8024X HD



Also multi channel acquisition is working

[kripton2035]

I’ve been providing these builds to kripton2035 from this thread, and rosenrot who reached out to me privately.  You’d have to ask them if there are issues.

seems to work fine on the arm/sonoma version for me. even a 100Mpts acquisition seems to work, but it takes a long time to come to the computer (20-30s)

[kripton2035]

it also seems to work with a 200Mpts acquisition...

[fredo_]

Thank you @Furna and @kripton2035 for the feedback, glad to know that it starts working !

seems to work fine on the arm/sonoma version for me. even a 100Mpts acquisition seems to work, but it takes a long time to come to the computer (20-30s)

That's perfectly normal : there is a huge amount of data to transfer over TCP (that's 100Mbyte per channel), it takes quite some time.

Anyone with a Rigol DHO800 or 900 was able to play with it ?

I created a new version to try and solve triggering issues on large time bases :  Windows (64bits) installer (zip password is 'sigrok').
08/04/2024 Update
Siglent SDS :
- Fixed triggering issues on large timebases
- Known limitations :
   - USB acquisition does not work (use TCP/IP with Raw TCP and port 5025)
   - LA acquisition pagination (for memory depth > 5Mpts) is not working on SDS 2000X HD (firmware issue ?) causing the first 5Mpts to be replicated several times
   - LA acquisition might fail for memory depth > 50 Mpts

I worked with @Frex too to fix support for SDS 2000X Plus and he reported that he managed a 100Mpts acquisition on 4 analog channels + 16 digital channels !

Please keep the feedback coming!

[skander36]

It seem to work also with SDS1000X-HD.
I can't connect to DHO1000X-HD.

[fredo_]

It seem to work also with SDS1000X-HD.

Great, thank you for the feedback @skander36 !

It seem to work also with SDS1000X-HD.
I can't connect to DHO1000X-HD.

That's because I only added DHO800/900 to the driver descriptor.
If DHO1000 line uses the same SCPI protocol, I can try and add it too.
For that I would need :
- The response to the "*IDN?" SCPI command
- For USB support, the productId as returned by lsusb or equivalent (see here)

[skander36]

Thank you very much for your work.

...
- The response to the "*IDN?" SCPI command

RIGOL TECHNOLOGIES,DHO1074,HDO1B244401552,00.02.13


For USB I will provide later as this scope use a high speed USB3) connector for which I dont have a cable -
Anyway I'm not using USB for any device.

[fredo_]

Regarding LA acquisition, I spent quite some time trying and understand how to have pagination work (data blocks are limited to 5Mpts, over that memory depth, data has to be paginated) but I came to the conclusion that the SDS2000X HD has a bug that prevents pagination to work. The result is that the first 5Mpts datablock is replicated several times on LA channels :-/
I ended up sending a mail to Siglent support to report the issue. Not sure if/when I'll get a response and this will be fixed...

Just a quick update on this , I got the following  reply from Siglent support :

This may be a bug in the software. Our R&D department is analyzing this problem. I will inform you as soon as I have the result.

Wait and see !...

[skander36]

...
 RIGOL TECHNOLOGIES,DHO1074
- For USB support, the productId as returned by lsusb or equivalent (see here)

SCPI - USB0::0x1AB1::0x0610::HDO1B244401552::INSTR
LSUSB - Bus 002 Device 006: ID 1ab1:0610 Rigol Technologies HDO1074
Windows Device Manager - USB\VID_1AB1&PID_0610\HDO1B244401552

[fredo_]

SCPI - USB0::0x1AB1::0x0610::HDO1B244401552::INSTR
LSUSB - Bus 002 Device 006: ID 1ab1:0610 Rigol Technologies HDO1074
Windows Device Manager - USB\VID_1AB1&PID_0610\HDO1B244401552

Thanks @skander36 

And here comes the version with DHO1000 and DHO4000 support ! : Windows (64bits) installer (zip password is 'sigrok').

@skander36 and @Frex can you check if it is working as expected with your DHO1000 ?

[Spike]

SCPI - USB0::0x1AB1::0x0610::HDO1B244401552::INSTR
LSUSB - Bus 002 Device 006: ID 1ab1:0610 Rigol Technologies HDO1074
Windows Device Manager - USB\VID_1AB1&PID_0610\HDO1B244401552

Thanks @skander36 

And here comes the version with DHO1000 and DHO4000 support ! : Windows (64bits) installer (zip password is 'sigrok').

@skander36 and @Frex can you check if it is working as expected with your DHO1000 ?

Apologies if anyone is waiting for a Mac build.  I’ve been sick recently and am still recovering and hope to be back on my feet in the next couple days.  I will try to get updated builds out then.

[thm_w]

Thanks @skander36 

And here comes the version with DHO1000 and DHO4000 support ! : Windows (64bits) installer (zip password is 'sigrok').

@skander36 and @Frex can you check if it is working as expected with your DHO1000 ?

Thank you fredo, working here for USB and ethernet.

For USB, usual sigrok routine:
- Run Zadig -> Options -> Show all devices. Select DHO1000, replace driver with WinUSB.
- USB 3 cable is not required.

[fredo_]

Thank you fredo, working here for USB and ethernet.

Thank you @thm_w, that's good news ! 

[neodimio91]

@_fredo , I'm a sds2104x plus owner, everything seems to work perfectly with new updates, feel free to reach me for any testing !

[fredo_]

@_fredo , I'm a sds2104x plus owner, everything seems to work perfectly with new updates, feel free to reach me for any testing !

Thanks for the feedback @neodimio91 ! 

[Spike]

SCPI - USB0::0x1AB1::0x0610::HDO1B244401552::INSTR
LSUSB - Bus 002 Device 006: ID 1ab1:0610 Rigol Technologies HDO1074
Windows Device Manager - USB\VID_1AB1&PID_0610\HDO1B244401552

Thanks @skander36 

And here comes the version with DHO1000 and DHO4000 support ! : Windows (64bits) installer (zip password is 'sigrok').

@skander36 and @Frex can you check if it is working as expected with your DHO1000 ?

Apologies if anyone is waiting for a Mac build.  I’ve been sick recently and am still recovering and hope to be back on my feet in the next couple days.  I will try to get updated builds out then.

Updated Mac builds available at the link provided previously.

[Frex]

Hello fredo_,

As others, I also have run successfully you last version with both
Siglent SDS2104X+ and RIGOL DHO1074.
I can use the maximum memory depth in both cases.
Congratulation for your work and perseverance !

I have a little question anyway.
I noticed that with the SDS2104X+ it work as making a single acquisition
and then imported in PulseView capture window.
There is no "live" mode data view like with the DHO1074.
Is that come from the scope itself ?

Another thing that can be annoying sometimes (at least for me...),
I couldn't set the vertical sensitivity lower than 10mV/div.
Both scope can go down to 500µV/div so it seem that PulseView
doesn't support it even it is displayed in configure channel top menu.
Best regards,

Frex

[skander36]

SCPI - USB0::0x1AB1::0x0610::HDO1B244401552::INSTR
LSUSB - Bus 002 Device 006: ID 1ab1:0610 Rigol Technologies HDO1074
Windows Device Manager - USB\VID_1AB1&PID_0610\HDO1B244401552

Thanks @skander36 

And here comes the version with DHO1000 and DHO4000 support ! : Windows (64bits) installer (zip password is 'sigrok').

@skander36 and @Frex can you check if it is working as expected with your DHO1000 ?

Hello!
Sorry I forgot to check for notify this thread.
Yes the DHO1074 can be seen now on USB and also with live mode.
With a USB 2.0 (printer) cable, the transfer is slow and in live mode capture fail quickly when change timebase on scope.
Thank you!

[fredo_]

Thanks for the feedback @Frex and @skander36  !

There is no "live" mode data view like with the DHO1074.
Is that come from the scope itself ?

That's not really the scope but more how the original Siglent SDS driver was designed..
It's probably possible to have a "Live" mode like the on the Rigol driver, but it would require a big rework and there's the risk to break support for older scopes (for which I have ne way to test backward compatibility).

I couldn't set the vertical sensitivity lower than 10mV/div.
Both scope can go down to 500µV/div so it seem that PulseView
doesn't support it even it is displayed in configure channel top menu.

That I should be able to fix, I'll take a look.

Yes the DHO1074 can be seen now on USB and also with live mode.
With a USB 2.0 (printer) cable, the transfer is slow and in live mode capture fail quickly when change timebase on scope.

Yeah I'm not surprised about that : live mode would not detect changes in the settings on the scope ant that would lead to protocol errors.

[dpenev]

Hello,
I check the latest installer above. It seems it is a bit more stable with mine SDS2104X Plus ,
but I have found an issue first 2 min i was playing.
Probably I am not doing something right?

I and using "Siglent SDS/08-07-2024(siglent-sds)" "TCP/IP Port 5025 "Raw TCP"
Is this what I have to use?

1. I had my scope with CH2 only enabled (before starting PulseView) and I was able to press Run in PulseView and capture the trace.
2. I have tried to enable the CH1 now as shown
3. On pressing Run again I get "Capture Failed"

Any comments?

[Furna]

I and using "Siglent SDS/08-07-2024(siglent-sds)" "TCP/IP Port 5025 "Raw TCP"
Is this what I have to use?

Yes, correct connection parameter

1. I had my scope with CH2 only enabled (before starting PulseView) and I was able to press Run in PulseView and capture the trace.
2. I have tried to enable the CH1 now as shown
3. On pressing Run again I get "Capture Failed"

I'll try to replicate ASAP (could take long) ... meanwhile you might want to capture some logs.
See https://www.eevblog.com/forum/testgear/new-sigrokpulseview-hardware-support-(siglent-sds-hd-rigol-dho800-)/msg5558089/#msg5558089

[Frex]

Thanks for the feedback @Frex and @skander36  !

I couldn't set the vertical sensitivity lower than 10mV/div.
Both scope can go down to 500µV/div so it seem that PulseView
doesn't support it even it is displayed in configure channel top menu.

That I should be able to fix, I'll take a look.

Hello fredo, you're welcome 

That would be great !
Thank you for all your efforts and the detailed answers.
Regards.

Frex