
PowerSync Analyzer Reference Manual
March 9, 2010
Sifos Technologies page
138
The command passing file must
be created with each PowerShell
command or command sequence
and associated arguments
organized as a list. Each
command must be surrounded in
braces
{ }
to accomplish this.
The following command passing
file is an example of a sequence
that connects to a PSA chassis,
configures it for a particular PSE
type, then runs the PSE
Conformance Test Sequencer on
4 ports (3 commands):
c:\Program Files\Sifos\PSA1200\Config\env\psa_command.txt:
When PowerShell TCL completes execution of all passed commands, it will create a short ascii text file
c:\Program Files\Sifos\PSA1200\Config\env\psa_response.txt
that will simply contain the value “DONE”. This serves as a handshake to the outside process that other commands
may be passed into PowerShell TCL. The outside, or executive process may then remove that file if it chooses to.
A special command can be passed to PowerShell TCL to end Remote Command Processing and allow it to return a
normal PowerShell interactive prompt. This command is:
psa_echo_off
This command will enable any subsequent commands entered into the PowerShell TCL resource file to execute, such as
a possible “exit” command discuss below.
8.4.3.
Returning Test and Measurement Results to Host Applications
Generally, the above method for interactive interfacing with PowerShell is best applied when the commands passed to
PowerShell are actually automated test scripts written with the PowerShell API and stored into the
…PSA1200/Contrib/
directory. These scripts should be written to collect any test data or query results, and store
those to any user-specified ASCII file for passing back to a host application outside PowerShell and Tcl/Tk. For
example:
PowerShell test sequencers for
PSE Conformance Test Suite
and
PSE Multiport Test Suite
provide this capability
through simple command arguments to specify test file names and locations. Those files can be ascii text files or .csv
(.xls) files that are created as those sequencers run. Sections 4.13 and 4.14 provide further information concerning the
use of the
sequence
and
multiport
commands including file handling arguments.
{
psa
192.168.221.106
}
{
psa_pse
myPSE
}
{
set portList
"1,1 1,2 2,1 2,2"
}
{
myTestProgram
$portList
}
Figure 8.13
PowerShell Tcl Opent to Interactive Command Processing Mode
{
psa
192.168.221.106
}
{
myTestProgram
"1,1 1,2 2,1 2,2 3,1 3,2" –file myResultsFile.txt
}
Summary of Contents for PowerSync PSA100
Page 26: ...PowerSync Analyzer Reference Manual March 9 2010 Sifos Technologies page 26 ...
Page 56: ...PowerSync Analyzer Reference Manual March 9 2010 Sifos Technologies page 56 ...
Page 84: ...PowerSync Analyzer Reference Manual March 9 2010 Sifos Technologies page 84 ...
Page 110: ...PowerSync Analyzer Reference Manual March 9 2010 Sifos Technologies page 110 ...
Page 120: ...PowerSync Analyzer Reference Manual March 9 2010 Sifos Technologies page 120 ...