Please see the Readme.txt for information on the compatibility of this package with previous versions of the application and the Test Management Environment.
Keysight TME is no longer packaged and installed with TME applications. TME must be installed separately. Once TME is installed on the target PC, the applications can then be installed.
Please see the TME help system and Readme for information on installing the Keysight Test Management Environment.
Please see the Readme.txt for minimum system requirements to run this application.
There are two ways to install TME and its applications:
Network Installations - Equipment and test data information is stored in a central location (the TME Server). This data is shared among a set of TME Clients. Multiple test stations can then have access to this central information.
Local Installations - Everything is installed on one PC
In a network installation, order information is stored centrally and can be accessed by any TME client in the network. This allows you to combine data from tests that were run on multiple stations into a single report. Equipment data and order information are also accessible from any station
To set up a new TME network, please see the instructions in the TME help system.
|
|
|
To install an application on a network follow the following steps:
Find the PC where the TME network was installed (Shows “TME Server” in Add/Remove Programs or Programs and Features depending on the OS).
Run Setup.exe for the application on that PC. This will install all networked components for that application.
Install application clients:
TME clients will be asked to install the application the next time TME is started.
Or
Applications can be installed by running the setup file from the network directory:
\\FileServer\Test Management Environment\Install\(AppName)\(AppName)ClientSetup.exe
|
|
The client setup must be run from this location. It should not be moved or renamed. |
TME must be installed on the target PC before the application installation can occur.
On a local installation, all application data is stored on the target PC. Once TME has been installed as a local installation the application installation will automatically install locally when executed. Order information, test results, and equipment data will not be shared with other users.
|
|
If you uninstall TME completely or uninstall any TME application, you will lose the data associated with those applications. Create any reports needed and save them as PDF files before you perform any uninstallation of that product. |
To uninstall previous versions of TME, please see Installing over Previous Versions.
To uninstall TME or any TME application, select that package from Add/Remove Programs or Programs and Features depending on the OS.
To uninstall an application client, select that package from Add/Remove Programs or Programs and Features depending on the OS and click Remove.
|
|
Data will not be lost if only a client is uninstalled. Other clients will still have access to the data in the network. |
To uninstall an application server:
Follow the directions above to uninstall all application clients.
Once all application clients have been uninstalled, uninstall the application server from the PC where the server installation was performed.
Select the application server from Add/Remove Programs or Programs and Features depending on the OS and click Remove.
To uninstall an application local installation, select that package from Add/Remove Programs or Programs and Features depending on the OS and click Remove.
Protection against ESD (electrostatic discharge) is essential while connecting, inspecting, or cleaning connectors attached to a static-sensitive circuit (such as those found in test sets). Static electricity can build up in your body and can easily damage sensitive internal circuit elements when discharged. Static discharges too small to be felt can cause permanent damage. Devices such as calibration components and units under test (UUTs) can also carry an electrostatic charge. To prevent damage to the test set, components and devices:
Always wear a grounded wrist strap having a 1 million Ohm resistor in series with it when handling components and devices or when making connections to the test set.
Always use a grounded antistatic mat in front of your test equipment.
This section describes the preparation of the instruments used by the test software at a given test station. The test software does not check instruments for proper operation on the GPIB bus before attempting to perform tests.
The typical GPIB address configuration for a test station is:
|
Spectrum Analyzer |
18 |
|
Power Meter |
13 |
|
Frequency Counter |
3 |
|
Source |
19 |
|
Network Analyzer |
16 |
|
DVM |
22 |
|
Function Generator |
10 |
|
Oscilloscope |
4 |
It is recommended that the operator follow the steps below to manually check for proper connection of the GPIB devices before performing tests on a newly connected test station.
Note the GPIB address of each instrument associated with the test station/test plan defined earlier.
Connect a power cord to each instrument, and then connect each instrument to the computer serving as the GPIB controller.
Power up all the instruments on the GPIB bus.
Check each GPIB instrument for proper communication over the bus and the required "detectable" options. Follow the process described in "Checking GPIB Bus Devices" below.
|
|
When checking for basic operation of each GPIB device or when checking for detectable options on a given device, you may have to look up the actual command for retrieving the identification string before performing these procedures. |
The following applies only to Keysight/HP GPIB cards; a different program is used for National Instruments GPIB cards.
Start the VISA Assistant:
Select the "hp" or the IO box on the right
side of the task bar or access it through: Start/Programs/Keysight
I_O Libraries/VISA Assistant.
Check for all expected GPIB devices:
Verify that all expected GPIB devices are shown
in the left window.
If a device is missing, correct the problem and restart the VISA
Assistant.
Check all GPIB device addresses:
Verify that no two GPIB addresses are the same.
Follow the process described in the user manual for the device if an address needs to be changed. The following numbers are reserved and are not available for GPIB addresses: 0, 1, 21, 31.
After changing the address of the device, go to
the Administration area, highlight the device icon, and enter the correct
GPIB address into the Address field.
Check for basic operation of each GPIB device:
|
|
If an instrument does not support SCPI, refer to the user guide for your product to learn more about checking the basic operation of its GPIB. |
Select a GPIB device to highlight it.
Select the "Formatted I/O" tab (expand the window if needed).
Select the SCPI radio button.
Select on the "*IDN?" button.
Check to see that the expected model number is contained in the response text string.
Check for detectable options on a given device:
Select a GPIB device to highlight it.
Select the "Formatted I/O" tab.
Select the SCPI radio button.
Enter "*OPT?" and select "viQueryf".
A "detectable" option is one that can be detected through the GPIB.
There are three choices for test variants you can select when setting up your test system.
The Factory Recommended variant is the suite of tests that the factory recommends. This variant has four tests removed:
|
Gain Compression and TOI are both two tone measurements. Gain Compression meets its specified performance if TOI performance passes specification. |
|
|
The IF Phase Ripple test has been removed because the IF Amplitude Ripple test measures the same IF performance that the IF Phase Ripple test measures. The IF Amplitude Ripple test procedure was re-written to test to a much more aggressive limit; thus the IF Phase Ripple measurement was redundant testing. |
|
|
These two tests have been collapsed into one Noise Sidebands Performance Test. This test will allow either the PSG/notch filter, or the Wenzel source to be used. If the Wenzel source is not mapped, the test will assume that the PSG/notch filter solution is being used. The 8663A/8665B legacy sources cannot be used in this test. |
The Normal Variant allows the operator to provide a test report that is consistent with previous test reports. It contains the four tests listed above that were removed from the Factory Recommended Variant.
This test variant contains a Banded Frequency Response measurement. The reason for providing a Banded Frequency Response measurement is to save time when troubleshooting a Frequency Response failure. Frequency Response testing can be time consuming. With the banded test, the operator can test one frequency band of the PSA rather than all bands.
