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

[fredo_]

I'm starting a new thread as a follow-up of the discussions on Siglent HD and Rigol DHO800/900 models support for Sigrok/PulseView.

There seems to be quite some frustration about the lack of activity in Sigrok development, and the fact that Pull Requests for new hardware never get merged in the codebase, due to the difficulty of testing changes on different scope models.
I was thinking, maybe we could leverage on the strong EEVblog community to overcome this testing issue.
So I spent (quite!) some time setting up a Linux building environment (as recommended by the Sigrok team) to be able to cross-compile PulseView Windows installer ; and I was able to create a binary with a first attempt of support for new Siglent models (2000X plus and 2000X HD) based on the work of Eric Kuzmenko.

It's been successfully tested on my SDS2000X HD over Ethernet (see pictures bellow) and by other EEVblog contributors on SDS800X HD, SDS1000X HD and SDS2000X Plus.

If anyone is interested in testing it with other Siglent/Rigol models, here is a link to the Windows (64bits) installer (zip password is 'sigrok').

And thanks to the work of @Spike : here is a Mac OS version (the dmg doesn't explicitly say it but the arm64 will only run on Sonoma and the x86_64 is for Ventura.).

I also own a Rigol DHO800, so my next challenge (when I come back from vacation, two weeks from now  ) could be to try and add new Rigol models support if you guys are interested  ...
Rigol DHO800/900/1000/4000 support added on latest versions !

08/26/2024 Update
Siglent SDS : fixed support for sub 10mV vertical ranges
08/07/2024 Update
Rigol DHO : added support for DHO1000 and DHO4000
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
08/01/2024 Update
Siglent SDS :
- Fixed pagination for memory depth > 4 Mpts (issue where the waveform was truncated and replicated)
07/27/2024 Update
Siglent SDS :
- Fixed acquisition for memory depth > 4 Mpts
Rigol DHO :
- Fixed USB acquisition
07/22/2024 Update
Added Rigol DHO 800/900 support with known limitations :
- LA not tested (I don't own a DHO 900)
- Only works in TCP/IP mode
- Segmented mode only works if :
  1/ UltraAquire is manually activated on the scope (SCPI command to activate it does not seem to work)
  2/ Memory depth is set to 10Kpts or lower

I'm waiting for your feedback on this !

Cheers,

Frederic.

P.S. : The source code of my work is available here : https://github.com/fredzo/libsigrok

[kripton2035]

subscribed...
if you can compile a binary for macos arm I would be really interesed ! I tried to compile original sigrok sources with no luck so far.

[TomKatt]

That's a LOT of work - my hat is off to you.

Open source can be great, but sometimes things turn into spaghetti code over time and experienced coders move on to different projects leaving things in a state that can be difficult to add new features.  I'm surprised that the device driver foundation wasn't set up to be more flexible from the beginning, but I'm sure the original coders had their reasons...  Or simply never anticipated the project would grow to the extent that it did.

Edit - While it's obviously not the best option, if the desire to get newer Siglent / Rigol gear working with Sigrock is sufficient, perhaps the project just gets forked into a version that only works for those models so you don't have to test or worry about all the legacy devices...   Seems like the goal now is to add device compatibility rather than adding new functionality.  DSlogic took this approach when they 'borrowed' Sigrok's source code to create their DSview application for their own brand of logic analyzers.  While they were (rightfully) dragged through the mud for not disclosing that Sigrok's code was used to create their code, they might have got some slack for not contributing any improvements they made back to the original Sigrok project considering the difficulties mentioned earlier.

Edit2 - I wonder if Siglent's SigScopeLab software is aiming towards providing Sigrok like functionality for their compatible products?  I haven't tried it myself, but it seems limited and I understand from posts in the forums that it's a bit buggy as well.

[fredo_]

if you can compile a binary for macos arm I would be really interesed ! I tried to compile original sigrok sources with no luck so far.

Well that's another story!... You need a Mac and MacOS to do that, which I don't have :-(

That's a LOT of work - my hat is off to you.

Thanks TomKatt !

While it's obviously not the best option, if the desire to get newer Siglent / Rigol gear working with Sigrock is sufficient, perhaps the project just gets forked into a version that only works for those models so you don't have to test or worry about all the legacy devices...I understand from posts in the forums that it's a bit buggy as well.

Well my hope here is to find some help from owners of older Siglent models, to validate my patch so that it can hopefully be merged back to Sigrok's codebase

I wonder if Siglent's SigScopeLab software is aiming towards providing Sigrok like functionality for their compatible products?  I haven't tried it myself, but it seems limited and I understand from posts in the forums that it's a bit buggy as well.

Well I tried it when it got out and could not get anything out of it appart from hanging my scope to the point that I had to hard-reboot it  ...
Just checked, there is no new version available yet...

[Spike]

if you can compile a binary for macos arm I would be really interesed ! I tried to compile original sigrok sources with no luck so far.

Well that's another story!... You need a Mac and MacOS to do that, which I don't have :-(

I can build you a macOS binary, kripton, but as I recall you’re still on Ventura which I cannot build for arm64.  Unless you want x86_64, I’m afraid it’s Sonoma only.  Otherwise I can try to help you build your own but I suspect that will be a bit of a pain because my dependencies come from macports rather than homebrew like everyone seems to use these days.

[Spike]

That's a LOT of work - my hat is off to you.

Open source can be great, but sometimes things turn into spaghetti code over time and experienced coders move on to different projects leaving things in a state that can be difficult to add new features.  I'm surprised that the device driver foundation wasn't set up to be more flexible from the beginning, but I'm sure the original coders had their reasons...  Or simply never anticipated the project would grow to the extent that it did.

Edit - While it's obviously not the best option, if the desire to get newer Siglent / Rigol gear working with Sigrock is sufficient, perhaps the project just gets forked into a version that only works for those models so you don't have to test or worry about all the legacy devices...   Seems like the goal now is to add device compatibility rather than adding new functionality.  DSlogic took this approach when they 'borrowed' Sigrok's source code to create their DSview application for their own brand of logic analyzers.  While they were (rightfully) dragged through the mud for not disclosing that Sigrok's code was used to create their code, they might have got some slack for not contributing any improvements they made back to the original Sigrok project considering the difficulties mentioned earlier.

I think that working toward the flexibility you talk about is effort better spent, rather than forking. Separating the hardware support from libsigrok altogether would be a good start.  These should be separately buildable and dynamically loaded at runtime.   Sure the project could bundle support for a collection of vetted, tested devices but it should not require a new build of sigrok to support your device if you have the means to write/build your own.  That, of course, means a dynamic loader for the hardware modules with access to the existing API.  If that can't get merged then a fork would seem in order.

Edit2 - I wonder if Siglent's SigScopeLab software is aiming towards providing Sigrok like functionality for their compatible products?  I haven't tried it myself, but it seems limited and I understand from posts in the forums that it's a bit buggy as well.

Unfortunately I don't think Siglent has ever published anything other than Windows software which leaves folks like kripton2035 and myself out in the cold.  Siglent software will likely never be an option for us.

[kripton2035]

if you can compile a binary for macos arm I would be really interesed ! I tried to compile original sigrok sources with no luck so far.

Well that's another story!... You need a Mac and MacOS to do that, which I don't have :-(

I can build you a macOS binary, kripton, but as I recall you’re still on Ventura which I cannot build for arm64.  Unless you want x86_64, I’m afraid it’s Sonoma only.  Otherwise I can try to help you build your own but I suspect that will be a bit of a pain because my dependencies come from macports rather than homebrew like everyone seems to use these days.

As chatgpt for macos desktop works only on sonoma+, I think this will convince me to upgrade very soon ...

[kripton2035]

wouldn't it be easier to build one sigrok for each device brand ? one for rigol, one for siglent ?
as a hobbyst, I will not change my main scope very often... so I could stay with one "sigrok for siglent" for many years to come ...

[dpenev]

I've checked the fredo windows installer with my SDS2000X and I have observed very unstable behavior.
I am using "siglent-sds" TCP/IP Port 5025 "Raw TCP" to connect to my scope.

I did manage to capture few analog frames but most of the time the PulseView hangs or terminates completely.
Probably I have to set something?   

[kripton2035]

this is for the 2000x HD, not sure if it can work for the 2000X or plus ?
the standard sigrok version is announced to work with the 2000x

[Spike]

I've checked the fredo windows installer with my SDS2000X and I have observed very unstable behavior.
I am using "siglent-sds" TCP/IP Port 5025 "Raw TCP" to connect to my scope.

I did manage to capture few analog frames but most of the time the PulseView hangs or terminates completely.
Probably I have to set something?   

This patch adds support for the 2000X Plus and 2000X HD (though the level of testing for the Plus is unknown), it should not affect the behavior on the 2000X.  If you do not see this instability with the official nightly build but you do with this one, that would be useful information to know.  Have you tried the official nightly with your scope?

[dpenev]

Sorry, my oscilloscope is actually SDS2000X Plus family.

[Spike]

Sorry, my oscilloscope is actually SDS2000X Plus family.

The Plus and HD share virtually all the code in this implementation so if Frederic can reproduce this on his HD then perhaps a fix will be forthcoming.  Regardless you’ll probably need to provide him a detailed description of the behavior.  For now, as mentioned upthread, he is on holiday for the next couple weeks.

[fredo_]

Hi dpenev,
Thank you for taking the time to test the patch with you SDS2000X Plus!
For my SDS2000X HD, no additional settings was needed, it worked with Raw TCP on port 2025 (see picture bellow).
Could you please try and send us the content of you log window :
- Launch PulseView, go to Settings (tools icon in the top bar) / Logging and set log level to 5
- Connect to your scope and Run an acquisition
- Go back to settings and see what's in the Logging window
Thanks for your help !

[kripton2035]

@Spike, I'm now on Sonoma, so tests can go further ! thanks.

[Spike]

@Spike, I'm now on Sonoma, so tests can go further ! thanks.

PM sent

[Frex]

Hello fredo_,

I'm also interested to use Sigrock with my SDS2000X+.
So, I tried your installer for pulseview and I installed also Sigrock "sigrok-cli (64bit)" Nightly builds.
(Done with Win11 PC).

I tested first with a Rigol MSO2072A that is in supported device list of Sigrock.
It is well recognized and Pulseview works ok (Raw TCP only).

Then I tried to do same with SDS2104X+, but the scope is not detected in any TCP/VXI mode.
Do I should try something else ?
Regards.

Frex

[Frex]

Hi,

I finally manage to connect to the SDS2104X+.
For that, I changed port to 5025 as on your screenshoot.

The screen data record work(>20Mpts), but when scope data point become high it no longer work.
 In some case, I had even need to restart the scope that no responding anymore.
Regards.

FRex

[fredo_]

Bonjour Frex !
Yes I was about to suggest to check the connection port ;-)
OK thanks for the feedback, you seem to run in the same troubles as dpenev :-/
I suspect a timing issue due to the delay needed by the scope to send the data to the computer.
Could you try and get access to the log content as suggested here ? : https://www.eevblog.com/forum/testgear/new-sigrokpulseview-hardware-support-(siglent-sds-hd-rigol-dho800-)/msg5558089/#msg5558089
Just PM me if you need assistance in French ! :-)

[Frex]

Bonjour fredo_ ! 

You can show below the log results for a first connection with 1ms timebase and 10Mpts that work fine.
The second screenshot is the result when I change timebase to 2ms for 20Mpts.
Regards.

Frex

[fredo_]

Great, thanks Frex !
That confirms my hypothesis.
I'll prepare a fix when I come back home by the end of next week.

[Lathe26]

I am looking forward to DHO900 support from Sigrok.  However, be aware that there is a bug in the current firmware (v1.02.00.02) where the analog channels (CHAN1-CHAN4) and math channels (MATH1-MATH4) are supported but the logic analyzer is not (D0-D15).  The documentation claims that D0-D15 are supported via ":WAVeform:SOURce" but this command fails when you actually try it.  This issue has been reported to Rigol but with no response yet.

[fredo_]

Thanks for the heads up Lathe26 !
Let's hope Rigol issues a fix soon...
Anyway, I will not be able to test the LA for Rigol Sigrok driver since I only own a DHO8OO :-/
But if you or anyone else can test and report back, I'll be glad to try and make any necessary adjustments

[Lathe26]

I am willing to try it out once Rigol fixes their LA bug.

[fredo_]

Hi folks !
Back from a beautiful journey in Scotland, I patched the installer to try and fix the read timing issues
Link has been updated on the first post, and you can find it here as well : Windows (64bits) installer (zip password is 'sigrok').
@Frex / @dpenev could you please try this new version and see if it works any better for your scopes ?
This new version should also support all Siglent recent series, that is :

• SDS 800X HD Series
• SDS 1000X HD Series
• SDS 2000X HD Series
• SDS 3000X HD Series
• SDS 5000X Series
• SDS 6000L Series
• SDS 6000A Series
• SDS 6000 Pro Series
• SDS 7000A Series

Best,

Frederic.

[teddychn]

Hi Fredo,

Thanks for sharing! I'm really excited to try your patched version.

With just CH1 acquisition, it works perfectly with memory depth equal to or less than 4Mpts. However, PulseView seems to wait forever with a data length of 10Mpts. My environment is a Windows 10 PC with an SDS2000X HD. Please take a look at the attachments to see if they have any information useful to this situation.

Appreciate it!

[Electro Fan]

Hi folks !
Back from a beautiful journey in Scotland, I patched the installer to try and fix the read timing issues
Link has been updated on the first post, and you can find it here as well : Windows (64bits) installer (zip password is 'sigrok').
@Frex / @dpenev could you please try this new version and see if it works any better for your scopes ?
This new version should also support all Siglent recent series, that is :

• SDS 800X HD Series
• SDS 1000X HD Series
• SDS 2000X HD Series
• SDS 3000X HD Series
• SDS 5000X Series
• SDS 6000L Series
• SDS 6000A Series
• SDS 6000 Pro Series
• SDS 7000A Series

Best,

Frederic.

It is very impressive and valuable what you and the other contributors are doing with this project!
Thanks!

[fredo_]

With just CH1 acquisition, it works perfectly with memory depth equal to or less than 4Mpts. However, PulseView seems to wait forever with a data length of 10Mpts. My environment is a Windows 10 PC with an SDS2000X HD. Please take a look at the attachments to see if they have any information useful to this situation.

Thanks for the feedback @teddychn !
I'm almost done with Rigol DHO800/900 support (thanks to the work previously done by Diana Ellefson (OrionOth) and RemiNV here).
I'll switch back to Siglent SDS2000X HD to try and reproduce your problem right after that.

[fredo_]

~~~ Updated version with Rigol DHO 800/900 support ~~~
Hi folks !
Here is my attempt to add Rigol DHO 800/900 support to Sigrok/PulseView (link has been updated in first post too) : Windows (64bits) installer (zip password is 'sigrok').
Disclaimer :
- LA not tested since I only have a DHO 800 with an identity crisis 
- Only works in TCP/IP mode
- Segmented mode only works if :
  1/ UltraAquire is manually activated on the scope (SCPI command to activate it does not seem to work)
  2/ Memory depth is set to 10Kpts or lower
Any feedback is welcome, especially from DHO 900 owners !

[Furna]

@Frex / @dpenev could you please try this new version and see if it works any better for your scopes ?
This new version should also support all Siglent recent series, that is :

• SDS 800X HD Series

I will try ASAP with my Siglent SDS824X HD and report here.
I was starting to work on this (see https://www.eevblog.com/forum/testgear/siglent-sds800x-hd-12-bit-dsos-coming/msg5546249/#msg5546249) but currently I am following too many projects; so a big thank you!

[fredo_]

Hi guys,

I just updated the patch with the following changes:
07/27/2024 Update
Siglent SDS :
- Fixed acquisition for memory depth > 4 Mpts
- Known limitations :
   - USB acquisition does not work (use TCP/IP with Raw TCP and port 5025)
   - LA acquisition might fail for memory depth > 50 Mpts
Rigol DHO :
- Fixed USB acquisition
Link has been updated on the first post, and you can find it here as well : Windows (64bits) installer (zip password is 'sigrok').

@teddychn this should fix your issue with memory depth >4Mpts.

Please let me know if this is working for you guys !

Best,

Fredo.

[Spike]

Hi guys,

I just updated the patch with the following changes:
07/27/2024 Update
Siglent SDS :
- Fixed acquisition for memory depth > 4 Mpts
- Known limitations :
   - USB acquisition does not work (use TCP/IP with Raw TCP and port 5025)
   - LA acquisition might fail for memory depth > 50 Mpts
Rigol DHO :
- Fixed USB acquisition
Link has been updated on the first post, and you can find it here as well : Windows (64bits) installer (zip password is 'sigrok').

@teddychn this should fix your issue with memory depth >4Mpts.

Please let me know if this is working for you guys !

Best,

Fredo.

Are you planning to keep the Siglent and Rigol support on separate branches from now on or will this get merged onto your master?

[fredo_]

Are you planning to keep the Siglent and Rigol support on separate branches from now on or will this get merged onto your master?

I will keep separated branches to be able to eventually create two distinct pull requests on Sigrok repository.
But I just merged the two branches on my master to make it easier for you to create a Mac OS build.
The USB fix is not included as I borrowed it from a PR on sigrok repository, but it's a Windows only fix, so no worries.

[Spike]

Are you planning to keep the Siglent and Rigol support on separate branches from now on or will this get merged onto your master?

I will keep separated branches to be able to eventually create two distinct pull requests on Sigrok repository.
But I just merged the two branches on my master to make it easier for you to create a Mac OS build.
The USB fix is not included as I borrowed it from a PR on sigrok repository, but it's a Windows only fix, so no worries.

Excellent!   Thank you very much.

[Spike]

Are you planning to keep the Siglent and Rigol support on separate branches from now on or will this get merged onto your master?

I will keep separated branches to be able to eventually create two distinct pull requests on Sigrok repository.
But I just merged the two branches on my master to make it easier for you to create a Mac OS build.
The USB fix is not included as I borrowed it from a PR on sigrok repository, but it's a Windows only fix, so no worries.

Excellent!   Thank you very much.

Did you push those back up?  I'm not seeing it.

[fredo_]

Did you push those back up?  I'm not seeing it.

Sorry, forgot to push, that should be good now!

[Spike]

Did you push those back up?  I'm not seeing it.

Sorry, forgot to push, that should be good now!

Got it now.  Thanks again.

[Spike]

Did you push those back up?  I'm not seeing it.

Sorry, forgot to push, that should be good now!

Got it now.  Thanks again.

Hitting this while trying to compile the rigol stuff:

Code: [Select]

  CC       src/hardware/rigol-ds/api.lo
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1038:4: error: expected expression
                        int frames = 0;
                        ^
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1040:55: error: use of undeclared identifier 'frames'
                        if (sr_scpi_get_int(sdi->conn, ":ACQ:ULTR:MAXF?", &frames) != SR_OK)
                                                                           ^
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1042:8: error: use of undeclared identifier 'frames'
                        if (frames <= 0) {
                            ^
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1046:33: error: use of undeclared identifier 'frames'
                        devc->num_frames_segmented = frames;
                                                     ^
4 errors generated.

Pretty sure this needs it's own scope or there needs to be a statement before that declaration.

[fredo_]

Hitting this while trying to compile the rigol stuff:

Code: [Select]

  CC       src/hardware/rigol-ds/api.lo
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1038:4: error: expected expression
                        int frames = 0;
                        ^
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1040:55: error: use of undeclared identifier 'frames'
                        if (sr_scpi_get_int(sdi->conn, ":ACQ:ULTR:MAXF?", &frames) != SR_OK)
                                                                           ^
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1042:8: error: use of undeclared identifier 'frames'
                        if (frames <= 0) {
                            ^
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1046:33: error: use of undeclared identifier 'frames'
                        devc->num_frames_segmented = frames;
                                                     ^
4 errors generated.

Pretty sure this needs it's own scope or there needs to be a statement before that declaration.

Yep, not sure why my compiler did not complain... I pushed the fix.

[Spike]

Hitting this while trying to compile the rigol stuff:

Code: [Select]

  CC       src/hardware/rigol-ds/api.lo
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1038:4: error: expected expression
                        int frames = 0;
                        ^
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1040:55: error: use of undeclared identifier 'frames'
                        if (sr_scpi_get_int(sdi->conn, ":ACQ:ULTR:MAXF?", &frames) != SR_OK)
                                                                           ^
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1042:8: error: use of undeclared identifier 'frames'
                        if (frames <= 0) {
                            ^
/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1046:33: error: use of undeclared identifier 'frames'
                        devc->num_frames_segmented = frames;
                                                     ^
4 errors generated.

Pretty sure this needs it's own scope or there needs to be a statement before that declaration.

Yep, not sure why my compiler did not complain... I pushed the fix.

Looks good, thanks!

[teddychn]

@teddychn this should fix your issue with memory depth >4Mpts.

Please let me know if this is working for you guys !

Hi Fredo,

Now it can download waveforms of more than 4Mpts. However, the waveform on PulseView seems off. I found that the issue starts at 5Mpts and occurs periodically. Please refer to the screenshots.

Thanks for your work and Best Regards,
Ted

[Furna]

Hello Fredo,

I have the same behaviour seen by teddychn on my SDS824X HD; see screenshots.





First time I am using an oscilloscope and first time I am using Sigrock/PulseView ... still have to learn a lot.
Let me know if I can test anything specific and sorry for taking long to test and report.

[Frex]

Hello,

I am back on vacation and then I tested your new Windows 10 installer.
(is it normal that the zip uses strictly the same file name "pulseview-0.5.0-git-d00efc6-installer"
 when they are different versions?).

Now, when the data points exceed 10 Mpts, only the first channel is acquired and then stops.
The other channels are not acquired and it is not possible to restart the acquisition.

I also noticed that a new icon appears in this case, indicating the sequence mode...
I don't know why. The resulting screenshot below.

I also noticed that the scope hang very often and need to be rebooted to work again.

Frex

[fredo_]

Hi guys,

(is it normal that the zip uses strictly the same file name "pulseview-0.5.0-git-d00efc6-installer"
 when they are different versions?).

Well it's obviously not ideal but it's the easiest way for me to update the file without having to change the link on the different posts in this topic.
From now on, to make it easier to identify the version, I will add the date to the model description in the connection dialog :


Anyway, here is a new version (link has been updated in first post too) : Windows (64bits) installer (zip password is 'sigrok')

Changes in this version :
08/01/2024 Update
Siglent SDS :
- Fixed pagination for memory depth > 4 Mpts (issue where the waveform was truncated and replicated)
- 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

This should fix the truncated waveform reported by @teddychn and @Furna.

@Frex, I reworked the acquisition logic in this version so could you please make another attempt with your SDS 2000X plus and send me the log window content with log level set to 5 ?

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...
Anyway, be aware that LA acquisition will not work properly for memory depth > 5Mpts.

Best,

Fredo.

[Furna]

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...

You might want to check
https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/
https://www.eevblog.com/forum/testgear/siglent-sds2000x-hd-missing-features-and-bugs/
and contact forum member 2N3055 if you do not get an answer from Siglent.

[Spike]

Hi guys,

(is it normal that the zip uses strictly the same file name "pulseview-0.5.0-git-d00efc6-installer"
 when they are different versions?).

Well it's obviously not ideal but it's the easiest way for me to update the file without having to change the link on the different posts in this topic.
From now on, to make it easier to identify the version, I will add the date to the model description in the connection dialog :
(Attachment Link)

Anyway, here is a new version (link has been updated in first post too) : Windows (64bits) installer (zip password is 'sigrok')

Changes in this version :
08/01/2024 Update
Siglent SDS :
- Fixed pagination for memory depth > 4 Mpts (issue where the waveform was truncated and replicated)
- 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

This should fix the truncated waveform reported by @teddychn and @Furna.

@Frex, I reworked the acquisition logic in this version so could you please make another attempt with your SDS 2000X plus and send me the log window content with log level set to 5 ?

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...
Anyway, be aware that LA acquisition will not work properly for memory depth > 5Mpts.

Best,

Fredo.

Any chance this could be merged to master?

[fredo_]

Any chance this could be merged to master?

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

[Frex]

Hekko Fredo and all,


Renaming model name in dialog list is a good idea 
That avoid confusing versions.

I tried your newer pulseview version, but it seem not working for me.
The "Run" button become green for about a second and then stop after clicking on it.
There is no resulting acquisition trace.
You can show below the log result (log level set to 5).
I add also a log file.
Thank you for all your efforts !
Regards.

FRex

[fredo_]

Thanks Frex for the feedback et log information !
Could you please try and put the scope in Stop mode before launching the capture ?
I suspect that the scope as not yet triggered when it receives de "DATA?" command...

[Frex]

Hi,
I tried to put it in stop mode before to start acquisition, same behavior.
You can find the log result of few unsuccessful attempt below.
Regards.

Frex

[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

[dpenev]

Thanks Furna,
I have  followed the procedure I have described two messages back and the log attached.
 

...
sr: scpi_tcp: Successfully sent SCPI command: ':TDIV? '.
sr: scpi: Got response: 'DAT2,#9000000000 AVEDESC1.00E+075.00E-04', length 40.
sr: session: bus: Received SR_DF_HEADER packet.
sr: scpi_tcp: Successfully sent SCPI command: 'WAV:MAXP? '.
sr: scpi: Got response: '5.00E-04', length 8.
sr: scpi: get_int: non-integer rational=500/1000000
sr: session: Could not start siglent-sds device tcp-raw/192.168.1.6/5025 acquisition.
...

'DAT2,#9000000000 AVEDESC1.00E+075.00E-04' looks a concatenation of few responses.

5.00E-04 is my current timing resolution 500us/div

WAV:MAXP?  if sent separately to the oscilloscope returns 10000000 but I don't see it in the log.

 

[Furna]

Thanks Furna,
I have  followed the procedure I have described two messages back and the log attached.
 

...
sr: scpi_tcp: Successfully sent SCPI command: ':TDIV? '.
sr: scpi: Got response: 'DAT2,#9000000000 AVEDESC1.00E+075.00E-04', length 40.
sr: session: bus: Received SR_DF_HEADER packet.
sr: scpi_tcp: Successfully sent SCPI command: 'WAV:MAXP? '.
sr: scpi: Got response: '5.00E-04', length 8.
sr: scpi: get_int: non-integer rational=500/1000000
sr: session: Could not start siglent-sds device tcp-raw/192.168.1.6/5025 acquisition.
...

'DAT2,#9000000000 AVEDESC1.00E+075.00E-04' looks a concatenation of few responses.

5.00E-04 is my current timing resolution 500us/div

WAV:MAXP?  if sent separately to the oscilloscope returns 10000000 but I don't see it in the log.

Can you try with a different resolution? I was succesfull with 10mV/div with SDS824X HD

See also
https://www.eevblog.com/forum/testgear/new-sigrokpulseview-hardware-support-(siglent-sds-hd-rigol-dho800-)/msg5605601/#msg5605601
With SDS2104X+ it is not possible to go lower than 10mV/div and fredo_ is looking at it.

[dpenev]

Seems not related with Voltage resolution. I have tested with 1V/div and still similar behavior.
| am attaching another log for someone to check. I have a feeling that it is a timing issue in the the communication.
Assuming that the software is working fine for someone else with SDS2000X+
In my case both the PC running PV and the scope are in the same LAN connected directly in the same router, 1,2m LAN cables.

Pinging 192.168.1.6 with 32 bytes of data:
Reply from 192.168.1.6: bytes=32 time<1ms TTL=64
Reply from 192.168.1.6: bytes=32 time<1ms TTL=64
Reply from 192.168.1.6: bytes=32 time<1ms TTL=64
Reply from 192.168.1.6: bytes=32 time<1ms TTL=64

[fredo_]

Hi @dpenev and thank you for your investigations !

Seems not related with Voltage resolution. I have tested with 1V/div and still similar behavior.
| am attaching another log for someone to check. I have a feeling that it is a timing issue in the the communication.
Assuming that the software is working fine for someone else with SDS2000X+
In my case both the PC running PV and the scope are in the same LAN connected directly in the same router, 1,2m LAN cables.

No it doesn't seem to be a timing issue, the problem comes from the response of the scope to the ACQ:POIN? command.
You scope gives a ".9" reply while the Sigrok (and the documentation) expects something of the form "1.25E+08".
This command returns the number of points of the current waveform. Can you check the memory depth of the scope and maybe the value returned by ACQ:POIN? SCPI command form web control ?

[fredo_]

Oh and @dpenev, you may want to try and reboot your scope (including removing the powder cable).
It happened to me a few times: I started having very strange SCPI responses from the scope, and after a full reboot, everything went back to normal  .

[fredo_]

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.

That would be great !

Hi there,
Here is a new version that should fix the sub 10mV vertical range issue for Siglent models : Windows (64bits) installer (zip password is 'sigrok').
08/26/2024 Update
Siglent SDS : fixed support for sub 10mV vertical ranges

[Spike]

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.

That would be great !

Hi there,
Here is a new version that should fix the sub 10mV vertical range issue for Siglent models : Windows (64bits) installer (zip password is 'sigrok').
08/26/2024 Update
Siglent SDS : fixed support for sub 10mV vertical ranges

Updated macOS builds available; see first post for link.

[hansibull]

Amazing work! What are the odds of getting your fork merged into the official Sigrok repo? I have been using Sigrok's libserialport library, and I even found a nasty bug that affects macOS. I clearly demonstrated the issue and even submitted a PR, but It hasn't gotten any attention from the developers.

[fredo_]

Amazing work! What are the odds of getting your fork merged into the official Sigrok repo?

Thanks !
Well I created the two PRs yesterday, now that things seem quite stable:
https://github.com/sigrokproject/libsigrok/pull/245
https://github.com/sigrokproject/libsigrok/pull/246
So wait and see !...

[Furna]

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 !...

Any update from Siglent ?

[Furna]

Amazing work! What are the odds of getting your fork merged into the official Sigrok repo?

Thanks !
Well I created the two PRs yesterday, now that things seem quite stable:
https://github.com/sigrokproject/libsigrok/pull/245
https://github.com/sigrokproject/libsigrok/pull/246
So wait and see !...

Let us know if we can sponsor your PR

[fredo_]

Any update from Siglent ?

Yes I had a first reply from the support team with a code snippet showing a working example of pagination on digital data, but this was not relevant since it was paginating only on a few hundred of bytes.
I replied explaining that the problem only appeared for 5Mpts+ frame, but they did not come back to me so far (this was mid-august).

Let us know if we can sponsor your PR

For now I'm trying to reach out to project committers on the dedicated Discord channel...

[hansibull]

I really hope your PRs gain some traction from the Sigrok maintainers. They cover the most popular Rigol and Siglent scopes currently on the market, making Sigrok relevant for many new users.
I used your Sigrok fork to capture data with a Siglent SDS2000X HD and decode an SPDIF signal, something no scope has built-in decoding for.

[Spike]

Amazing work! What are the odds of getting your fork merged into the official Sigrok repo?

Thanks !
Well I created the two PRs yesterday, now that things seem quite stable:
https://github.com/sigrokproject/libsigrok/pull/245
https://github.com/sigrokproject/libsigrok/pull/246
So wait and see !...

The reviewer of the siglent PR on which your work is based was github user fenugrec.  I’d be shocked if that isn’t the very same fenugrec user as here on the EEVblog forum.  Perhaps you could reach out here and see if you can get things moving a little sooner.

[wiretail]

Just wanted to add a hearty thanks for this.  One of the first things I tested with my new SDS804/824.  Works great!

Doing analog->digital convert->custom python decoder's direct from the scope, , is wonderful.  (Wherever it might be -- with a tailscale network, it's handy for remote investigation too.)

[fredo_]

Just wanted to add a hearty thanks for this.  One of the first things I tested with my new SDS804/824.  Works great!

Doing analog->digital convert->custom python decoder's direct from the scope, , is wonderful.  (Wherever it might be -- with a tailscale network, it's handy for remote investigation too.)

Thanks for the feedback @wiretail !
If you have some spare time, you might want to check the other project I'm working on: https://www.eevblog.com/forum/testgear/ngscopeclient-ultimate-acquisition-software-protocol-decoder-debug-tool/
We need testing from SDS800 owners ;-)

[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 !...

Any update from Siglent ?

I just received a confirmation from Siglent support that they could reproduce the bug and that they are working on a fix ! 

[Furna]

I just received a confirmation from Siglent support that they could reproduce the bug and that they are working on a fix ! 

Thank you for the update!