New Sigrok/PulseView hardware support (Siglent SDS HD, Rigol DHO...) - Page 1
Forum section: electronics / testgear

author: fredo_
author_rank: Regular Contributor
timestamp: June 27, 2024, 10:56:41 am
content: I'm starting a new thread as a follow-up of the discussions onSiglent HDandRigol DHO800/900models 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 onthe 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 theWindows (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 !12/13/2024 UpdateRigol DHO : added support for DHO824 model08/26/2024 UpdateSiglent SDS : fixed support for sub 10mV vertical ranges08/07/2024 UpdateRigol DHO : added support for DHO1000 and DHO400008/04/2024 UpdateSiglent 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 Mpts08/01/2024 UpdateSiglent SDS :- Fixed pagination for memory depth > 4 Mpts (issue where the waveform was truncated and replicated)07/27/2024 UpdateSiglent SDS :- Fixed acquisition for memory depth > 4 MptsRigol DHO :- Fixed USB acquisition07/22/2024 UpdateAdded 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 lowerI'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

author: kripton2035
author_rank: Super Contributor
timestamp: June 27, 2024, 12:08:56 pm
content: 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.

author: TomKatt
author_rank: Frequent Contributor
timestamp: June 27, 2024, 01:10:24 pm
content: 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'sSigScopeLabsoftware 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.

author: fredo_
author_rank: Regular Contributor
timestamp: June 27, 2024, 05:01:03 pm
content: Quote from: kripton2035 on June 27, 2024, 12:08:56 pmWell that's another story!... You need a Mac and MacOS to do that, which I don't have :-(Quote from: TomKatt on June 27, 2024, 01:10:24 pmThanks TomKatt !Quote from: TomKatt on June 27, 2024, 01:10:24 pmWell 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 codebaseQuote from: TomKatt on June 27, 2024, 01:10:24 pmWell 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...

author: Spike
author_rank: Regular Contributor
timestamp: June 27, 2024, 05:47:39 pm
content: Quote from: fredo_ on June 27, 2024, 05:01:03 pmI 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.

author: Spike
author_rank: Regular Contributor
timestamp: June 27, 2024, 07:08:51 pm
content: Quote from: TomKatt on June 27, 2024, 01:10:24 pmI 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 mergedthena fork would seem in order.QuoteUnfortunately 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.

author: kripton2035
author_rank: Super Contributor
timestamp: June 28, 2024, 07:03:05 pm
content: Quote from: Spike on June 27, 2024, 05:47:39 pmAs chatgpt for macos desktop works only on sonoma+, I think this will convince me to upgrade very soon ...

author: kripton2035
author_rank: Super Contributor
timestamp: June 28, 2024, 07:05:53 pm
content: 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 ...

author: dpenev
author_rank: Regular Contributor
timestamp: June 29, 2024, 07:02:54 am
content: 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?

author: kripton2035
author_rank: Super Contributor
timestamp: June 29, 2024, 07:08:15 am
content: 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

author: Spike
author_rank: Regular Contributor
timestamp: June 29, 2024, 08:10:06 am
content: Quote from: dpenev on June 29, 2024, 07:02:54 amThis 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?

author: dpenev
author_rank: Regular Contributor
timestamp: June 29, 2024, 02:51:13 pm
content: Sorry, my oscilloscope is actually SDS2000X Plus family.

author: Spike
author_rank: Regular Contributor
timestamp: June 29, 2024, 05:48:14 pm
content: Quote from: dpenev on June 29, 2024, 02:51:13 pmThe 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.

author: fredo_
author_rank: Regular Contributor
timestamp: June 29, 2024, 06:03:23 pm
content: 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 windowThanks for your help !

author: kripton2035
author_rank: Super Contributor
timestamp: July 01, 2024, 06:31:45 am
content: @Spike, I'm now on Sonoma, so tests can go further ! thanks.

author: Spike
author_rank: Regular Contributor
timestamp: July 02, 2024, 12:38:29 am
content: Quote from: kripton2035 on July 01, 2024, 06:31:45 amPM sent

author: Frex
author_rank: Regular Contributor
timestamp: July 02, 2024, 08:32:23 am
content: 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

author: Frex
author_rank: Regular Contributor
timestamp: July 02, 2024, 09:07:24 am
content: 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

author: fredo_
author_rank: Regular Contributor
timestamp: July 02, 2024, 09:37:07 am
content: 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/#msg5558089Just PM me if you need assistance in French ! :-)

author: Frex
author_rank: Regular Contributor
timestamp: July 03, 2024, 06:26:26 am
content: 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

author: fredo_
author_rank: Regular Contributor
timestamp: July 03, 2024, 09:04:15 pm
content: Great, thanks Frex !That confirms my hypothesis.I'll prepare a fix when I come back home by the end of next week.

author: Lathe26
author_rank: Contributor
timestamp: July 06, 2024, 10:09:58 pm
content: 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.

author: fredo_
author_rank: Regular Contributor
timestamp: July 07, 2024, 04:36:34 pm
content: 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

author: Lathe26
author_rank: Contributor
timestamp: July 08, 2024, 01:19:11 am
content: I am willing to try it out once Rigol fixes their LA bug.

author: fredo_
author_rank: Regular Contributor
timestamp: July 18, 2024, 10:17:40 pm
content: Hi folks !Back from a beautiful journey in Scotland, I patched the installer to try and fix the read timing issuesLink 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 SeriesSDS 1000X HD SeriesSDS 2000X HD SeriesSDS 3000X HD SeriesSDS 5000X SeriesSDS 6000L SeriesSDS 6000A SeriesSDS 6000 Pro SeriesSDS 7000A SeriesBest,Frederic.

author: teddychn
author_rank: Regular Contributor
timestamp: July 21, 2024, 08:39:45 am
content: 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!

author: Electro Fan
author_rank: Super Contributor
timestamp: July 21, 2024, 09:17:43 pm
content: Quote from: fredo_ on July 18, 2024, 10:17:40 pmIt is very impressive and valuable what you and the other contributors are doing with this project!Thanks!

author: fredo_
author_rank: Regular Contributor
timestamp: July 22, 2024, 10:20:14 am
content: Quote from: teddychn on July 21, 2024, 08:39:45 amThanks for the feedback @teddychn !I'm almost done with Rigol DHO800/900 support (thanks to the work previously done by Diana Ellefson (OrionOth) and RemiNVhere).I'll switch back to Siglent SDS2000X HD to try and reproduce your problem right after that.

author: fredo_
author_rank: Regular Contributor
timestamp: July 22, 2024, 08:52:11 pm
content: ~~~ 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 lowerAny feedback is welcome, especially from DHO 900 owners !

author: Furna
author_rank: Frequent Contributor
timestamp: July 23, 2024, 04:58:34 pm
content: Quote from: fredo_ on July 18, 2024, 10:17:40 pmI will try ASAP with my Siglent SDS824X HD and report here.I was starting to work on this (seehttps://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!

author: fredo_
author_rank: Regular Contributor
timestamp: July 27, 2024, 03:55:54 pm
content: Hi guys,I just updated the patch with the following changes:07/27/2024 UpdateSiglent 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 MptsRigol DHO :- Fixed USB acquisitionLink 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.

author: Spike
author_rank: Regular Contributor
timestamp: July 27, 2024, 09:00:33 pm
content: Quote from: fredo_ on July 27, 2024, 03:55:54 pmAre you planning to keep the Siglent and Rigol support on separate branches from now on or will this get merged onto your master?

author: fredo_
author_rank: Regular Contributor
timestamp: July 27, 2024, 10:03:52 pm
content: Quote from: Spike on July 27, 2024, 09:00:33 pmI 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 froma PR on sigrok repository, but it's a Windows only fix, so no worries.

author: Spike
author_rank: Regular Contributor
timestamp: July 27, 2024, 10:05:00 pm
content: Quote from: fredo_ on July 27, 2024, 10:03:52 pmExcellent! Thank you very much.

author: Spike
author_rank: Regular Contributor
timestamp: July 27, 2024, 10:09:35 pm
content: Quote from: Spike on July 27, 2024, 10:05:00 pmDid you push those back up? I'm not seeing it.

author: fredo_
author_rank: Regular Contributor
timestamp: July 27, 2024, 10:58:57 pm
content: Quote from: Spike on July 27, 2024, 10:09:35 pmSorry, forgot to push, that should be good now!

author: Spike
author_rank: Regular Contributor
timestamp: July 27, 2024, 11:08:02 pm
content: Quote from: fredo_ on July 27, 2024, 10:58:57 pmGot it now. Thanks again.

author: Spike
author_rank: Regular Contributor
timestamp: July 27, 2024, 11:28:56 pm
content: Quote from: Spike on July 27, 2024, 11:08:02 pmHitting this while trying to compile the rigol stuff:Code:CC src/hardware/rigol-ds/api.lo/Users/gcorral/Documents/Source/sigrok/libsigrok/src/hardware/rigol-ds/api.c:1038:4: error: expected expressionint 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.

author: fredo_
author_rank: Regular Contributor
timestamp: July 27, 2024, 11:51:06 pm
content: Quote from: Spike on July 27, 2024, 11:28:56 pmYep, not sure why my compiler did not complain... I pushed the fix.

author: Spike
author_rank: Regular Contributor
timestamp: July 28, 2024, 12:00:07 am
content: Quote from: fredo_ on July 27, 2024, 11:51:06 pmLooks good, thanks!

author: teddychn
author_rank: Regular Contributor
timestamp: July 28, 2024, 02:35:32 am
content: Quote from: fredo_ on July 27, 2024, 03:55:54 pmHi 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

author: Furna
author_rank: Frequent Contributor
timestamp: July 28, 2024, 08:13:33 pm
content: 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.

author: Frex
author_rank: Regular Contributor
timestamp: July 31, 2024, 06:30:15 am
content: 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

author: fredo_
author_rank: Regular Contributor
timestamp: August 01, 2024, 06:52:28 pm
content: Hi guys,Quote from: Frex on July 31, 2024, 06:30:15 amWell 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 UpdateSiglent 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 MptsThis 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 contentwith 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.

author: Furna
author_rank: Frequent Contributor
timestamp: August 01, 2024, 06:58:50 pm
content: Quote from: fredo_ on August 01, 2024, 06:52:28 pmYou might want to checkhttps://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.

author: Spike
author_rank: Regular Contributor
timestamp: August 01, 2024, 11:44:38 pm
content: Quote from: fredo_ on August 01, 2024, 06:52:28 pmAny chance this could be merged to master?

author: fredo_
author_rank: Regular Contributor
timestamp: August 02, 2024, 06:39:21 am
content: Quote from: Spike on August 01, 2024, 11:44:38 pmDone !@Spike if you have working Mac build, maybe you could share it here ?

author: Frex
author_rank: Regular Contributor
timestamp: August 02, 2024, 08:25:31 am
content: Hekko Fredo and all,Renaming model name in dialog list is a good ideaThat 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

author: fredo_
author_rank: Regular Contributor
timestamp: August 02, 2024, 09:41:43 am
content: 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...

author: Frex
author_rank: Regular Contributor
timestamp: August 02, 2024, 02:14:03 pm
content: 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

author: Spike
author_rank: Regular Contributor
timestamp: August 03, 2024, 12:29:42 am
content: Quote from: fredo_ on August 02, 2024, 06:39:21 amSure, here's something:https://www.dropbox.com/scl/fo/7fp3toladqj5fz16ugp8w/AImd1yuWyACIZ1nnTrm9-rk?rlkey=be64qo1o3ppvu24sbm05s8rxu&dl=0The dmg doesn't explicitly say it but the arm64 will only run on Sonoma and the x86_64 is for Ventura.

author: fredo_
author_rank: Regular Contributor
timestamp: August 03, 2024, 11:31:47 am
content: Quote from: Frex on August 02, 2024, 02:14:03 pmThanks for that Frex! I just sent you a PM to investigate your problem.Quote from: Spike on August 03, 2024, 12:29:42 amGreat ! 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 ?

author: Spike
author_rank: Regular Contributor
timestamp: August 03, 2024, 04:34:37 pm
content: Quote from: fredo_ on August 03, 2024, 11:31:47 amNope. 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.

author: Furna
author_rank: Frequent Contributor
timestamp: August 04, 2024, 12:07:34 pm
content: Quote from: fredo_ on July 27, 2024, 03:55:54 pmWorking OK on SDS8024X HDAlso multi channel acquisition is working

author: kripton2035
author_rank: Super Contributor
timestamp: August 04, 2024, 12:51:38 pm
content: Quoteseems 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)

author: kripton2035
author_rank: Super Contributor
timestamp: August 04, 2024, 12:57:09 pm
content: it also seems to work with a 200Mpts acquisition...

author: fredo_
author_rank: Regular Contributor
timestamp: August 04, 2024, 10:08:09 pm
content: Thank you @Furna and @kripton2035 for the feedback, glad to know that it starts working !Quote from: kripton2035 link=topic=432887.msg5593343#msg5593343 date=1722775 reached out to me privately. You’d have to ask them if there are issues.[/quoteThat'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 UpdateSiglent 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 MptsI 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!

author: skander36
author_rank: Frequent Contributor
timestamp: August 04, 2024, 10:44:41 pm
content: It seem to work also with SDS1000X-HD.I can't connect to DHO1000X-HD.

author: fredo_
author_rank: Regular Contributor
timestamp: August 04, 2024, 11:06:45 pm
content: Quote from: skander36 on August 04, 2024, 10:44:41 pmGreat, thank you for the feedback @skander36 !Quote from: skander36 on August 04, 2024, 10:44:41 pmThat'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 (seehere)

author: skander36
author_rank: Frequent Contributor
timestamp: August 05, 2024, 09:05:04 am
content: Thank you very much for your work.Quote from: fredo_ on August 04, 2024, 11:06:45 pmRIGOL TECHNOLOGIES,DHO1074,HDO1B244401552,00.02.13For 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.

author: fredo_
author_rank: Regular Contributor
timestamp: August 05, 2024, 01:57:41 pm
content: Quote from: fredo_ on August 01, 2024, 06:52:28 pmJust a quick update on this , I got the following reply from Siglent support :QuoteWait and see !...

author: skander36
author_rank: Frequent Contributor
timestamp: August 07, 2024, 11:59:56 am
content: Quote from: fredo_ on August 04, 2024, 11:06:45 pmSCPI - USB0::0x1AB1::0x0610::HDO1B244401552::INSTRLSUSB - Bus 002 Device 006: ID 1ab1:0610 Rigol Technologies HDO1074Windows Device Manager - USB\VID_1AB1&PID_0610\HDO1B244401552

author: fredo_
author_rank: Regular Contributor
timestamp: August 07, 2024, 03:48:16 pm
content: Quote from: skander36 on August 07, 2024, 11:59:56 amThanks @skander36And 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 ?

author: Spike
author_rank: Regular Contributor
timestamp: August 07, 2024, 09:07:28 pm
content: Quote from: fredo_ on August 07, 2024, 03:48:16 pmApologies 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.

author: thm_w
author_rank: Super Contributor
timestamp: August 08, 2024, 12:11:22 am
content: Quote from: fredo_ on August 07, 2024, 03:48:16 pmThank 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.

author: fredo_
author_rank: Regular Contributor
timestamp: August 08, 2024, 07:39:36 am
content: Quote from: thm_w on August 08, 2024, 12:11:22 amThank you @thm_w, that's good news !

author: neodimio91
author_rank: Newbie
timestamp: August 08, 2024, 11:35:00 am
content: @_fredo , I'm a sds2104x plus owner, everything seems to work perfectly with new updates, feel free to reach me for any testing !

author: fredo_
author_rank: Regular Contributor
timestamp: August 08, 2024, 10:09:15 pm
content: Quote from: neodimio91 on August 08, 2024, 11:35:00 amThanks for the feedback @neodimio91 !

author: Spike
author_rank: Regular Contributor
timestamp: August 08, 2024, 10:32:46 pm
content: Quote from: Spike on August 07, 2024, 09:07:28 pmUpdated Mac builds available at the link provided previously.

author: Frex
author_rank: Regular Contributor
timestamp: August 14, 2024, 04:19:31 pm
content: Hello fredo_,As others, I also have run successfully you last version with bothSiglent 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 acquisitionand 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 PulseViewdoesn't support it even it is displayed in configure channel top menu.Best regards,Frex

author: skander36
author_rank: Frequent Contributor
timestamp: August 14, 2024, 09:37:12 pm
content: Quote from: fredo_ on August 07, 2024, 03:48:16 pmHello!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!

author: fredo_
author_rank: Regular Contributor
timestamp: August 15, 2024, 10:16:11 am
content: Thanks for the feedback @Frex and @skander36 !Quote from: Frex on August 14, 2024, 04:19:31 pmThat'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).Quote from: Frex on August 14, 2024, 04:19:31 pmThat I should be able to fix, I'll take a look.Quote from: skander36 on August 14, 2024, 09:37:12 pmYeah 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.

author: dpenev
author_rank: Regular Contributor
timestamp: August 16, 2024, 09:34:52 am
content: 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 shown3. On pressing Run again I get "Capture Failed"Any comments?

author: Furna
author_rank: Frequent Contributor
timestamp: August 16, 2024, 09:44:44 am
content: Quote from: dpenev on August 16, 2024, 09:34:52 amYes, correct connection parameterQuote from: dpenev on August 16, 2024, 09:34:52 amI'll try to replicate ASAP (could take long) ... meanwhile you might want to capture some logs.Seehttps://www.eevblog.com/forum/testgear/new-sigrokpulseview-hardware-support-(siglent-sds-hd-rigol-dho800-)/msg5558089/#msg5558089

author: Frex
author_rank: Regular Contributor
timestamp: August 16, 2024, 12:14:46 pm
content: Quote from: fredo_ on August 15, 2024, 10:16:11 amHello fredo, you're welcomeThat would be great !Thank you for all your efforts and the detailed answers.Regards.Frex

author: dpenev
author_rank: Regular Contributor
timestamp: August 16, 2024, 01:09:13 pm
content: 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/1000000sr: 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/divWAV:MAXP? if sent separately to the oscilloscope returns 10000000 but I don't see it in the log.

author: Furna
author_rank: Frequent Contributor
timestamp: August 16, 2024, 04:11:12 pm
content: Quote from: dpenev on August 16, 2024, 01:09:13 pmCan you try with a different resolution? I was succesfull with 10mV/div with SDS824X HDSee alsohttps://www.eevblog.com/forum/testgear/new-sigrokpulseview-hardware-support-(siglent-sds-hd-rigol-dho800-)/msg5605601/#msg5605601With SDS2104X+ it is not possible to go lower than 10mV/div and fredo_ is looking at it.

author: dpenev
author_rank: Regular Contributor
timestamp: August 17, 2024, 12:40:08 pm
content: 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=64Reply from 192.168.1.6: bytes=32 time<1ms TTL=64Reply from 192.168.1.6: bytes=32 time<1ms TTL=64Reply from 192.168.1.6: bytes=32 time<1ms TTL=64

author: fredo_
author_rank: Regular Contributor
timestamp: August 17, 2024, 12:57:16 pm
content: Hi @dpenev and thank you for your investigations !Quote from: dpenev on August 17, 2024, 12:40:08 pmNo 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 ?

author: fredo_
author_rank: Regular Contributor
timestamp: August 17, 2024, 10:34:10 pm
content: 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.

author: fredo_
author_rank: Regular Contributor
timestamp: August 26, 2024, 09:20:58 pm
content: Quote from: Frex on August 16, 2024, 12:14:46 pmHi 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 UpdateSiglent SDS : fixed support for sub 10mV vertical ranges

author: Spike
author_rank: Regular Contributor
timestamp: August 26, 2024, 10:49:07 pm
content: Quote from: fredo_ on August 26, 2024, 09:20:58 pmUpdated macOS builds available; see first post for link.

author: hansibull
author_rank: Regular Contributor
timestamp: August 30, 2024, 07:50:23 am
content: Amazing work! What are the odds of getting your fork merged into the official Sigrok repo? I have been using Sigrok'slibserialport 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.

author: fredo_
author_rank: Regular Contributor
timestamp: August 30, 2024, 09:05:45 am
content: Quote from: hansibull on August 30, 2024, 07:50:23 amThanks !Well I created the two PRs yesterday, now that things seem quite stable:https://github.com/sigrokproject/libsigrok/pull/245https://github.com/sigrokproject/libsigrok/pull/246So wait and see !...

author: Furna
author_rank: Frequent Contributor
timestamp: August 30, 2024, 11:09:43 am
content: Quote from: fredo_ on August 05, 2024, 01:57:41 pmAny update from Siglent ?

author: Furna
author_rank: Frequent Contributor
timestamp: August 30, 2024, 11:10:28 am
content: Quote from: fredo_ on August 30, 2024, 09:05:45 amLet us know if we can sponsor your PR

author: fredo_
author_rank: Regular Contributor
timestamp: August 30, 2024, 11:53:00 am
content: Quote from: Furna on August 30, 2024, 11:09:43 amYes 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).Quote from: Furna on August 30, 2024, 11:10:28 amFor now I'm trying to reach out to project committers on the dedicated Discord channel...

author: hansibull
author_rank: Regular Contributor
timestamp: August 30, 2024, 01:25:09 pm
content: 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.

author: Spike
author_rank: Regular Contributor
timestamp: August 30, 2024, 05:34:07 pm
content: Quote from: fredo_ on August 30, 2024, 09:05:45 amThe 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.

author: wiretail
author_rank: Newbie
timestamp: September 21, 2024, 09:40:55 am
content: 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.)

author: fredo_
author_rank: Regular Contributor
timestamp: September 21, 2024, 09:48:05 am
content: Quote from: wiretail on September 21, 2024, 09:40:55 amThanks 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 ;-)

author: fredo_
author_rank: Regular Contributor
timestamp: September 25, 2024, 09:22:01 pm
content: Quote from: Furna on August 30, 2024, 11:09:43 amI just received a confirmation from Siglent support that they could reproduce the bug and that they are working on a fix !

author: Furna
author_rank: Frequent Contributor
timestamp: September 25, 2024, 09:24:25 pm
content: Quote from: fredo_ on September 25, 2024, 09:22:01 pmThank you for the update!

author: qubit
author_rank: Newbie
timestamp: October 13, 2024, 05:07:33 am
content: I've just been scrolling through the open pull requests on github and there is actually someone working on fixing the Siglent SDS E-series driver, awesome!Here's the link to the PR:https://github.com/sigrokproject/libsigrok/pull/247Anyone with an E/U-series oscilloscope can help with testing the driver, and anyone with a 1000X/2000X series scope can help with regression testing@fredo_ if you have time, could you please kindly share a compiled version of the PR247 so that we can test the changes? I'm still not able to get the building process working

author: fredo_
author_rank: Regular Contributor
timestamp: October 14, 2024, 10:25:15 am
content: Quote from: qubit on October 13, 2024, 05:07:33 amHi @qubit,Yes I'm aware of this PR and already proposed to merge it with mine on Sigrok Discord channel.They are preparing a release and plan to integrate some PRs to it, Rigol and Siglent driver update PRs (245,246,247) are candidate for it:https://sigrok.org/wiki/Developers/Release_0.8.0TBH I'm not spending more time on it until I'm sure this eventually make its way to upstream ; I moved to another project (ngscopeclient) for now.I can try and guide you to have your build work thought, what platform are you using?

author: DirtySignal
author_rank: Newbie
timestamp: October 14, 2024, 01:41:46 pm
content: Quote from: qubit on October 13, 2024, 05:07:33 amI have a DSD1104X-E... do you have a link for a test binary on Windows? Thanks

author: fredo_
author_rank: Regular Contributor
timestamp: October 14, 2024, 01:46:31 pm
content: Quote from: DirtySignal on October 14, 2024, 01:41:46 pmYes you'll find a link in the first page of this topic :https://www.eevblog.com/forum/testgear/new-sigrokpulseview-hardware-support-(siglent-sds-hd-rigol-dho800-)/Please report the results of your tests here as it will help validate the corresponding Pull Request and merge the code to Sigrock upstream.

author: DirtySignal
author_rank: Newbie
timestamp: October 14, 2024, 01:49:23 pm
content: Quote from: fredo_ on October 14, 2024, 01:46:31 pmI think I was not clear enough, apologies - I meant a test binary for the PR mentioned in the previous post. I've tested the binary you provided in the first post but sigrok hangs when trying to acquire anything from the scope... so I wanted to test that PR which seems to be a fix for that issue specifically.I had a look at building from source but it looks a little complicated for a background activity at the moment...

author: fredo_
author_rank: Regular Contributor
timestamp: October 14, 2024, 02:45:41 pm
content: Oh no sorry it's me who misread your model number, I thought it was an old Rigol.I don't have a binary for PR #247, sorry, maybe you should get in touch with its author for that ?:https://github.com/mike42

author: DirtySignal
author_rank: Newbie
timestamp: October 14, 2024, 02:52:26 pm
content: Quote from: fredo_ on October 14, 2024, 02:45:41 pmThanks, I fired up a WSL session busy building the dev environment, let's see how far I getedit: Windows 32bit and 64bit binary built successfully for that PR

author: qubit
author_rank: Newbie
timestamp: October 15, 2024, 12:31:56 pm
content: Quote from: fredo_ on October 14, 2024, 10:25:15 amI am trying to build for Windows 11. I am using MSYS2/Mingw64 and the sigrok-native-msys2 script from sigrok-utilhttps://github.com/sigrokproject/sigrok-util/blob/master/cross-compile/msys2/sigrok-native-msys2. I've changed a few lines in this script.I've changed the git repository for libusb to point to the official libsusb repo's master branch, the libsikrok repo to the siglent-sds branch of mike42's repository and the repository of pulseview to the Fix/71 branch as described in the pull request PR247https://github.com/sigrokproject/libsigrok/pull/247.I can build pulseview sucessfully and also run it from within a Ming64 terminal.When running pulseview from MinGW64 I get a lot of python ModuleNotFoundErrors in the console output: No module named 'math', No module named 'binascii'. These are internal modules of python, so they shouldn't have to be installed. Is there maybe something wrong with the python installation?When I try to run the pulseview.exe executable from within Windows I get error messages:The procedure entry point _Z20qResourceFeatureZlibv count not be located in the dynamic link library, hinting at a problem with the Qt5 dlls. I guess that when running from within MinGW64, the PATH variable points to the correct locations of Qt5Core.dll and all required dlls.When I run the commandCode:ldd ./pulseview.exeI can see that Qt5Core.dll will be loaded from /mingw64/bin/Qt5Core.dll, as well as a lot of other dlls that also will be loaded from /mingw64/bin/.How can I compile Qt5 into the pulseview executable statically, so that running pulseview.exe from within Windows does work? Did you also run into such problems?

author: DirtySignal
author_rank: Newbie
timestamp: October 15, 2024, 01:34:31 pm
content: I don't know about compiling native using MSYS2/Mingw64 - I managed to compile using the cross mingw compile under Linux but I had to do many things that I hope I can retrace now for later use to get it all done and among that was having to create the installer after the build completed which bundles all the dependencies for Windows using makensis. It might be that you will need to do something similar. In the meantime we're hijacking this thread a little off-label...

author: fredo_
author_rank: Regular Contributor
timestamp: October 15, 2024, 04:03:28 pm
content: Quote from: qubit on October 15, 2024, 12:31:56 pmYep that's "normal", I never got native build to run as a standalone exe either, it only works when launched from MinGW64 shell.You need Linux cross compilation like @DirtySignal said to generate an installer that can work standalone.Other option might be to use github actions from sigrok-build project:https://github.com/sigrokproject/sigrok-build/actions/

author: ttelectronic
author_rank: Regular Contributor
timestamp: October 19, 2024, 03:32:57 am
content: Thanks for the work on this!I am able to get it to work ok on the displayed data. Apologies I'm not real familiar with pulseview. I'm trying to pull data from history on my SDS824X HD, I am only able to pull the displayed data.So I'm not sure if I'm misunderstanding this feature in pulse view, or whether its not working for this scope.

author: tautech
author_rank: Super Contributor
timestamp: October 19, 2024, 04:28:25 am
content: Quote from: ttelectronic on October 19, 2024, 03:32:57 amPlease see History use examples here:https://www.eevblog.com/forum/testgear/sds800x-hd-review-demonstration-thread/msg5293747/#msg5293747

author: chris178
author_rank: Contributor
timestamp: December 02, 2024, 03:20:47 pm
content: Thank you @fredo_ for this implementation - great work, very impressive.Recently I've upgraded my DHO804 to DHO824. It seems device is no longer recognized while trying to connect.I take it might be due to DHO824 not being on the supported models list?

author: fredo_
author_rank: Regular Contributor
timestamp: December 02, 2024, 04:01:03 pm
content: Oh yes, that's very likely the case !...I'll see what I can do.

author: fredo_
author_rank: Regular Contributor
timestamp: December 19, 2024, 04:58:14 pm
content: I just uploaded a new version for DHO824 support:Windows (64bits) installer (zip password is 'sigrok').12/13/2024 UpdateRigol DHO : added support for DHO824 model

author: enoch247
author_rank: Contributor
timestamp: December 21, 2024, 08:17:55 pm
content: I have a SDS1104X-E. I just tried Pulseview (installed via apt on Ubuntu). I can connect to it over Ethernet, but anytime I initiate a capture, Pulseview hangs. Surprisingly the version in my OS's repo looks like it is the most current (0.4.2). Is there any experiment I can perform to help the effort in this thread to better support theses scopes?

author: tautech
author_rank: Super Contributor
timestamp: December 21, 2024, 08:21:21 pm
content: Quote from: enoch247 on December 21, 2024, 08:17:55 pmThis is certainly not the case when using the inbuilt webserver Save Screenshot.Have you tried it ?

author: Furna
author_rank: Frequent Contributor
timestamp: December 21, 2024, 09:17:04 pm
content: Quote from: enoch247 on December 21, 2024, 08:17:55 pmThe Sigrok/Pulseview website is quite clear: use the Nightly Buildshttps://sigrok.org/wiki/DownloadsThose are the "recomended always up to date" as opposed to the release "might be missing features or bugfixes).Welcome to Sigrok community

author: enoch247
author_rank: Contributor
timestamp: December 22, 2024, 01:34:56 pm
content: Thanks for the tip. I just tried the nightly appimage build. Same issue though Pulseview just hangs once the capture is started. It gets stuck in a loop dumping the following error to the console:Code:WARNING: Received analog packet with 0 samples.For those who have gotten this working, I'd love to know what is different about my setup.

author: Furna
author_rank: Frequent Contributor
timestamp: December 24, 2024, 05:36:41 pm
content: Quote from: enoch247 on December 22, 2024, 01:34:56 pmTry this way:- Setup the scope to measure a signal with Auto trigger (the scope draws continuously the signal on the display)- Hit the "Run" button in SigrokThe scope will stop the acquisition and data is transferred to Pulseview.

author: enoch247
author_rank: Contributor
timestamp: December 31, 2024, 11:41:52 am
content: QuoteThis is what I did. The scope does respond by stopping the capture, but the data of the captured waveform never seems to make it over to the PC.

author: Furna
author_rank: Frequent Contributor
timestamp: December 31, 2024, 12:11:48 pm
content: Quote from: enoch247 on December 31, 2024, 11:41:52 amUnfortunately, I don't own an SDS1104X-E so I can't really help more than giving my best guess. Did you upgrade your scope firmaware?Check with a network analyzer (i.e. Wireshark) what is going on ... the "WARNING analog packet with 0 samples" makes me think of a firmware bug ... the scope send empty waveform?If you need the wavefrom's data in a PC without loosing too much time, you can try to export the waveform using SigScopeLab software available for free on Siglent web site.

author: Furna
author_rank: Frequent Contributor
timestamp: January 03, 2025, 06:37:54 pm
content: @enoch247: you might want to try thishttps://github.com/geekman/siglent-bin2srIt is supposed to convert bin form of a waveform directly to Sigrok/PulseView

author: sal0ne
author_rank: Newbie
timestamp: January 04, 2025, 12:25:14 am
content: @fredo_ I compiled your fork on Fedora Linux and confirm its working with my Siglent SDS2104X Plus.Nice work, its a shame the upstream project is slow/reluctant to merge PR's.

author: enoch247
author_rank: Contributor
timestamp: January 04, 2025, 02:39:15 am
content: Quote from: Furna on January 03, 2025, 06:37:54 pmThanks!

author: Kurt_!
author_rank: Regular Contributor
timestamp: April 02, 2025, 11:19:24 am
content: Should this software also work on my DHO1104?I selected the driver (Rigol DS/DHO).Unfortunately, no luck!Can anyone help?

author: skander36
author_rank: Frequent Contributor
timestamp: April 02, 2025, 12:58:15 pm
content: Quote from: Kurt_! on April 02, 2025, 11:19:24 amHi! If you are talking about DHO1104X-HD it should work. My 1074X-HD used to work.Please check this post for Zadig settings -https://www.eevblog.com/forum/testgear/new-sigrokpulseview-hardware-support-(siglent-sds-hd-rigol-dho800-)/msg5597367/#msg5597367

author: Langdon
author_rank: Frequent Contributor
timestamp: April 02, 2025, 01:22:22 pm
content: I wish it was GPL v2 or some other license.The GPL v3 is a bit too restrictive for my liking.The pursuit of "freedom" lead to control.(Along with most everything else.)

author: Furna
author_rank: Frequent Contributor
timestamp: April 02, 2025, 04:23:54 pm
content: Quote from: skander36 on April 02, 2025, 12:58:15 pmAlso be sure to use binaries provided in the first post of this topic; AFAIK fredo_ contribution has not yet been published in the main project.

author: fredo_
author_rank: Regular Contributor
timestamp: April 02, 2025, 04:39:35 pm
content: Quote from: Furna on April 02, 2025, 04:23:54 pmSadly, I can confirm that my Pull Request has not yet been merged to the main project...

author: Kurt_!
author_rank: Regular Contributor
timestamp: April 02, 2025, 05:02:48 pm
content: It's already working...It's already recognized it.Now I have to play around with the program a bit.

author: Spike
author_rank: Regular Contributor
timestamp: April 02, 2025, 05:30:53 pm
content: Quote from: fredo_ on April 02, 2025, 04:39:35 pmIt has only been 7 months, fredo_, it’s going to take a bit longer for a dead project to merge your changes. If your changes ever get merged I’ll be quite shocked.

author: mwb1100
author_rank: Frequent Contributor
timestamp: April 02, 2025, 10:11:22 pm
content: Quote from: Langdon on April 02, 2025, 01:22:22 pmYou might be planning to incorporate GLPed software into some other project or product. But in case you just want to use GPLed software, note that the GPL (neither V2 or v3) impose any requirements onusers. The requirements only kick in when youdistributeGPLed software:Quote from:https://www.gnu.org/licenses/gpl-faq.html#ClickThrough

author: Langdon
author_rank: Frequent Contributor
timestamp: April 03, 2025, 12:35:35 pm
content: So I can like use GPL v3 code in an MIT-licensed project without issue so long as I don't distribute it?Makes sense, I guess.But I still dislike the v3.v2 is fine tho.Not perfect, but fine; legal stuff is always somewhat stupid and imperfect.

author: mwb1100
author_rank: Frequent Contributor
timestamp: April 03, 2025, 06:28:56 pm
content: Quote from: Langdon on April 03, 2025, 12:35:35 pmYes.But AFAIK the MIT license is compatible with both GPL 2 and GPL 3. With both versions of the GPL you can incorporate MIT licensed code, it's just that if you distribute the project you must make both the GPL'ed code and the MIT licensed code available. That's OK since releasing the MIT code is fine (it's just that you're under no obligation to if it's not GPL 'infected').In fact, GNU explicitly states that the MIT license (they call it the "Expat" license - first time I've heard that name) is GPL compatible:Quote from:https://directory.fsf.org/wiki/License:ExpatAnyway, there's nothing that says you have to like the GPL 3. I just want to put the information out there.Disclaimer: IANAL

author: enoch247
author_rank: Contributor
timestamp: April 03, 2025, 11:04:10 pm
content: What does v3 have that you do not like that v2 did not have?

author: tatel
author_rank: Frequent Contributor
timestamp: April 23, 2025, 08:31:47 am
content: This link comes from sigrok-devel mailing list, where I have been lurking for a couple years:https://github.com/sigrokproject/libsigrok/graphs/contributorsSince what I have is a DSLogic, sigrok situation doesn't affect me. What DSLabs provides is all I need. But, should I been into developing new things for sigrok/pulseview, I would probably think about forking.With my best wishes for this interesting project

author: mwb1100
author_rank: Frequent Contributor
timestamp: April 23, 2025, 04:50:05 pm
content: More to the point:[sigrok-devel] Is sigrok dead?Also from the thread:Quote from:https://sourceforge.net/p/sigrok/mailman/message/59176185/

author: dzungpham0703
author_rank: Newbie
timestamp: May 22, 2025, 02:45:46 pm
content: I have DH914s, LAN mode partly working but USB mode is not, I am running PulseView build here on Apple M2 Max, Mac OS 15.4.1.Live view never work for me, but the memory mode work.About the timing, it will be wrong for the first time, then I press start/stop 2 or 3 time and it will match the time on the dho914s.Usb mode show error: Capture failed, generic/unspecified error.My DHO running latest official version: 00.01.04