
PVA-3000 Reference Manual
December 2, 2019
Sifos Technologies
Page
129
6.2.2.
Initial Connection Dialog Control
– PowerShell Wish (and PSA Interactive)
Whenever
PowerShell Wish
(or
PSA Interactive
) is initiated, the user is presented with a PSA Connection dialog that
must, by default, be completed before the application will fully start.
Users may elect to either bypass this dialog entirely by setting the value of the global variable
psaConnectPause
found
near the beginning of
wishrc.tcl
and
wishrc_psapi.tcl
. If the value is set to 1 (default), the initial PSA connection
dialog will always occur and wait indefinitely for a user selection. If the value is set to 0, the connection dialog will be
bypassed and the application will automatically attempt to connect to the most recently connected PSA address.
NOTE
!
It is generally not a good idea to bypass the initial connection dialog if multiple (2 or more) PSA chassis’
exist on a common LAN and are shared by multiple users. Bypassing the initial connection dialog increases the risk
that 2 users will attempt to control the same PSA at the same time.
6.2.3.
Tcl Version Compatibility
PowerShell PSA is developed and tested on platforms running Tcl version 8.4.5 through 8.4.12. PowerShell PSA is
distributed in compiled bytecode format, along with a bytecode loader implemented in a binary library compatible with
the installation platform: a Dynamic Link Library (.dll) for Microsoft Windows, or a Shared Object Library (.so) for
Linux or Sun Solaris.
The Tcl bytecode loader extension package (tbcload) that is furnished with PowerShell PSA is
tbcload14
. Sifos
does not warrant that PowerShell PSA will load properly with other versions of this extension package.
PowerShell PSA has not been tested with Tcl versions 8.5 or later, and is not supported for use with newer Tcl
versions.
6.3.
Managing PowerShell from External Applications
There are various methods that can be used to work with PowerShell PSA from an external application context. In all
cases, it is recommended that the native PowerShell PSA scripting environment be used to develop and debug the
commands or scripts that perform the desired actions with the instrument, and then transition those commands to the
automation technique appropriate for the external application context the user needs to use.
PowerShell PSA can be accessed from external applications using the following methods:
1.
Application Programming Interface (API) Library
(accessible to any programming environment that can
call functions in either a Windows .dll or Linux .so library). Used primarily for compiled language support.
2.
Socket Interface
(accessible to any programming environment that can read and write a TCP/IP socket).
3.
Mailbox File
(available to any environment that is capable of creating files, and polling for the presence of
files).
4.
Batch Mode
(available to any environment that is capable of launching an executable with command line
arguments).
6.3.1.
API Library
The PhyView Analyzer API Library provides functions that allow all of the fundamental capabilities of the Sifos
PhyView Analyzer to be configured or queried. Each of these functions accepts specific arguments and returns values
to specific parameters. The library includes a general purpose function that will allow any valid Tcl command string
(including PowerShell PSA commands) to be submitted for execution, with the Tcl list response returned as delimited
text.
The API Library provides a very robust means of performing specific actions with the PhyView Analyzer, where each
function defines exactly what it needs for input (input parameters), and exactly what will be returned (output
parameters, for any function that returns values). Each function returns the status of its execution. If that status
indicates that an error occurred, an API library function that furnishes a related error message text can be called. This is
the recommended technique for remote control for application environments that are capable of calling library
functions.
The PhyView PSA API Library is furnished in binary form, along with language specific definition files for various
languages including C, Visual Basic, C#, and National Instruments LabView.
PowerShell PSA and a supported version of Tcl must be installed on the system where the API library will be used.
The
PhyView API Library Reference Manual
(
PhyView API Library Ref Manual.pdf
) provides information
regarding the functions provided in the library, and usage with selected programming languages.
Содержание PhyView PVA-3000
Страница 22: ...PVA 3000 Reference Manual December 2 2019 Sifos Technologies Page 22 ...
Страница 70: ...PVA 3000 Reference Manual December 2 2019 Sifos Technologies Page 70 ...
Страница 108: ...PVA 3000 Reference Manual December 2 2019 Sifos Technologies Page 108 ...
Страница 124: ...PVA 3000 Reference Manual December 2 2019 Sifos Technologies Page 124 ...