Publicité
E
Communicating Through
TCP/IP Over Telnet
The EXFO Instrument Control provides SCPI automation or remote control
over Telnet through TCP/IP as a Windows Service that continuously listens
to a port from a Telnet server (FTB/IQS/LTB) on which modules to be
tested are connected.
Two types of commands can be sent over Telnet: SCPI commands and
internal protocol commands of the TCP/IP over Telnet service. The internal
commands allow you to perform actions such as send SCPI commands as
a script instead of one by one, force the disconnection of an active session,
view the status of modules and of connected clients, etc.
Executing SCPI Commands Over Telnet
You can remotely control the modules by executing SCPI commands
through TCP/IP over Telnet. The commands are sent remotely from the
Telnet client (on a computer) to the Telnet server (in this case, the IQS,
FTB, or LTB unit).
You can connect from a remote Windows or Linux (or Unix) client.
Note: The Telnet client is available on almost all units in case you intend to use
these units as computers to connect to a Telnet server. However, on an
FTB-1v2, FTB-2, or LTB-1 running Windows Embedded 8 Standard, the
Telnet client is not available. With these units, you must use the PuTTY
application to establish communication.
Before being able to send SCPI commands, you must first establish a
connection to the Telnet service.
Note: Socket (raw) connections are also available to send SCPI commands
through TCP/IP, but these connections do not support the internal protocol
commands listed hereafter. Such connections are similar to a
communication over GPIB or RS-232 where you send SCPI commands to
the instrument and read back responses over the opened socket
connection, but without the extra message information found in Telnet.
FTB-2/FTB-2 Pro and FTB-4 Pro
499
Publicité
