Test SCPI socket communications with PuTTY
PuTTY as an interactive SCPI console: configure a Raw connection to port 5025, fix the line-ending settings, and drive your instrument by keyboard.
PuTTY isn't just for SSH — its Raw mode makes an excellent interactive SCPI console for Siglent instruments that support the raw socket on port 5025, with no Windows feature-flags required. Most current models do, including every power supply and the DC load; a handful of older ones do not, and those need VXI-11 or USB instead.
Configure the session
- Download PuTTY from putty.org (free)
- Connection type: Raw
- Host: your instrument's IP address (from its LAN/IO menu)
- Port: 5025
- Under Terminal: enable Implicit CR in every LF and Local echo: Force on — so you can see what you type and responses line up
Talk to the instrument
*IDN? *OPC? C1:BSWV FRQ,2500
Siglent Technologies,SDG6052X,SDG6XBAD1R0001,6.01.01.28R5 1
Save the session under the instrument's name in PuTTY — next time it's a double-click to get a console on your scope or generator.
If characters appear but nothing answers: you probably connected to the wrong port, or the model has no 5025 socket and needs VXI-11 (see that note). If the window closes instantly, the IP is wrong or a firewall is blocking port 5025.
Does my model have the 5025 socket?
| Services | Models |
|---|---|
| Socket 5025 and Telnet 5024 | SDS5000X, SDS2000X Plus, SDS2000X-E, SDS1000X-E, SDS1104X-U, SDG6000X, SDG2000X, SDG1000X, SSA3000X, SSA3000X Plus, SSA3000X-R, SVA1000X, SDM3045X, SDM3055, SDM3065X, SSG3000X, SSG5000X, SNA5000A |
| Socket 5025 only — PuTTY Raw still works | SPD3303X, SPD3303X-E, SPD1000X, SPS5000X, SDL1000X |
| No socket — use VXI-11 or USB instead | SDS2000X, SDS1000X, SDS1000CML+, SDS1000DL+, SDG800, SPD3303C, SHS800, SHS1000 |
Which services a given model offers is published by Siglent in Instrument Socket and Telnet Port Information. Check it before assuming — the pattern is not uniform across the range, and the power supplies in particular offer the socket but not Telnet.
When PuTTY works, every automation layer above it (PyVISA, sockets, LabVIEW) has a proven transport underneath — debugging becomes a code question, not a network question.
Instruments used in this note
Related application notes
Our engineers use these instruments daily — ask us anything.