User's Manual

3 Getting Started
48 Series N6700 User’s Guide
Using Telnet
In an MS-DOS Command Prompt box type: telnet hostname 5024
where hostname is the N6700 hostname or IP address, and 5024 is
the instrument’s telnet port.
You should get a Telnet session box with a title indicating that you
are connected to the power system. Type the SCPI commands at the
prompt.
Using Sockets
NOTE
Power system mainframes with firmware revision C.00.00 and up installed allow
any combination of up to four simultaneous data socket, control socket, and
telnet connections to be made.
Agilent instruments have standardized on using port 5025 for SCPI
socket services. A data socket on this port can be used to send and
receive ASCII/SCPI commands, queries, and query responses. All
commands must be terminated with a newline for the message to be
parsed. All query responses will also be terminated with a newline.
The socket programming interface also allows a control socket
connection. The control socket can be used by a client to send device
clear and to receive service requests. Unlike the data socket, which
uses a fixed port number, the port number for a control socket varies
and must be obtained by sending the following SCPI query to the data
socket: SYSTem:COMMunicate:TCPip:CONTrol?
After the port number is obtained, a control socket connection can be
opened. As with the data socket, all commands to the control socket
must be terminated with a newline, and all query responses returned
on the control socket will be terminated with a newline.
To send a device clear, send the string “DCL” to the control socket.
When the power system has finished performing the device clear it
echoes the string “DCL” back to the control socket.
Service requests are enabled for control sockets using the Service
Request Enable register. Once service requests have been enabled,
the client program listens on the control connection. When SRQ goes
true the instrument will send the string “SRQ +nn” to the client. The
“nn” is the status byte value, which the client can use to determine
the source of the service request.