содержание .. 28 29 30
FTB-2 и FTB-2 Pro. Руководство пользователя - часть 30
Communicating Through TCP/IP over Telnet
Executing SCPI Commands Over Telnet
6. Enter the desired SCPI commands as follows:
For a single SCPI command: Type or copy the desired command in
the Telnet editor window, and then press ENTER to execute it.
For multiple SCPI commands: Copy the desired commands from
any script file, enclose them in a BEGIN and END block in the
Telnet editor window, and then press ENTER. For more
information, see Internal Commands of the TCP/IP over Telnet
Protocol on page 459.
Note: Multiple commands that are not enclosed in BEGIN...END blocks will be
executed, but problems may occur (results of one command mixed with
the results of another one, skipped commands, etc.).
Once at least one valid command is executed, the module is blocked
for any other sessions until the module is released. For more
information, see Releasing Modules on page 458.
FTB-2 and FTB-2 Pro
455
Communicating Through TCP/IP over Telnet
Executing SCPI Commands Over Telnet
7. Click
to close the session.
To connect through TCP/IP over Telnet from a remote Linux client:
1. From your computer, right-click on the desktop, and then click Open
Terminal.
The command prompt is displayed in the Telnet editor window.
2. Connect to the TCP/IP Telnet Service by typing the
OPEN <IP_ADDRESS_OF_TELNET_SERVER> <PORT> command:
Example: open 10.192.2.45 5024
Note: Port 5024 is designated for sending SCPI commands in the Telnet protocol.
The connection is established when the message Connected to
Toolbox/IQS Manager is displayed in the Telnet editor window.
456
FTB-2 and FTB-2 Pro
Communicating Through TCP/IP over Telnet
Executing SCPI Commands Over Telnet
3. Enter the desired SCPI commands as follows:
For a single SCPI command: Type or copy the desired command in
the Telnet editor window, and then press ENTER to execute it.
For multiple SCPI commands: Copy the desired commands from
any script file, enclose them in a BEGIN and END block in the
Telnet editor window, and then press ENTER. For more
information, see Internal Commands of the TCP/IP over Telnet
Protocol on page 459.
Note: Multiple commands that are not enclosed in BEGIN...END blocks will be
executed, but problems may occur (results of one command mixed with
the results of another one, skipped commands, etc.).
Once at least one valid command is executed, the module is blocked
for any other sessions until the module is released. For more
information, see Releasing Modules on page 458.
4. Click
to close the session.
FTB-2 and FTB-2 Pro
457
Communicating Through TCP/IP over Telnet
Releasing Modules
Releasing Modules
A module is blocked as soon as a connection is established from any user
session executing the internal command CONNECT LINS, or a valid
instrument (SCPI) command.
For example, when the SCPI command
LINS10:SOURce:DATA:TELecom:CLEar command is executed for the first
time by client session 10.192.2.155:1364, the module is blocked for any
other client/session until you release it.
A module is released by one of the following actions:
Executing the CLOSE LINS command to disconnect the link with the
module. For more information, see CLOSE LINS on page 462.
Executing the CLOSE command to end the current session once the
execution of all the desired commands has been completed. For more
information, see CLOSE on page 461.
Closing the current session by clicking the Close button on the Telnet
editor windows’ title bar.
Shutting down and restarting the client computer.
A network interruption.
A module can also be released when you terminate the communication by
using the KILL LINS command. For more information, see KILL LINS on
page 464.
458
FTB-2 and FTB-2 Pro
Communicating Through TCP/IP over Telnet
Internal Commands of the TCP/IP over Telnet Protocol
Internal Commands of the TCP/IP over Telnet
Protocol
The internal commands allow you to perform certain 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. The internal commands are not case-sensitive.
By default, log files are generated both for client and server (all logs are
kept on your unit). You can delete them with the CLEAR LOGS command
(see CLEAR LOGS on page 461), or manually via the file explorer. The client
and sever logs are kept respectively in the C:\ProgramData\EXFO\SCPI
Over TCPIP Logs\Client log and in the C:\ProgramData\EXFO\SCPI Over
TCPIP Logs\Server log folders.
ABORT BEGIN
Syntax: ABORT BEGIN
The ABORT BEGIN command stops the execution of the SCPI commands
that are enclosed in a BEGIN and END block, and returns to the READY>
prompt in the Telnet editor window.
FTB-2 and FTB-2 Pro
459
Communicating Through TCP/IP over Telnet
Internal Commands of the TCP/IP over Telnet Protocol
BEGIN and END
To execute multiple SCPI commands, you must enclose them in BEGIN
and END blocks in a Telnet editor window.
Note: To execute a single command, simply type or paste the command in the
Telnet editor window.
Note: You cannot enclose internal commands in a BEGIN and END block, except
the ABORT BEGIN command.
460
FTB-2 and FTB-2 Pro
Communicating Through TCP/IP over Telnet
Internal Commands of the TCP/IP over Telnet Protocol
CLEAR LOGS
Syntax: CLEAR LOGS
This command clears all the client and server log files that are older than
36 hours (default value) from the time you execute the command.
Note: You can also delete the logs manually via the file explorer. The client and
sever logs are kept respectively in the C:\ProgramData\EXFO\SCPI Over
TCPIP Logs\Client log and in the C:\ProgramData\EXFO\SCPI Over TCPIP
Logs\Server log folders.
CLOSE
Syntax: CLOSE
The CLOSE command terminates the current Telnet session.
FTB-2 and FTB-2 Pro
461
Communicating Through TCP/IP over Telnet
Internal Commands of the TCP/IP over Telnet Protocol
CLOSE LINS
Syntax: CLOSE LINS<Unit_Number><Module_Slot_Number>
You must specify the unit number and the slot number identifying the
module for which you want to close the connections.
This command allows to close active connections. You can send this
command to close all client’s connections with any module, including the
current connection.
If the command is not executed successfully, the possible reasons could
be:
The module is not present at the specified position.
The provided information does not correspond to a valid LINS.
462
FTB-2 and FTB-2 Pro
Communicating Through TCP/IP over Telnet
Internal Commands of the TCP/IP over Telnet Protocol
CONNECT LINS
Syntax: CONNECT LINS<Unit_Number><Module_Slot_Number>
You must specify the unit number and the slot number identifying the
module to which the session will connect.
This command allows to connect to different modules through TCP/IP. You
can connect to multiple modules from a single session.
If the command is not executed successfully, the possible reasons could
be:
The module is already connected to a different client session.
The module is not present at the specified position.
The provided information does not correspond to a valid LINS.
Note: For backward compatibility reasons, to connect to a single module, you do
not have to use the CONNECT LINS command. A valid instrument
command (for example, Lins10:SOURce:DATA:TELecom:CLEar) for a valid
LINS position will work for a first module. However, you will need to use
the CONNECT LINS command if you want to connect to other modules as
well.
FTB-2 and FTB-2 Pro
463
Communicating Through TCP/IP over Telnet
Internal Commands of the TCP/IP over Telnet Protocol
KILL LINS
Syntax: KILL LINS<Unit_Number><Module_Slot_Number>
You must specify the unit number and the slot number identifying the
module for which you want to terminate the session.
This command allows any user to terminate the session that contains the
specified connection (LINS). This means it will terminate all active
connections that belongs to a session.
To know the status of the modules before terminating connections using
the KILL LINS command, you can first enter the STATUS CLIENT
command. For more information, see STATUS CLIENT on page 465.
In the example below, two modules are connected: LINS13 and LINS10.
To disconnect the LINS10 module used by another session, enter the kill
lins10 command. The This client session is terminated message is
displayed once the module is disconnected.
464
FTB-2 and FTB-2 Pro
Communicating Through TCP/IP over Telnet
Internal Commands of the TCP/IP over Telnet Protocol
Enter again the STATUS CLIENT command to confirm the termination of
the module (LINS10 in our example). Only the information of the
remaining connected client is displayed.
STATUS CLIENT
Syntax: STATUS CLIENT
This command lists out all clients with their connection time and modules.
STATUS CONNECTION
Syntax: STATUS CONNECTION
This command lists out all the connections with their Idle or Active status.
Note: If any connection is idle for a certain period (5 minutes by default), the
service automatically changes the status to Idle.
FTB-2 and FTB-2 Pro
465
Communicating Through TCP/IP over Telnet
Internal Commands of the TCP/IP over Telnet Protocol
STATUS MODULE
Syntax: STATUS MODULE
This command lists out all the modules with the slot numbers where they
are located.
WHO M I?
Syntax: WHO M I?
This command retrieves the IP address and the communication port of the
current session.
466
FTB-2 and FTB-2 Pro
Указатель
Указатель
communication
A
ActiveX
238
ActiveX
changing settings
242
control
238
default settings
245
linking units
239
Ethernet TCP/IP
237, 238
selecting
243
RS-232
237, 238
angled brackets
282
TCP/IP over Telnet
238, 449-452
ASCii format
241
ConnectorMax2
159
automation
237
control
ActiveX
238
Ethernet TCP/IP
237, 238
B
remote
237
Bluetooth
RS-232
238
данные о диапазоне частот
x
TCP/IP over Telnet
238
компонент
18
controlling modules
237
ограничения
164
conventions, programming
280, 283, 285
передача данных
164
copying
устройства
78
commands into text document
288, 290
braces
282
brackets
angled
282
D
square
281
data
types
361
data input
C
IEEE 488.2
362
changing
SCPI
381
communication settings
242
data output IEEE 488.2
codes, error
286
special
374, 382
colon
282
standard
371
COM, local control
238
DCOM
COM/DCOM
configuring computers
246
events
448
technology
238
properties
441
digit
281
comma
283
commands
IEEE 488.2
384
SCPI
280
specific
405
TCP/IP
459-465
467
Указатель
E
O
error messages in remote control
286
output IEEE 488.2
Ethernet TCP/IP
special
374, 382
control
237, 238
standard
371
port
239
Explorer, Internet
143
P
PACked format
241
I
pipe character
282
IEEE 488.2 commands
384
platform commands
405
input
port
IEEE 488.2 data types
362
Ethernet
239
SCPI data types
381
product
instrument control settings
242
specifications
359
programmable instruments,
standards
237, 280
K
keywords, SCPI
282
R
receiving data
L
with Ethernet port
239
LAN network
238
register
linking units
diagram
278, 279
Ethernet port
239
ESE
276
list separator
282
ESR
276
local control
238, 243
SRE
276
STB
276
M
remote control
mandatory commands
384
ActiveX (DCOM)
238, 239
mnemonic, definition
282
configuring
243, 246, 451
module
description of commands
280
controlling
237
error messages
286
monitoring remote commands
287
methods
237
multiple capabilities
281
monitoring
287
RS-232
237, 238
TCP/IP
238, 449-465
N
reverting to default settings
245
network, LAN/WAN
238
RS-232
communication
237
control
238
selecting
243
468
Указатель
rules
features
450
programming
285
introduction
449
syntax
283
port number 5024
449
syntax conventions
280
release examples
458
selecting
243, 452
technical specifications
359
S
ToolBox X
SCPI
параметры
132
commands
280
приложения
156
data types
381
язык
103
guidelines
237, 280
types, data
361
semicolon
283
sending data
with Ethernet port
239
U
separator
282, 283
USB
service request enable register (SRE)
276
порты
4, 6
setting
устройство
76
instrument control utility
242
space
281
V
specific commands
405
vertical bar
282
specifications, product
359
VFL
square brackets
281
очистка
293
standard event status
enable register (ESE)
276
register (ESR)
276
W
standard status data structure
WAN network
238
diagram
278, 279
white space
281
general
276
Wi-Fi
status byte register (STB)
276
данные о диапазоне частот
x
syntax
компонент
18
rules
280, 283
подключение
174
SCPI
280
Windows
symbols
281
Embedded 8 Standard
63
версия 8.1 Pro
63
обновление приложений
311
T
wsp
281
TCP/IP
activating
451
commands
459-465
А
configuring parameters
244
автоматическая
connecting to Linux
456
скорость вентилятора
17
connecting to Windows
452
автоматические
control
237, 238
обновления Windows
311
469
Указатель
адаптер
26
вправо, прокрутка
63
модулей
4
вставка
активация экранной клавиатуры
62
батареи
298
антивирусное программное
модуль
4, 5, 41
обеспечение
74
выбор
аппаратная клавиатура
76
параметры управления питанием
118
приложений при запуске
98
часовой пояс
117
Б
язык
103
батарея
16
выключение
допустимый тип
298
Wi-Fi
187
замена или извлечение
298
устройство
51
индикатор
3
выход из ToolBox X
60
ошибка
12
рекомендации по обслуживанию
295
уровень
295
Г
безопасность
гарантия
внимание!
20
аннулирование
354
информация
23
исключения
355
предостережение
20
общая
353
условные обозначения
20
ответственность
355
безопасность устройства
75
сертификация
356
беспроводная
гарнитура
сеть
174
Bluetooth
78
беспроводное
громкость динамика
80, 137
внутреннее устройство
187
грязные волокна
159
соединение
144
беспроводной
Д
принтер
78
дата
беспроводные
передача
164
мышь и клавиатура
78
дата и время
быстро мигающий индикатор
12
настройка
117
форматы
115
В
датчик волокон
159
Веб-браузер
143
датчик для проверки
159
вентиляция
25
деактивация Wi-Fi
187
виртуальная частная сеть (VPN)
191
дефектоскоп
включение беспроводного устройства
187
доступ
157
влево, прокрутка
63
опция
4
внешний источник питания
26
дисковое пространство, свободное
162
вниз, прокрутка
63
документация
340
возврат оборудования
357
документы, печать
139
470
содержание .. 28 29 30