Remote Operation Getting Started Guide
Example remote control procedures
Transport Module, DMC, MSAM, and 5800 Remote Operation 23
> :SYSTem:ERRor?
0, "No error"
> :INITiate
Start the test. (When applications are launched through remote control, they begin in
the "stopped" state).
> :SYSTem:ERRor?
0, "No error"
When using remote control with the GUI enabled and an desired application is already
running, a similar process can be followed to connect to it. Use the ":SYSTem:APPLica-
tion:CAPPlication?" query to find its application id, select the application, then create and
start a remote session. ":INITiate" only needs to be sent if the test is in the "stopped" state.
This example also illustrates use of the :SYSTem:ERRor? query. The user should have this
command sent automatically after every non-query command and the 0, "No error"
response should be expected. Doing so will provide vital information in the event of a
command error or connection issue.
Restarting the test
To restart the test using remote control, send the test stop command followed by a test start.
> :ABORtTest stop
> :INITiateTest start
Using setups, actions,
and results (inserting
and checking an
alarm)
The following commands demonstrate the use of application setups, actions and results. In
this example, assume we have launched and initialized the DS1 BERT Terminate applica-
tion (TermDs1Bert). Lines starting with ">" indicate commands sent by the user.
> :SOURce:ALARm:TYPE?
Query the current alarm type setup
"Ds1LofAlarm"
Note: some query commands return values with double quotes (") and some do not.
Making remote control scripts quote-insensitive when checking returned values is
highly recommended.
> :SOURce:ALARm:TYPE Ds1AisAlarm
Set the alarm type setup to AIS.
> :SOURce:PDH:DS1:INSert:AIS ON
Enable the AIS alarm insertion action
> :SOURce:PDH:DS1:INSert:AIS?
Query the current state of the AIS alarm insertion action
ON
To Next Page
Loading...