
PowerSync Analyzer Reference Manual
March 9, 2010
Sifos Technologies page
20
PSE_Test_Results_Path
: This parameter, if provided, will override the default test reporting path found in the
psa_env.txt
environment file and guide all test results and reports to the specified directory path that can be PSE type
or model specific.
NOTE
: This setting can only be changed by editing the PSE local configuration file directly – the
setting is retained whenever a local configuration file is “loaded”, then “saved” by PSA Interactive or PowerShell.
PSE_Conf_Test_Report
: Specifies a non-standard PSE Conformance Test template (spreadsheet) file for use by the
PSE Conformance Test Suite running on a
PSA-1200
(or PSA-100, PSA-2400). An example might be a re-named copy
of
psa_report.xls
that has modified test limits for a particular PSE type.
NOTE
: This setting can only be changed by
editing the configuration file directly – the setting is retained whenever a local configuration file is “saved” by PSA
Interactive or PowerShell. See Section 5.10 of the PSA-1200 manual for further information.
PSE_MP_Test_Report
: Specifies a non-standard PSE Multi-Port Test template (spreadsheet) file. An example might
be a re-named copy of
mp_report.xls
that has modified test limits for a particular PSE type.
NOTE
: This setting can
only be changed by editing the configuration file directly – the setting is retained whenever a local configuration file
is “saved” by PSA Interactive or PowerShell. See Section 6.11 for further information.
Note that changes to PSE Local Configuration Files required to make existing files compatible with PSA 3.4 Version
software will occur automatically after software is updated and those PSE Local Configuration Files are loaded or
saved.
2.4.5.
Directory and File Organization – Microsoft Windows
When PowerSync Analyzer software is installed to a Microsoft Windows
®
PC, files will be populated to particular
directories as described in the following table.
Directory Path
Directory
Files
PowerShell Script Library
PowerShell Wish and PowerShell Tcl Executables
PSA Initialization Script
PowerShell Wish and PowerShell Tcl resource files
\documentation\
Various PSA reference documents
C: \Program Files\Sifos\PSA1200
\PSA Interactive\ PSA Interactive Script Library and various library sub-
directories to support PSA Interactive functions (plotchart,
tkprint1.1, tbcload14, etc.).
PSA Interactive Executable
PSA Interactive resource file
\Config\
PSA (local) Configuration Files including \Config\env
environment file sub-directory.
\Results\
PSA Test Report Files
Including
psa_report.xls
,
mp_report.xls
,
and
service_report.xls
template report spreadsheets and the
psa_trace.xls
trace display spreadsheet. Chassis-specific
subdirectories under \Results will automatically be created as
needed by PowerSync Analyzer software.
\Emul\
Files only used when PSAsoftware is placed in “Demo Mode”
(also called Emulation Mode).
Windows NT – Windows XP
C: \Program Files\Sifos\PSA1200
Windows Vista – Windows 7
C:\Users\Public\Sifos\PSA1200
\Contrib\
Tcl scripts stored in this directory will automatically source
into PowerShell. This directory includes various sample
scripts at installation.
Version information concerning individual PowerSync Analyzer software libraries is available from PSA Interactive
under the [
Help
] menu as well as from PowerShell using the
psa_version
command.
2.4.6.
Directory and File Organization – Linux and Unix
PSA Software installs into Linux and Unix in a manner that separates and organizes files into 3 categories:
Category
File Locations
Compiled Software and Libraries
/usr/local/Sifos/PSA1200
Configuration and User Data
<User’s Home Directory>/ Sifos/PSA1200
Shell Scripts (Program Launchers)
<User’s Home Directory>/bin
This organization allows various users in a shared computing or NFS type of environment to maintain local user
information independent from other users and independent of the actual shared software modules and libraries.
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 ...