Oscilloscope Network Capture - does it work with your scope? - Page 1
Forum section: electronics / general

author: Beauvais7165
author_rank: Contributor
timestamp: September 20, 2025, 09:39:32 pm
content: I have developed a Windows tool, which is able to capture an image from your network connected scope. As it usesSCPIcommands, itshouldwork on other scopes than myRigol DS2202A, but this is very I would really appreciate some simple verification.If you want to help me with this, then I kind ask for you to:Go to GitHub and download newest release (just the one executable),https://github.com/HovKlan-DH/Oscilloscope-Network-Capture/releasesLaunch the Windows tool, change IP and click the button "Check oscilloscope connectivity"Ideally here youshouldsee the scope vendor and model?If it does, then continue:Click the button "Capture continuesly"Now look at your scope and try some of these keyboard actions:-or+to increase timespan*to STOP acquisition on scope (freeze image)/to RESUME acquisition on scopeARROW UPorARROW DOWNto change trigger level with 0.25VENTERto save image to a fileI would apreciate feedback both if this is confirmed work or not. In both cases I would like to know yourscope vendorandmodel.Requirement for tool:Windows 10 or newer.NET Framework 4.8.1

author: PlainName
author_rank: Super Contributor
timestamp: September 23, 2025, 05:14:07 pm
content: Fantastic stuff, thanks!Unfortunately, I tried this with my DSOX2004 and (perhaps not surprisingly) got the following:Code:18:11:35.573 Scope port changed to 502418:11:35.703 Opening SCPI session: 192.168.0.51:502418:11:35.917 Instrument error: >>*CLS18:11:35.919 Instrument error: *IDN?18:11:35.921 Instrument error: :SYST:ERR?18:11:35.923 Instrument error: :SYST:ERR?18:11:35.925 Instrument error: :SYST:ERR?18:11:35.926 Instrument error: :SYST:ERR?Edit:Trying to be usefulI turned on debug and got:Code:18:14:25.067 Attempting TCP connectivity.18:14:25.072 Port 5024 preliminary probe succeeded.18:14:25.074 Opening SCPI session: 192.168.0.51:502418:14:25.287 IDN: ÿûÿû*CLS18:14:25.302 Instrument error: *IDN?18:14:25.314 Instrument error: :SYST:ERR?18:14:25.317 Instrument error: :SYST:ERR?18:14:25.320 Instrument error: :SYST:ERR?18:14:25.322 Instrument error: :SYST:ERR?18:14:25.324 Instrument error: :SYST:ERR?then switched to 2025 - the Agilent documentation explains the difference:QuoteUsing 5025 got me this:Code:18:14:40.627 Scope port changed to 502518:14:40.631 Saved configuration:18:14:40.632 IP: 192.168.0.51:502518:14:40.634 Region: PAL18:14:40.637 Component: U118:14:40.639 FilenameFormat: {Component}_{Number}_{Region}_{Date}_{Time}18:14:40.641 OutputFolder: R:\output18:14:40.642 Beep: 118:14:40.644 ForceAcquisition: 018:14:40.646 SplitterDistance: 32718:14:40.652 WindowMaximized: 018:14:40.798 Attempting TCP connectivity.18:14:40.802 Port 5025 preliminary probe succeeded.18:14:40.804 Opening SCPI session: 192.168.0.51:502518:14:41.279 IDN: AGILENT TECHNOLOGIES,DSO-X 2004A,MY52101004,02.50.201902273618:14:41.281 Connected with oscilloscope:18:14:41.284 Vendor: AGILENT TECHNOLOGIES18:14:41.285 Model: DSO-X 2004A18:14:41.287 Firmware: 02.50.201902273618:14:41.289 Oscilloscope is ready.18:14:41.291 Instrument error: +0,"No error"18:14:41.293 Instrument error: +0,"No error"18:14:41.295 Instrument error: +0,"No error"18:14:41.297 Instrument error: +0,"No error"18:14:41.299 Instrument error: +0,"No error"18:14:41.301 Instrument error: +0,"No error"

author: Beauvais7165
author_rank: Contributor
timestamp: September 23, 2025, 06:19:26 pm
content: Quote from: PlainName on September 23, 2025, 05:14:07 pmThe correct port to use forSCPI socketon this scope, seems to be5025as 5024 appears to be the port for the telnet protocol.The error at the last line:Instrument error: +0,"No error"... may be because this scope is reporting the "no error" differently than the other couple of tested scopes, where it adds a "+0" instead of "0", so I have corrected this in my development code. I have pushed the code to GitHub, if you have the possibility to download the sources and test? Otherwise I can release a new version Friday and let you know.GitHub project,https://github.com/HovKlan-DH/Oscilloscope-Network-CaptureThis is the first test of aAgilent/Keysight, so thank you very much for taking your time and reporting the feedback :-)

author: PlainName
author_rank: Super Contributor
timestamp: September 23, 2025, 07:09:37 pm
content: Thanks for considering other scopes than the usual Rigols and SiglentsI'm afraid I don't have the tools to compile this code so I will patiently wait until you have time to do the business. Just as a matter of interest, I am running Windows 7 and it works fine, although I wouldn't be too surprised if later versions didn't.

author: Beauvais7165
author_rank: Contributor
timestamp: September 24, 2025, 05:41:34 pm
content: Quote from: PlainName on September 23, 2025, 07:09:37 pmWell, if the scope supports standard SCPI, then I don't see a big issue in doing this. Now I have a minimum experience with Rigol, Siglent and yours (Agilent), and though the commands are slightly different, then it is still within same framework, so doable (I hope).Quote from: PlainName on September 23, 2025, 07:09:37 pmI have made a new interim release available here - would you mind checking if this fixes your issue? I have actually also lowered the requirement, so .NET Framework 4.8 should also be fine, and this I know is supported on Windows 7.Oscilloscope Network CaptureGitHub releases:https://github.com/HovKlan-DH/Oscilloscope-Network-Capture/releases

author: tooki
author_rank: Super Contributor
timestamp: September 24, 2025, 06:26:09 pm
content: Rohde & Schwarz MXO4: Unsuccessful.20:23:16.914 Connecting SCPI socket session.20:23:19.422 Trigger state: HS20:23:19.552 Acquisition stopped for screenshot.20:23:19.552 Trying screenshot command: :DISP:DATA?20:23:19.561 Trying screenshot command: :DISP:DATA? PNG20:23:19.561 Trying screenshot command: :DISP:DATA? ON,0,PNG20:23:19.568 Trying screenshot command: :HARDcopy:DATA? PNG20:23:19.571 Trying screenshot command: :HCOPy:DATA? PNG20:23:19.574 Trying screenshot command: :DISP:DATA? ON,0,BMP20:23:19.576 Trying screenshot command: :SCDP?20:23:19.578 Capture failed: System.IO.InvalidDataException: All screenshot command attempts failed.at Oscilloscope_Network_Capture.Scope.<>c__DisplayClass16_0.<CaptureAsync>b__0()Manual (includes SCPI commands):https://www.datatec.eu/media/ae/49/1a/1702461583/Rohde_Schwarz-1335.5050_(7).pdfHARDcopy documented page 578ff

author: Beauvais7165
author_rank: Contributor
timestamp: September 24, 2025, 06:34:49 pm
content: Quote from: tooki on September 24, 2025, 06:26:09 pmWould it be possible to enable "Debug" and copy/paste full log from start to end, including the "Check connectivity to scope"? Could use that for troubleshooting :-)Quote from: tooki on September 24, 2025, 06:26:09 pmThanks - I will for sure take a look at this.

author: Mahagam
author_rank: Regular Contributor
timestamp: September 24, 2025, 06:40:53 pm
content: Quote from: tooki on September 24, 2025, 06:26:09 pmThe Scope processor isn't exactly a high-end gaming processor. Be patient with it and give it some time to respond.

author: Beauvais7165
author_rank: Contributor
timestamp: September 24, 2025, 06:50:49 pm
content: Quote from: Mahagam on September 24, 2025, 06:40:53 pmThe fast timing here is because scope returns something "unexpected", so not me only waiting for a few milli-seconds. Actually my timeout is 5 seconds, so it seems the scope IS a high-end gaming machine that can give a response this fastI will check if I can output the received data for more debug info.

author: tooki
author_rank: Super Contributor
timestamp: September 24, 2025, 06:52:20 pm
content: Quote from: Mahagam on September 24, 2025, 06:40:53 pmLOL.The program sends commands on its own when you press Enter to capture. I didn't enter them myself. The snippet is what the program itself logged in its terminal area.Not that it matters since the scope doesn't support any of those commands.(Also, the MXO4 is a very modern, not entry-level scope. It wouldn't have any trouble responding to a bunch of unsupported commands. It can handle real-time interaction with its GUI via its web interface, which streams a live video feed of its display, which you can interact with directly.)

author: tooki
author_rank: Super Contributor
timestamp: September 24, 2025, 06:54:48 pm
content: Quote from: Beauvais7165 on September 24, 2025, 06:50:49 pmIt also certainly doesn't hurt that it has a private Ethernet link to my PC on a separate network interface (since I cannot simply connect test equipment to the university LAN).

author: tooki
author_rank: Super Contributor
timestamp: September 24, 2025, 07:16:10 pm
content: Quote from: Beauvais7165 on September 24, 2025, 06:34:49 pmTest 121:01:35.645 Application version: 2025-September-2421:01:36.614 Port 5555 preliminary probe failed (will still attempt full connect).21:01:36.614 Opening SCPI socket session: 192.168.0.100:555521:01:41.637 Connectivity check failed (timeout): SCPI connect timeout.21:01:53.436 Scope port changed to 4880Enabled debug, clicked "Check oscilloscope connectivity"21:02:00.222 Attempting TCP connectivity.21:02:00.230 Port 4880 preliminary probe succeeded.21:02:00.232 Opening SCPI socket session: 192.168.1.100:4880Nothing happened here so I pressed Enter21:02:17.544 Capture mode active. Press  to capture,  to stop.Pressed Enter21:02:21.125 Connecting SCPI socket session.21:02:23.629 Trigger state: HS21:02:23.760 Acquisition stopped for screenshot.21:02:23.762 Trying screenshot command: :DISP:DATA?21:02:23.763 Trying screenshot command: :DISP:DATA? PNG21:02:23.765 Trying screenshot command: :DISP:DATA? ON,0,PNG21:02:23.766 Trying screenshot command: :HARDcopy:DATA? PNG21:02:23.768 Trying screenshot command: :HCOPy:DATA? PNG21:02:23.769 Trying screenshot command: :DISP:DATA? ON,0,BMP21:02:23.770 Trying screenshot command: :SCDP?21:02:23.771 Capture failed: System.IO.InvalidDataException: All screenshot command attempts failed.at Oscilloscope_Network_Capture.Scope.<>c__DisplayClass16_0.<CaptureAsync>b__0()Test 2Another attempt, with "Enable debug" clicked before editing IP address and port, and letting it go until it gives up:21:07:52.329 Application version: 2025-September-2421:07:53.316 Port 5555 preliminary probe failed (will still attempt full connect).21:07:53.325 Opening SCPI socket session: 192.168.0.100:555521:07:57.480 Saved configuration:21:07:57.491 IP: 192.168.0.100:555521:07:57.492 Region: PAL21:07:57.492 Component: U121:07:57.492 FilenameFormat: {Component}_{Number}_{Region}_{Date}_{Time}21:07:57.492 OutputFolder: C:\Users\username\AppData\Local\Temp\scoped_dir4752_1941406270\output21:07:57.492 Beep: 121:07:57.492 ForceAcquisition: 021:07:57.492 ForceClear: 021:07:57.492 SplitterDistance: 36321:07:57.502 WindowMaximized: 021:07:57.502 Misc:snipped multiple similar blocks while resizing the window21:08:02.020 Scope port changed to 488021:08:02.027 Saved configuration:21:08:02.030 IP: 192.168.0.100:488021:08:02.033 Region: PAL21:08:02.037 Component: U121:08:02.041 FilenameFormat: {Component}_{Number}_{Region}_{Date}_{Time}21:08:02.074 OutputFolder: C:\Users\username\AppData\Local\Temp\scoped_dir4752_1941406270\output21:08:02.076 Beep: 121:08:02.076 ForceAcquisition: 021:08:02.082 ForceClear: 021:08:02.082 SplitterDistance: 62421:08:02.119 WindowMaximized: 021:08:02.119 Misc:21:08:09.026 Saved configuration:21:08:09.043 IP: 192.168.1.100:488021:08:09.052 Region: PAL21:08:09.058 Component: U121:08:09.059 FilenameFormat: {Component}_{Number}_{Region}_{Date}_{Time}21:08:09.059 OutputFolder: C:\Users\username\AppData\Local\Temp\scoped_dir4752_1941406270\output21:08:09.069 Beep: 121:08:09.118 ForceAcquisition: 021:08:09.125 ForceClear: 021:08:09.127 SplitterDistance: 62421:08:09.127 WindowMaximized: 021:08:09.127 Misc:21:08:12.746 Attempting TCP connectivity.21:08:12.754 Port 4880 preliminary probe succeeded.21:08:12.759 Opening SCPI socket session: 192.168.1.100:488021:09:12.795 Connectivity check failed (I/O): Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.Pressing Enter produces the same output as in the prior tests.

author: tooki
author_rank: Super Contributor
timestamp: September 24, 2025, 08:05:09 pm
content: Trying different port numbers, perhttps://www.rohde-schwarz.com/webhelp/Remote_Control_SCPI_HTML_GettingStarted/Content/5833b78181fd4439.htm(Port 4880 is the only one configurable by the user, so that's what I tried first...)Port 111Checking connectivity:21:36:24.954 Attempting TCP connectivity.21:36:24.954 Port 111 preliminary probe succeeded.21:36:24.966 Opening SCPI socket session: 192.168.1.100:11121:36:24.982 Connectivity check failed (I/O): Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.Attempting to capture:21:37:18.134 Capture mode active. Press  to capture,  to stop.21:37:20.556 Connecting SCPI socket session.21:37:20.563 No trigger state response; assuming running.21:37:20.681 Acquisition stopped for screenshot.21:37:20.689 Trying screenshot command: :DISP:DATA?21:37:20.697 Trying screenshot command: :DISP:DATA? PNG21:37:20.702 Trying screenshot command: :DISP:DATA? ON,0,PNG21:37:20.706 Trying screenshot command: :HARDcopy:DATA? PNG21:37:20.713 Trying screenshot command: :HCOPy:DATA? PNG21:37:20.719 Trying screenshot command: :DISP:DATA? ON,0,BMP21:37:20.724 Trying screenshot command: :SCDP?21:37:20.752 Capture failed: System.IO.InvalidDataException: All screenshot command attempts failed.at Oscilloscope_Network_Capture.Scope.<>c__DisplayClass16_0.<CaptureAsync>b__0()Port 5025:Checking connectivity:21:39:50.778 Attempting TCP connectivity.21:39:50.793 Port 5025 preliminary probe succeeded.21:39:50.800 Opening SCPI socket session: 192.168.1.100:502521:39:50.814 IDN: Rohde&Schwarz,MXO44,1335.5050k04/[serial number],2.6.2.221:39:50.850 Connected with oscilloscope:21:39:50.891 Vendor: Rohde&Schwarz21:39:50.896 Model: MXO4421:39:50.901 Firmware: 2.6.2.221:39:50.907 Oscilloscope is ready.Some progress of sorts!Attempting to capture:21:40:44.390 Capture mode active. Press  to capture,  to stop.21:40:45.889 Connecting SCPI socket session.21:40:45.896 IDN: Rohde&Schwarz,MXO44,1335.5050k04/[serial number],2.6.2.221:40:45.901 Vendor classification: Unknown21:40:49.516 No trigger state response; assuming running.21:40:49.650 Acquisition stopped for screenshot.21:40:49.663 Trying screenshot command: :DISP:DATA?21:40:54.665 Trying screenshot command: :DISP:DATA? PNG21:41:02.678 Trying screenshot command: :DISP:DATA? ON,0,PNG21:41:10.682 Trying screenshot command: :HARDcopy:DATA? PNG21:41:18.690 Trying screenshot command: :HCOPy:DATA? PNG21:41:26.696 Trying screenshot command: :DISP:DATA? ON,0,BMP21:41:34.712 Trying screenshot command: :SCDP?21:41:42.728 Capture failed: System.IO.InvalidDataException: All screenshot command attempts failed.at Oscilloscope_Network_Capture.Scope.<>c__DisplayClass16_0.<CaptureAsync>b__0()While it attempts those commands, the scope's screen is blanked and displays "Remote mode" in giant letters.Port 5125:Checking connectivity:21:51:30.687 Attempting TCP connectivity.21:51:30.692 Port 5125 preliminary probe succeeded.21:51:30.698 Opening SCPI socket session: 192.168.1.100:512521:52:30.727 Connectivity check failed (I/O): Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.Attempting to capture:21:53:04.845 Capture mode active. Press  to capture,  to stop.21:53:06.970 Connecting SCPI socket session.21:53:13.099 No trigger state response; assuming running.21:53:14.734 Acquisition stopped for screenshot.21:53:14.739 Trying screenshot command: :DISP:DATA?21:53:19.742 Trying screenshot command: :DISP:DATA? PNG21:53:27.757 Trying screenshot command: :DISP:DATA? ON,0,PNG21:53:35.769 Trying screenshot command: :HARDcopy:DATA? PNG21:53:43.785 Trying screenshot command: :HCOPy:DATA? PNG21:53:51.787 Trying screenshot command: :DISP:DATA? ON,0,BMP21:53:59.797 Trying screenshot command: :SCDP?21:54:07.867 Capture failed: System.IO.InvalidDataException: All screenshot command attempts failed.at Oscilloscope_Network_Capture.Scope.<>c__DisplayClass16_0.<CaptureAsync>b__0()Port 2525:Checking connectivity:22:00:02.754 Attempting TCP connectivity.22:00:03.368 Port 2525 preliminary probe failed (will still attempt full connect).22:00:03.370 Opening SCPI socket session: 192.168.1.100:252522:00:05.415 Connectivity check failed: No connection could be made because the target machine actively refused it 192.168.1.100:2525Attempting to capture:22:01:19.783 Capture mode active. Press  to capture,  to stop.22:01:23.209 Capture failed: System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 192.168.1.100:2525at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult)at Oscilloscope_Network_Capture.Scope.ScpiClient.Connect(String host, Int32 port, Int32 connectTimeoutMs, Int32 ioTimeoutMs)at Oscilloscope_Network_Capture.Scope.<>c__DisplayClass16_0.<CaptureAsync>b__0()

author: PlainName
author_rank: Super Contributor
timestamp: September 24, 2025, 08:30:17 pm
content: Quote from: Beauvais7165 on September 24, 2025, 05:41:34 pmConnects without issue but can't capture. The scope pops up an 'undefined header' note, stops the scope and then says command complete. On trying a new capture the scope doesn't enter run mode.Debug:Code:21:24:29.909 Attempting TCP connectivity.21:24:29.914 Port 5025 preliminary probe succeeded.21:24:29.917 Opening SCPI socket session: 192.168.0.51:502521:24:30.380 IDN: AGILENT TECHNOLOGIES,DSO-X 2004A,MY52101004,02.50.201902273621:24:30.402 Connected with oscilloscope:21:24:30.404 Vendor: AGILENT TECHNOLOGIES21:24:30.407 Model: DSO-X 2004A21:24:30.409 Firmware: 02.50.201902273621:24:30.412 Oscilloscope is ready.21:24:41.435 Capture mode active. Press  to capture,  to stop.21:24:45.386 Connecting SCPI socket session.21:24:45.399 IDN: AGILENT TECHNOLOGIES,DSO-X 2004A,MY52101004,02.50.201902273621:24:45.410 Vendor classification: Unknown21:24:50.502 No trigger state response; assuming running.21:24:50.624 Acquisition stopped for screenshot.21:24:50.627 Trying screenshot command: :DISP:DATA?21:24:50.913 Command :DISP:DATA? succeeded (block, bytes=403478, head=42 4D 16 28 06 00 00 00 00 00 36 04 00 00 28 00)21:24:50.918 Capture failed: System.IO.InvalidDataException: BMP validation failed: Unsupported bpp 8at Oscilloscope_Network_Capture.Scope.<>c__DisplayClass16_0.<CaptureAsync>b__0()

author: Beauvais7165
author_rank: Contributor
timestamp: September 25, 2025, 02:43:36 pm
content: Quote from: tooki on September 24, 2025, 08:05:09 pmI will assume that port5025is the correct port for this scope, as it is same port as e.g. Siglent and other scopes (only my Rigol seems to be different with port 5555), so 5025 is probably some kind ofstandard SCPI socket command port.I will focus on getting more debug information available + I will check the programmers reference, and see if I can find anything useful in there, as I do expect the problem is that we just need to find the correct SCPI commands for this scope. I will get back to you later, when I do have a new try for this.Quote from: tooki on September 24, 2025, 06:52:20 pmONC works (for now, may change) in this way:At application launch you can setup various stuff - e.g. IP and you can input the variables where you will start your measurement. Then when done, you can press the "Capture continuously" (which will also be activated if you press ENTER after application launch), which will go into "capture mode". In capture mode it is the idea that you sit next to your scope, with a keyboard or a numpad, and then you can use various keys to control the scope - e.g. ENTER for capturing an image, which will run all these commands in this order, if it does not work the first time.Quote from: tooki on September 24, 2025, 06:52:20 pmIn terms of your scope... yeah, I looked it up after I saw your first post, and this is some crafty and veeeery nice scope you got there!

author: Beauvais7165
author_rank: Contributor
timestamp: September 25, 2025, 06:31:24 pm
content: Quote from: tooki on September 24, 2025, 06:26:09 pm... and:Quote from: PlainName on September 24, 2025, 08:30:17 pmCan you please again try with a new version here,https://github.com/HovKlan-DH/Oscilloscope-Network-Capture/releasesDo enable debug mode and try first to "Check oscilloscope connectivity". If this succeed then try and capture one image. IF this also work (betting on many things here), then try and use all the keyboard commands from the "Help" tab.Would like to seefulldebug output, if anything fails

author: PlainName
author_rank: Super Contributor
timestamp: September 25, 2025, 06:55:24 pm
content: Quote from: Beauvais7165 on September 25, 2025, 06:31:24 pm(Helps to turn on the scope before trying this - long story...)Did this and had debug enabled from the off:Code:19:49:45.641  Scope port changed to 502519:49:49.802  Attempting TCP connectivity.19:49:49.811  Port 5025 preliminary probe succeeded.19:49:49.814  Opening SCPI socket session: 192.168.0.51:502519:49:49.852  IDN: AGILENT TECHNOLOGIES,DSO-X 2004A,MY52101004,02.50.201902273619:49:49.854  Connected with oscilloscope:19:49:49.856  Vendor: AGILENT TECHNOLOGIES19:49:49.857  Model: DSO-X 2004A19:49:49.859  Firmware: 02.50.201902273619:49:49.860  Oscilloscope is ready.19:49:56.012  Capture mode active. Press  to capture,  to stop.19:50:00.045  Connecting SCPI socket session.19:50:00.058  IDN: AGILENT TECHNOLOGIES,DSO-X 2004A,MY52101004,02.50.201902273619:50:00.060  Vendor classification: Keysight19:50:05.161  No trigger state response; assuming running.19:50:05.338  Acquisition stopped for screenshot.19:50:05.340  Trying screenshot command (Keysight): :DISPlay:DATA? PNG,SCReen,Color19:50:13.841  Keysight screenshot cmd :DISPlay:DATA? PNG,SCReen,Color failed. transport=IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond., instrErr=(-113,"Undefined header")19:50:13.845  Trying screenshot command (Keysight): :DISPlay:DATA? BMP,SCReen,Color19:50:22.344  Keysight screenshot cmd :DISPlay:DATA? BMP,SCReen,Color failed. transport=IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond., instrErr=(-113,"Undefined header")19:50:22.347  Trying screenshot command (Keysight): :DISP:DATA?19:50:22.643  Command :DISP:DATA? succeeded (bytes=403478, head=42 4D 16 28 06 00 00 00 00 00 36 04 00 00 28 00)19:50:22.646  Save: kind=Bmp, len=403478, head=42 4D 16 28 06 00 00 00 00 00 36 04 00 00 28 00, path=R:\output\U1_1_PAL_20250925_195000.png19:50:22.652  Saved R:\output\U1_1_PAL_20250925_195000.png19:50:25.953  Acquisition already running; no resume needed.19:50:25.959  Instrument error [-113]: Undefined header19:50:25.962  Instrument error [-224]: Illegal parameter value19:50:25.965  Instrument error [-224]: Illegal parameter value19:50:25.968  Instrument error [-113]: Undefined header19:50:25.970  Instrument error [-113]: Undefined header19:50:25.975  Instrument error [-113]: Undefined headerScreenie of the app and output attached

author: PlainName
author_rank: Super Contributor
timestamp: September 25, 2025, 07:11:02 pm
content: BTW, it takes 45 seconds to do a capture, which is a looong time. Also, the scope is stopped. I can set the scope to go manually but it would be nicer if the app could do that. And... continuous doesn't. It is a one-shot capture and then idles until I hit enter, when it captures again.

author: Beauvais7165
author_rank: Contributor
timestamp: September 25, 2025, 07:16:00 pm
content: Quote from: PlainName on September 25, 2025, 06:55:24 pmSo, it seems to be able to fetch and save a file - nice.I have just uploaded a new binary to the same release, so please re-download it. If you go to the "About" tab, it should show "(rev. 2)".Does this version fixes the errors shown?How about the keyboard command - do they work?Quote from: PlainName on September 25, 2025, 07:11:02 pm45 seconds is most likely because it is running through the queue of commands to try, and it was the 3rd command that worked + some time processing it. The new binary will (hopefully) have the work command as the first one now, so it should be faster.In terms of reenabling acqusition, then just click "Force acquistion" checkbox, which will enforce scope is running again after capture (if it works).

author: PlainName
author_rank: Super Contributor
timestamp: September 25, 2025, 07:29:49 pm
content: Capture is a bit quicker now, perhaps half the time of before. Force acquisition is on but doesn't do anything, and manually starting the scope doesn't change anything. Only command I have is enter, which starts a new acquisition and then stops.Code:20:25:49.954  Connecting SCPI socket session.20:25:49.968  IDN: AGILENT TECHNOLOGIES,DSO-X 2004A,MY52101004,02.50.201902273620:25:49.970  Vendor classification: Keysight20:25:55.071  No trigger state response; assuming running.20:25:55.193  Acquisition stopped for screenshot.20:25:55.196  Keysight legacy (InfiniiVision) screenshot strategy selected.20:25:55.200  Trying screenshot command (Keysight): :DISP:DATA?20:25:55.495  Command :DISP:DATA? succeeded (bytes=403478, head=42 4D 16 28 06 00 00 00 00 00 36 04 00 00 28 00)20:25:55.499  Save: kind=Bmp, len=403478, head=42 4D 16 28 06 00 00 00 00 00 36 04 00 00 28 00, path=R:\output\U1_4_PAL_20250925_202549.png20:25:55.502  Saved R:\output\U1_4_PAL_20250925_202549.png20:25:58.802  Acquisition already running; no resume needed.20:25:58.806  (Suppressed screenshot probe error [-113]: Undefined header)20:25:58.808  (Suppressed screenshot probe error [-113]: Undefined header)20:25:58.811  (Suppressed screenshot probe error [-113]: Undefined header)20:25:58.814  (Suppressed screenshot probe error [-113]: Undefined header)20:25:58.817  (Suppressed screenshot probe error [-113]: Undefined header)20:25:58.821  (Suppressed screenshot probe error [-113]: Undefined header)

author: Beauvais7165
author_rank: Contributor
timestamp: September 26, 2025, 03:25:07 pm
content: OK, I better do this a little differently, and do more investigation into the SCPI commands per scopeConsidering having a configuration tab for SCPI commands to use, so this can be tested and validated locally, instead of awaiting for me to fix things with a new executable.Will get back here ...

author: PlainName
author_rank: Super Contributor
timestamp: September 26, 2025, 05:02:57 pm
content: If it helps, the Agilent has a web interface, like the one Tooki describes, which does a real-time copy of the scope screen. Maybe that kind of thing might be easier - it's probably some HTML5 thing, but in any case likely a standard across browsers.

author: Beauvais7165
author_rank: Contributor
timestamp: September 26, 2025, 05:30:36 pm
content: Quote from: PlainName on September 26, 2025, 05:02:57 pmNo, my problem is that I am not fully in control on the SCPI commands used, and my code is not structured in a way that is suitable for multiple scopes, as this is primarily "vibe coded" with AI... because it was meant as a quick PoC for myself only. But I think I will go much deeper into this myself, so I understand this better, and I am currently reviewing SCPI commands per scope, to see if I can figure out the correct commands to use. The initial test here has showed this is possible and doable, so I just need to figure out to do this in a better way.Going HTML would for sure be a quick route for insanity

author: Beauvais7165
author_rank: Contributor
timestamp: October 03, 2025, 05:41:01 pm
content: @tookiand@PlainName- with reference to this other forum post, then there is now a completely new application you can try-out.Please read this thread for it,https://www.eevblog.com/forum/testgear/oscilloscope-network-capture-grab-images-from-your-scope-via-network/I would really like to hear your test of this, as I have spend some time investigating proper SCPI commands for your scopes. I of coursehopeit will work, but this is where your testing would be great

author: PlainName
author_rank: Super Contributor
timestamp: October 03, 2025, 06:16:17 pm
content: Gone over there...

author: metrologist
author_rank: Super Contributor
timestamp: October 03, 2025, 06:24:34 pm
content: I tried this version and it works on my DS1054Z.I had some comments to add features of course so will look at the new version.Basically I wanted to get other types of data out of the instrument and be able to send my own SCPI through your command line interface.I used to do this in an Excel spreadsheet to get and replot the graphs.

author: Beauvais7165
author_rank: Contributor
timestamp: October 03, 2025, 06:28:56 pm
content: Quote from: metrologist on October 03, 2025, 06:24:34 pmWhen working with my Rigol DS2202, yes then I would also expect it to work with the DS1000 series, but happy to see this confirmed (they should use more or less same SCPI commands) :-)Quote from: metrologist on October 03, 2025, 06:24:34 pmIf you could try-out the new version, and again validate, and then please consider how you see your new features embedded into this new application. As mentioned in the "About" tab, then the idea is not to make this a generic tool that can be used by everyone, as this will require too much development, and not my interest. But, if it can be done with minor adjustments, then I am for sure willing to investigate.