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.

6 min readIncludes code

PuTTY isn't just for SSH — its Raw mode makes a perfect interactive SCPI console for any Siglent instrument, with no Windows feature-flags required.

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

scpi

*IDN?
*OPC?
C1:BSWV FRQ,2500

What you should see

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 only supports VXI-11 (see that note). If the window closes instantly, the IP is wrong or a firewall is blocking port 5025.

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

Any Siglent LAN instrument

Interactive SCPI on port 5025

View

Related application notes

Verify an instrument LAN connection with Telnet Open-socket LAN control with Python (port 5025)Verify a remote connection with NI-MAX

Questions about this measurement?

Our engineers use these instruments daily — ask us anything.

Ask an engineer