Products > Test Equipment
ngscopeclient - Ultimate acquisition software / protocol decoder / debug tool ?
Kean:
--- Quote from: Antonio90 on September 13, 2024, 11:55:46 pm ---Hello, this might be a stupid question but, how do you estabilish a connection with the scope? I'm selecting the Siglent driver, and typing the LAN IP:5025, to no avail.
The console says something about the scope answering "welcome to SDS824X HD" after asking for an ID.
--- End quote ---
Are you sure you didn't accidentally type port 5024 instead of 5025?
According to the programming manual, port 5024 is the telnet port and would answer with "Welcome to ..." plus a ">>" prompt, then accept interactive SCPI commands.
As expected, port 5025 is meant for program control via socket without the prompts.
Antonio90:
--- Quote from: azonenberg on September 14, 2024, 05:13:52 pm ---
--- Quote from: Antonio90 on September 13, 2024, 11:55:46 pm ---Hello, this might be a stupid question but, how do you estabilish a connection with the scope? I'm selecting the Siglent driver, and typing the LAN IP:5025, to no avail.
The console says something about the scope answering "welcome to SDS824X HD" after asking for an ID.
--- End quote ---
I wonder if there's some weird setting on the scope to make it provide a full shell or something rather than just a raw SCPI command interface?
If you connect to the scope on the SCPI port, it should not send anything immediately.
If you then send "*IDN?" it should reply with something like "Siglent Technologies,SDL1020X-E,SDL13GCX6R0651,1.1.1.21R2".
If it sends any kind of command prompt or welcome banner or something that will confuse the driver as it's not supposed to be there. There might be a setting to turn this on/off, not sure.
--- End quote ---
Hello Andrew. Thank you very much for your help, and for developping the software. I got to know it through the Thunderscope project, which I have been following for a while, and it is truly impressive.
The oscilloscope sends a welcome banner when a Telnet connection is started with Putty, through port 5024. Before any command is sent, it prints:
"Welcome to the SCPI instrument 'Siglent SDS824X HD'"
I managed to get something like "Unknown serial number SDS824XHD" or similar, while alternating connections between Ngscopeclient and Putty, but haven't been able to reproduce it.
Now I only get this (image attached)
I'm already installing Linux, I want to try the AD2 too.
azonenberg:
--- Quote from: Antonio90 on September 14, 2024, 07:34:53 pm ---Hello Andrew. Thank you very much for your help, and for developping the software. I got to know it through the Thunderscope project, which I have been following for a while, and it is truly impressive.
The oscilloscope sends a welcome banner when a Telnet connection is started with Putty, through port 5024. Before any command is sent, it prints:
"Welcome to the SCPI instrument 'Siglent SDS824X HD'"
I managed to get something like "Unknown serial number SDS824XHD" or similar, while alternating connections between Ngscopeclient and Putty, but haven't been able to reproduce it.
Now I only get this (image attached)
I'm already installing Linux, I want to try the AD2 too.
--- End quote ---
Yeah you want to use 5025 which is the port for un-formatted raw SCPI remote control rather than telnet.
Antonio90:
Then the terminal just returns "ERROR: Unknown scope type"
Antonio90:
--- Quote from: Kean on September 14, 2024, 06:44:10 pm ---
--- Quote from: Antonio90 on September 13, 2024, 11:55:46 pm ---Hello, this might be a stupid question but, how do you estabilish a connection with the scope? I'm selecting the Siglent driver, and typing the LAN IP:5025, to no avail.
The console says something about the scope answering "welcome to SDS824X HD" after asking for an ID.
--- End quote ---
Are you sure you didn't accidentally type port 5024 instead of 5025?
According to the programming manual, port 5024 is the telnet port and would answer with "Welcome to ..." plus a ">>" prompt, then accept interactive SCPI commands.
As expected, port 5025 is meant for program control via socket without the prompts.
--- End quote ---
Apologies, I got your post lost in between answering. You are right, I initially tried both and neither worked. I just assumed "Unknown trigger type" was a more promising error than "Unknown scope type" and kept trying there.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version