Oscilloscope Network Capture - grab images from your scope via network - Page 1
Forum section: electronics / testgear

author: Beauvais7165
author_rank: Contributor
timestamp: October 03, 2025, 05:33:52 pm
content: From a previous forum post inGeneral>General Technical ChatI have shared a Windows application, which is able to grab images from the scope via network. I quickly found out my implementation was very poor handling other scopes than my own, but to fair this was actually not the intention from the beginning, as I just wanted something for my self. To make a long story short, then I have now rewritten the application entirely, to be multi-vendor/model capable and use only proper SCPI commands.However, my plea here is, that I really could use some help with a quick validation test, if this actually works in reality, and not only with myRigol DS2202Ascope.You can download the application with version2025-October-3from here,https://github.com/HovKlan-DH/Oscilloscope-Network-Capture/releasesI then kindly would like to draw your attention to the step-by-step guide here,https://github.com/HovKlan-DH/Oscilloscope-Network-Capture?tab=readme-ov-file#supported-scopes, and I really would appreciate if you would test this on your scope and then just send the result to me, via theDebugtab. If you would like help getting additional scopes supported, this would even better

author: PlainName
author_rank: Super Contributor
timestamp: October 03, 2025, 06:25:35 pm
content: Blinding!Had to set the IP but then it Just Worked. Kind of...Initially it wouldn't capture when I pressed enter. Only after a few tries did I discover that pressing the 'Check oscilloscope...' button left the focus on it, so hitting enter just repeated the check. Interestingly, even with focus on the capture folder editbox, enter does capture!I'm lost as to what capture mode is. In settings I have force acquisition after capture ticked, but what does that do? Whether it is ticked or not, I press enter and get a nice picture, nothing if I don't.Other than that it works well. Quicker than the last one! Just one small snagette which I doubt you can do anything about: after a capture there is a message "Remote operation completed" which shows on the scope screen, and another capture before that's removed captures that message too. Once would think that stuff like that would be overlayed on the actual screen so it's not part of the image, but there you go.Nice one

author: PlainName
author_rank: Super Contributor
timestamp: October 03, 2025, 06:31:19 pm
content: Controls:All seem to work to spec. Trigger level and single/resume work. Zooming (TIME/DIV) too.

author: Beauvais7165
author_rank: Contributor
timestamp: October 03, 2025, 06:41:37 pm
content: Quote from: PlainName on October 03, 2025, 06:25:35 pmAhhh, thanks a lot for the feedback - did not notice this, but is easy to put focus somewhere else after pushing this button.Quote from: PlainName on October 03, 2025, 06:25:35 pm"Force acquisition after capture". Consider this - you are fiddling with your scope, and you may be in STOP mode, because you have found the signal you want to save - then after the image has been captured, then the scope will again resume acquisition, so you do not manually need to do it.Quote from: PlainName on October 03, 2025, 06:25:35 pmI am sorry to hear that, but I doubt this is something that can be controlled via SCPI commands? Sounds like this must manually be toggled away? If someone knows if this is possible, then let me know.Quote from: PlainName on October 03, 2025, 06:31:19 pmExcellent, and thank you al lot for your feedback. I am quite happy that it works like I intended it to (except for that weird message)

author: Beauvais7165
author_rank: Contributor
timestamp: October 03, 2025, 08:38:33 pm
content: Quote from: Beauvais7165 on October 03, 2025, 05:33:52 pmI have already found a (minor) bug, where it is not possible to choose a new capture folder - it throws an exception. This has already been fixed in development, and will be part of next release. You can (for now) also edit the capture folder directly in the configuration file.

author: PlainName
author_rank: Super Contributor
timestamp: October 03, 2025, 09:11:03 pm
content: QuoteAh-ha! Thank youQuoteNope, can't even do it manually. It times out after a few seconds and disappears, even if you're still reading it and wish it wouldn't! So far as I can see, the only solution is not to do a capture within, say, 5 seconds of the previous one. And, to be fair, one probably wouldn't do that normally - I only did to try and find why the enter key didn't do a capture.Hmmm. Maybe that's a plus, actually. Suppose there's a message you want to record for posterity - quick dab of the enter key beats whipping out the phone and starting the photo app

author: egonotto
author_rank: Super Contributor
timestamp: October 04, 2025, 04:06:25 am
content: Hello,Thank you for the program.I would like to contribute something, but I don't want to publish the serial number.Therefore, please find attached the cfg file for the Siglent SDS 3000 X HD.Next, I will try it with the Micsig MHO3.Best regards,egonotto

author: egonotto
author_rank: Super Contributor
timestamp: October 04, 2025, 05:19:33 am
content: Hello,There are problems with the Micsig MHO3.The :PRINt? command cannot be found in the manual, but it can be executed and it outputs data. The meaning of the data is unclear. The error “image decode failed” appears.Kind regards,egonotto

author: Beauvais7165
author_rank: Contributor
timestamp: October 04, 2025, 08:34:54 am
content: Quote from: egonotto on October 04, 2025, 04:06:25 amI am sorry, but I did not fully understand if the "Siglent SDS2000/2000X Series" works or not for your scope? In the configuration file attached, you have included some special commands, but are they working or .. ?I would really like to see the full debug log (including seeing the specific scope model), when you test all the commands from the "Configuration" tab, if this would be possible to get? You can remove the serial manually from the text, if you do not want to show that, though I personally do not see the issue with this?

author: tautech
author_rank: Super Contributor
timestamp: October 04, 2025, 08:42:29 am
content: Quote from: Beauvais7165 on October 04, 2025, 08:34:54 amThose models are obsolete and do not use the same UI of full command set as current models.

author: Beauvais7165
author_rank: Contributor
timestamp: October 04, 2025, 08:58:14 am
content: For Siglent I have a hard time finding trustworthy documentation for SCPI commands - I am not even sure the official Siglent page shows correct information?As an example, I am now investigating the SCPI command*CLS, and for SiglentSDS1000X-EI can find this in this document here,https://siglentna.com/wp-content/uploads/dlm_uploads/2017/10/ProgrammingGuide_forSDS-1-1.pdf. I found this URL on a Google search, and it does show the*CLScommand is available, and it has even been confirmed working for aSDS1104X-Escope.However, going to the official Siglent page,https://www.siglenteu.com/resources/documents/and finding e.g.SDS1000X-Eprogramming reference,https://www.siglenteu.com/wp-content/uploads/dlm_uploads/2021/01/SDS1000-SeriesSDS2000XSDS2000X-E_ProgrammingGuide_PG01-E02D.pdf, then the*CLScommand is not at all listed anywhere?Any insights for good SCPI references?

author: egonotto
author_rank: Super Contributor
timestamp: October 04, 2025, 09:20:33 am
content: Hello,I have just sent the data for the SDS3000X HD.Kind regards,egonotto

author: Beauvais7165
author_rank: Contributor
timestamp: October 04, 2025, 09:40:48 am
content: Quote from: egonotto on October 04, 2025, 09:20:33 amAnd hereby included your validated data for the next release. Thanks a lot! :-)

author: egonotto
author_rank: Super Contributor
timestamp: October 04, 2025, 10:21:56 am
content: Hello,I have just sent the data for the AGILENT (now Keysight) DSO6104L.Kind regards,egonotto

author: tautech
author_rank: Super Contributor
timestamp: October 04, 2025, 10:32:40 am
content: Quote from: Beauvais7165 on October 04, 2025, 08:58:14 amSee p17 for the list of supported models:https://int.siglent.com/u_file/download/24_03_05/SDS2000X%20Plus_ProgrammingGuide_EN11F.pdf

author: egonotto
author_rank: Super Contributor
timestamp: October 04, 2025, 10:33:45 am
content: Hello,I have just sent the data for the Rigol DHO1074.Best regards,egonotto

author: Beauvais7165
author_rank: Contributor
timestamp: October 04, 2025, 10:57:21 am
content: Quote from: tautech on October 04, 2025, 10:32:40 amNot sure I understand what you mean, as you reference another scope, and not (as my example) for theSDS1000X-E?Both my web references applies to this specific series, where only one of the documents shows the*CLScommand. My assumption would be, that the official Siglent page would document also the*CLS, but apparently not?

author: Beauvais7165
author_rank: Contributor
timestamp: October 04, 2025, 10:58:39 am
content: Quote from: egonotto on October 04, 2025, 10:33:45 amAnd hereby included your validated data for the next release. This works just like the other Rigol scopes in application, so easy to add. Thanks a lot! :-)

author: egonotto
author_rank: Super Contributor
timestamp: October 04, 2025, 01:18:30 pm
content: Hello,I have just sent the data for the R&S RTA4000.Sometimes I couldn't find a suitable command. For example:TRIGger:A:LEVel<n>[:VALue] <Level>Best regards,egonotto

author: Beauvais7165
author_rank: Contributor
timestamp: October 04, 2025, 01:26:29 pm
content: Quote from: egonotto on October 04, 2025, 01:18:30 pmHOW MANY SCOPES DO YOU HAVE???This is really valuable to me, thanks a lot for all your contribution. I have added it for the next release.

author: egonotto
author_rank: Super Contributor
timestamp: October 04, 2025, 01:47:51 pm
content: Hello,only still a SDS2000X HD that can be assigned an IP number. However, it should behave like the SDS3000X HD.All others only have USB or RS232, or no data connection at all.Best regards,egonotto

author: Beauvais7165
author_rank: Contributor
timestamp: October 04, 2025, 07:54:43 pm
content: New version has been released,2025-October-4, and it can be downloaded from GitHub here:https://github.com/HovKlan-DH/Oscilloscope-Network-Capture/releasesChangelog:Fixed it will now always drain SYSTEM ERROR queueAdded a Feedback tabAdded default option to mask serial number in Debug tabAdded and restructured several new series of oscilloscopesChanged clicking any button in Capturing tab will change focus to the filename format fieldChanged clicking "Clear" button in Debug tab will change focus to the debug text fieldThanks a lot to the ones giving feedback and providing new scopes, especially@egonottofor his many scopesI would still like to get a lot more scopes supported, so if you can contribute with your scope and the required SCPI commands, then I will happily include it for the next release. You can easily connect with me via the Feedback tab.

author: PlainName
author_rank: Super Contributor
timestamp: October 04, 2025, 08:45:59 pm
content: QuoteI have a Micsig TO1074 (I think! it's packed away at the moment). Attached is the SCPI manual from Micsig. Haven't had a look at anything yet but will dig it out.

author: Beauvais7165
author_rank: Contributor
timestamp: October 04, 2025, 09:48:10 pm
content: Quote from: PlainName on October 04, 2025, 08:45:59 pmI have looked into the SCPI commands, and you can try-out these values, though some generic commands seems vague:Query identify instrument =*IDN?Query last system error =:SYST:ERR?Query "Operation Complete" =*OPC?Set "Clear Statistics" =:MEASURE:STATISTIC:RESETQuery active trigger =:TRIGGER:STATUS?Set "Stop" mode =:MENU:STOPSet "Single" mode =:MENU:SINGLESet "Run" mode =:MENU:RUNQuery trigger mode =:TRIGGER:TYPE?Query trigger level =:TRIGGER:EDGE:LEVEL?Set trigger level =:TRIGGER:EDGE:LEVEL {0}Query TIME/DIV =:TIMEBASE:ZOOM:SCAlE?Set TIME/DIV =:TIMEBASE:ZOOM:SCAlE {0}Query dump image =:WAV:DATA?I would be curious if this actually works?I cannot see the possible values for TIME/DIV, so if you can also provide this, then it would be great. For now the default values are:2nS, 5nS, 10nS, 20nS, 50nS, 100nS, 200nS, 500nS, 1uS, 2uS, 5uS, 10uS, 20uS, 50uS, 100uS, 200uS, 500uS, 1mS, 2mS, 5mS, 10mS, 20mS, 50mS, 100mS, 200mS, 500mS, 1S, 2S, 5S, 10S, 20S, 50S, 100S, 200S, 500S, 1000S

author: egonotto
author_rank: Super Contributor
timestamp: October 05, 2025, 10:24:46 am
content: Hello,I tried the commands with my MHO3. Unfortunately, it doesn't work with it.See the pictures.Best regards,egonotto

author: Beauvais7165
author_rank: Contributor
timestamp: October 05, 2025, 10:38:09 am
content: Quote from: egonotto on October 05, 2025, 10:24:46 amThe "Configuration" tab image is good, but I would rather like to see the "Debug" tab, as it has the details needed ;-)I am surprised Siglent does not recognize the*OPC?command, as I would assume this is an old standard SCPI command, though I am pretty new to this SCPI-game? But maybe this is an old legacy scope?Would anyone know what would work here instead, or if thewait-until-finishedsignal should entirely be scrapped for this scope?I can see that you have continued the tests, despite of errors. On my Rigol scope, my scope will completely tilt, if given an invalid command, and I then need to power-recycle scope and ONC application to get it working again. Not saying this is the case here, but it could be worth a try?

author: egonotto
author_rank: Super Contributor
timestamp: October 05, 2025, 10:51:44 am
content: Hello,*OPC? is a command from Siglent SDS3000X HD that also works for me.The manual states:“*OPCQueryDESCRIPTION The command query places an ASCII "1" in the output queuewhen all pending device operations have completed. Theinterface hangs until this query returns.QUERY SYNTAX *OPC?RESPONSE FORMAT 1 ”*OPC? is missing from Micsig.Best regards,egonotto

author: Beauvais7165
author_rank: Contributor
timestamp: October 05, 2025, 11:02:51 am
content: Quote from: egonotto on October 05, 2025, 10:51:44 amSorry, but I am confused here. In your previous post, you show you are using the "Siglent SDS1000CML+" series. If you are using a Rohde&Swartz scope, then why not select this scope? :-)I really, really need the debug info, to understand what is going on - e.g. to see which scope is being queried.UPDATED A FEW MINUTES LATER...OK, I can now see that I misunderstood and mixed the "R&C MXO 4" with "Micsig MHO3" (again back to info from debug).If Micsig does not have an*OPC?command, would there then be something else useful? It would be a little painful to readapt the application, so it can send specific command queues per scope, but it could of course be a possibility. Ideally this can be avoided, if another command is available?.

author: egonotto
author_rank: Super Contributor
timestamp: October 05, 2025, 11:20:44 am
content: Hello,SCPI at Micsig is still causing problems.I entered an example from the manual.:MEASure:OPEN PERiod , CH1But there is an error, even though the measurement appears on the screen.Could this be because *OPC? is called up afterwards?I insert with putty some commands:-------------------------------------------*IDN?Error:SCPI Command error!*IDN?Micsig,MHO3-2504,xxxxxxxxx,2.413.142*IDN?Micsig,MHO3-2504,xxxxxxxxx,2.413.142:SYST:ERR?Error:SCPI Command error!:SYST:ERR?Error:SCPI Command error!*OPC?*IDN?Micsig,MHO3-2504,xxxxxxxxx,2.413.142*OPC?*OPC?*OPC?:MEASURE:STATISTIC:RESET*IDN?Error:SCPI Command error!*IDN?Micsig,MHO3-2504,xxxxxxxxx,2.413.142:TRIGGER:STATUS?RUN:MENU:STOP:MENU:SINGLE:MENU:RUN:TRIGGER:TYPE?EDGE:TRIGGER:EDGE:LEVEL?0.31:TRIGGER:EDGE:LEVEL 0.5:TRIGGER:EDGE:LEVEL?0.5:TIMEBASE:ZOOM:SCAlE?0.001:TIMEBASE:ZOOM:SCAlE 0.002:TIMEBASE:ZOOM:SCAlE?0.001:WAV:DATA?#90000000010000*IDN?Micsig,MHO3-2504,xxxxxxxxx,2.413.142-------------------Why shouldn't you publish the serial number?Firstly, it makes sense to exercise general caution with personal data.But I've had a company ask for the serial number for a trial license so that you only get the trial license once. So someone could potentially abuse the system.Best regards,egonotto

author: Beauvais7165
author_rank: Contributor
timestamp: October 05, 2025, 12:15:41 pm
content: Quote from: egonotto on October 05, 2025, 11:20:44 amYou can check in the Debug tab exactly which commands are being sent to scope. For every SET command, the OPC and SYSERR is called, to ensure it is safe to continue with next command.Quote from: egonotto on October 05, 2025, 11:20:44 amSo, it seems these commands are not valid for Micsig::SYST:ERR?*OPC?Hmm... not good. If this is the case, and no substitute commands are available, then either I need to change my application or deem Micsig not supported.Quote from: egonotto on October 05, 2025, 11:20:44 amYeah, okay - I can see the point, but at least this has now been fixed and is masked per default :-)

author: egonotto
author_rank: Super Contributor
timestamp: October 05, 2025, 12:25:07 pm
content: Hello,We could also ask Micsig.I have had very good experiences with Micsig support. And it would be good for Micsig if your SCPI were improved.Should we ask Micsig?Best regards,egonotto

author: Beauvais7165
author_rank: Contributor
timestamp: October 05, 2025, 12:28:57 pm
content: Quote from: egonotto on October 05, 2025, 12:25:07 pmSeems like you would be the right person for that

author: Beauvais7165
author_rank: Contributor
timestamp: October 08, 2025, 05:57:59 pm
content: New version has been released here,https://github.com/HovKlan-DH/Oscilloscope-Network-Capture/releasesChangelog:Fixed "Set trigger level" for Rohde & Schwarz RTA4000Added Micsig scope with several model seriesAdded Siglent InfiniiVision 6000LAdded option to skip two non-vital SCPI commandsSpecifically for the Micsig scopes, the*OPC?and:SYSTEM:ERROR?commands have been set empty, which means they will be skipped entirely. As such they are not vital and act as "helpers", but if the scope does not support it, then it is at least now possible to exclude them.

author: Beauvais7165
author_rank: Contributor
timestamp: October 13, 2025, 06:47:59 pm
content: New version2025-October-11has been released here,https://github.com/HovKlan-DH/Oscilloscope-Network-Capture/releasesChangelog:Fixed "Set trigger level" and "Query dump image" for one of the Siglent series oscilloscopesFixed tab order for variables inCapturingtabFixed no start beep when capture beginsAdded checkbox for "Do not "Clear Statistics" when already in STOP mode" inSettingstabAdded visual feedback inCapturingtab when "ENTER" pressed in capture modeAdded visibility if capture mode is enabled or disabledAdded beep for deleting fileChanged editing filename format + "{NUMBER}" and dynamic variables will disable capture modeChanged the "{NUMBER}" variable is no longer saved to configuration fileRemoved Micsig oscilloscopes as SCPI commands for dumping image did not workVarious minor cosmetic changes

author: Beauvais7165
author_rank: Contributor
timestamp: October 18, 2025 10:22:10 pm
content: New version2025-October-18has been released here,https://github.com/HovKlan-DH/Oscilloscope-Network-Capture/releasesChangelog:Fixed misalignment for displayed image in UIAdded network connectivity check when capture mode enabled, and disable capture mode when scope is offlineAdded visual feedback in Capturing tab when capturing an imageChanged capturing mode will get reenabled as soon as loosing focus for any of the relevant input fields in Capturing tabChanged default CLEAR delay from 1750mS to 2000mS