E6562C WCDMA Wireless Test Manager Revision Information

 

Last updated: 8/04/06

© Copyright 2004-2006 Agilent Technologies

All Rights Reserved

 

This document describes the features that are in the Agilent Technologies E6562C WCDMA Wireless Test Manager releases. This document contains the original features, as well as enhancements that have been added over time. To get answers to frequently asked questions, as well as details on how to fix known problems, go to the web page http://www.agilent.com/find/E6562C and click on the Technical Support link below Key Library Information.

 

Select the appropriate link below to view the required release.

 

C.02.00 Release – August 2006

 

C.01.01 Release – May 2005

 

C.01.00 Release – July 2004 (initial release)

 

Contact Information

Service and Support

 

C.02.00 Release – August 2006

 

C.02.00 Release – Overview

W-CDMA Wireless Test Manager  Modifications

Supported 8960 Test Applications

 

Known Issues

Installation Issues

Uninstalling older software versions

Uninstalling all software versions

The USB security key is not recognized after installation

Back-up language files

??? <reference number> being displayed in the WTM UI

Other Issues

Issues known at shipment release

Issues discovered after release

 

Component Release Information

 

 

C.02.00 release – Overview

 

This software release adds six new tests, 25 new global parameters, new test specific parameters, and provides enhancements to existing test plan steps. In addition, enhancements have been made to the WCDMA Mobile Manufacturing Test - Methods of Measurement (Agilent.WTM.wmmtMoM.dll). To see the latest release notes for the E6562C (includes revision information) go to the Agilent Technologies web site http://www.agilent.com/find/E6562C and select ‘E6562C Release Notes’.

 

W-CDMA Wireless Test Manager Modifications

1.       Added support for HSDPA. This added two new classes with six new test steps and supporting routines. It also added 24 new HSDPA global parameters.

2.       Added support for the Auto uplink channel state through a new global parameter 'WCDMA Uplink Channel State'.

3.       Changed the upper limit of parameter 'MS Target Power' from 24 to 28 dBm in all test steps that use it.

4.       Modified the Max Input Level BER test steps to set DPCH to -19 dB.

5.       Modified the Phase Discontinuity test step to work correctly when the Power Control Pattern parameter is set to 'Five Up Four Down' or 'Five Down Four Up'. Before this change the measurement could time out and the measurement results could be inaccurate depending on how the other test step parameters were set.

6.       Changed the MS Target Power in the Maximum Output Power test step from 24 to 21 dBm.

7.       All calls to the Power Supply now use generic power supply calls.

8.       Fixed an arithmetic overflow exception generated when a channel pair is used that does not exist in the channel pair table.

 

Supported 8960 Test Applications

 

The following TA’s are supported by the C.02.00 release of the E6562C.
 

E1987A

A.04.27 or later

E1963A

A.09.06 or later

 

Known Issues

 

Installation Issues
 

Uninstalling older software versions
 

If the non-NET versions of Wireless Test Manager are uninstalled after the NET version of Wireless Test Manager is installed, the non-NET Wireless Test Manager selection will remain in the Start Programs Menu. You can safely delete this menu item if you desire.
 

Uninstalling all software versions
 

To completely remove both non-NET versions of Wireless Test Manager and the NET version of Wireless Test Manager, first uninstall all versions of the NET version of Wireless Test Manager (See ReadMe.txt section 1.3) prior to uninstalling the non-NET Wireless Test Manager.
 

The USB security key is not recognized after installation
 

Situation: You try to run Wireless Test Manager(WTM), but WTM prompts you with the message "No security or incorrect security key found." even though the security key is inserted into a USB port; or when you insert the security key into a USB port, the Windows Found New Hardware Wizard appears and wants you to install a device driver for the security key.
 

Solution: This problem is usually caused when the key was in the USB port during the WTM installation. This interferes with the installation of the Rainbow Technologies Security Key files.  Perform the following steps to correct the problem:

a.       Cancel or exit from any prompts.

b.       Remove the USB security key from the USB port.

c.        Close all applications that are running.

d.       Check to see that the sx32w.dll and sp32w.dll is installed in the Windows System32 directory.  If the file is not present in the System32 directory, copy the sx32w.dll and the sp32w.dll from the Rainbow Technologies directory on the Wireless Test Manager installation CD to the Windows System32 directory on your PC.  

e.       Run the SSD5411-32bit.exe program in the Rainbow Technologies directory on the WTM installation CD to reinstall the drivers.

f.         Insert the Security Key into a USB port on your PC.   

g.       The Security Key should be recognized next time you run Wireless Test Manager.   

 

Back-up language files
 

Back-up files were created for the language files located in the directories below the ".../WirelessTestManager/Common/" level in case they are written over when installing an older version of the Wireless Test Manager. The release date of this version of the WTM is appended to the name of these language files.

 

??? <reference number> being displayed in the WTM UI
 

Situation1: If any E656xA application (VB6 WTM) is installed after an E656xC/N588xA application (.NET WTM) has been installed, the Agilent WTM framework language files (.lng) will be overwritten by the older language files. This will result in ‘??? <reference number>’ showing up on some WTM user interface objects. This is due to old language files not containing the new messages added in .NET WTM.
 

Situation2: If E6560C 1.0 application is installed after any newer E656xC/N588xA application has been installed.
 

Solution: Restore the backup language file for the appropriate UI (Exec & wizard) that was created when the E656xA or E6560C 1.0 application was installed.

 

Example: If the E6562A application is installed after the E6562C then a file called 'English10152004.lng' (where 10152004 is the file date of the E6562C installed language file) will need to be renamed or copied to replace the 'English.lng' in the default installation directory 'C:\Program Files\Agilent\WirelessTestManager\Common\ExecLocalization'. The 'English10152004.lng' file in the default installation directory 'C:\Program Files\Agilent\WirelessTestManager\Common\WizardLocalization' will also need to be renamed or copied to replace the 'English.lng' in that directory.

 

Other Issues


Issues known at shipment release
 

The localization utility tool (LocalizeUtility.exe) may not work if Visual Studio .Net is not installed.
 

Issues discovered after release

 

Situation:  There is no global parameter for setting the initial band arbitrator (band V or band VI) to go along with the initial downlink channel with no looping and initial channel offset with no looping parameters. The test set will default to band VI.

 

Solution:  If a band V phone is being tested that requires the band arbitrator field to be set to band V then a work around is to surround the test plan with Start Loop/End Loop test steps that loop on one channel. Another work around would be to start the test plan with a Change Channel test step. Both the Start Loop and Change Channel test steps have a parameter for setting the band arbitrator.

 

 

** Note: the following issue only affects those who are using the startup template, supplied to create new, original WTM projects. If you do not use, or plan to use, the startup template, you can disregard this issue. **

 

Situation: The WTM directory on the installation CD contains a starter or template project used to start new WTM projects. The code in the FlowControl.vb module (in the WTM directory on the installation CD) was inadvertently modified which causes the project to now contain errors preventing it from being compiled as is.

 

Solution: One solution is to use the starter project files from a WTM installation CD other than the E6562C or N5882A version 02.00. A second solution (if you do not have an installation CD from another WTM application) is to replace the FlowControl.vb module with one not containing the modified code. A good FlowControl.vb file can be obtained by contacting your Agilent field representative and requesting a copy of the WTM Starter project FlowControl.vb file.


To find the latest information about component and application release notes, visit the following Agilent Technologies web site http://www.agilent.com/find/wtmanagers and select the ‘E6562C WCDMA Wireless Test Manager’ product and then the ‘E6562C Release Notes’ link.

 

Component Release Information

 

The following components will be installed with the Development installation of this release:

 

<Target Directory>\E6562C\RunTime

              E6562C_WCDMA_SAM_Net.exe

              Agilent.WTM.wmmtMoM.dll

 

Revision 2.0.0.0

Revision 2.0.0.0

 

 

<Target Directory>\Common

              Agilent.WTM.wmmtMoM.dll

              TestPlanMover.exe

              LocalizeUtility.exe

              WTMDataAnalyzer.exe

 

Revision 2.0.0.0

Revision 1.5.0.0

Revision 1.1.0.0

Revision 1.3.0.0

 

 

<Target Directory>\Common\NETWizards

              Agilent.WTM.AddInstrumentControl.dll

              Agilent.WTM.AddWirelessTest.dll

 

Revision 1.2.0.0

Revision 1.2.0.0

 

 

<Target Directory>\Common\NetWTMVersion1.X\Assemblies

              Agilent.WTM.Exec.dll

              Agilent.WTM.ag34970MoM.dll

              Agilent.WTM.gpioMoM.dll

              Agilent.WTM.psmtMoM.dll

              Agilent.WTM.MoMMUIServices.dll

              Agilent.WTM.MSJRO.Interop.dll

              Agilent.WTM.PathEffectServices.Interop.dll

              ScDerivedControls.dll

              ScUserControls.dll

 

Revision 1.8.0.0

Revision 1.1.0.0

Revision 1.1.0.0

Revision 1.3.0.0

Revision 1.0.0.0

Revision 2.6.0.0

Revision 1.0.0.0

Revision 1.0.1389.23550

Revision 1.0.1389.23557

 

 

<Target Directory>\WINNT\Assembly (Win2k)

<Target Directory>\WINDOWS\Assembly (XP)

              Agilent.WTM.ag34970MoM.dll

              Agilent.WTM.Exec.dll

              Agilent.WTM.gpioMoM.dll

              Agilent.WTM.psmtMoM.dll

              Agilent.WTM.MoMMUIServices.dll

              Agilent.WTM.MSJRO.Interop.dll

              Agilent.WTM.PathEffectServices.Interop.dll

              policy.1.0. Agilent.WTM.ag34970MoM

              policy.1.0. Agilent.WTM.ag34970MoM

              policy.1.0. Agilent.WTM.Exec

              policy.1.0. Agilent.WTM.Exec

              policy.1.1. Agilent.WTM.Exec

              policy.1.2. Agilent.WTM.Exec

              policy.1.3. Agilent.WTM.Exec

              policy.1.4. Agilent.WTM.Exec

              policy.1.5. Agilent.WTM.Exec

              policy.1.6. Agilent.WTM.Exec

              policy.1.7. Agilent.WTM.Exec

              policy.1.0. Agilent.WTM.gpioMoM

              policy.1.0. Agilent.WTM.gpioMoM

              policy.1.0. Agilent.WTM.MoMMUIServices

              policy.1.0. Agilent.WTM.PathEffectServices.Interop

              policy.1.0. Agilent.WTM.psmtMoM

              policy.1.0. Agilent.WTM.psmtMoM

              policy.1.1. Agilent.WTM.psmtMoM

              policy.1.2. Agilent.WTM.psmtMoM

              policy.2.6. Agilent.WTM.MSJRO.Interop

              ScDerivedControls.dll

              ScUserControls.dll

 

 

Revision 1.1.0.0

Revision 1.8.0.0

Revision 1.1.0.0

Revision 1.3.0.0

Revision 1.0.0.0

Revision 2.6.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.1.0.0

Revision 1.0.0.0

Revision 1.8.0.0

Revision 1.8.0.0

Revision 1.8.0.0

Revision 1.8.0.0

Revision 1.8.0.0

Revision 1.8.0.0

Revision 1.8.0.0

Revision 1.8.0.0

Revision 1.0.0.0

Revision 1.1.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.3.0.0

Revision 1.3.0.0

Revision 1.3.0.0

Revision 2.6.0.0

Revision 1.0.1389.23550

Revision 1.0.1389.23557

 

 

C:\Program Files\Common Files\Agilent Shared\Wireless

              PathEffectSvc.dll

 

Revision 1.1.0.0

 

 

C.01.01 Release – May 2005

 

C.01.01 Release – Overview

WCDMA Wireless Test Manager  Modifications

Supported 8960 Test Applications

 

Known Issues

Installation Issues

Uninstalling older software versions

Uninstalling all software versions

The USB security key is not recognized after installation

Back-up language files

??? <reference number> being displayed in the WTM UI

Other Issues

Issues known at shipment release

Issues discovered after release

 

       Component Release Information

 

 

C.01.01 release – Overview

 

This software release adds one new test, new global parameters, new test specific parameters, and provides enhancements to existing test plan steps. In addition, enhancements have been made to the WCDMA Mobile Manufacturing Test - Methods of Measurement (wmmtMoM). To see the latest release notes for the E6562C (includes revision information) go to the Agilent Technologies web site http://www.agilent.com/find/E6562C and select ‘E6562C Release Notes’.

 

 

W-CDMA Wireless Test Manager Modifications

1.       The parameter Display Average Maximum and Standard Deviation has been removed from the test steps ACLR, Maximum Output Power, Minimum Output Power, Waveform Quality, and Occupied Bandwidth which no longer display the Maximum and Standard Deviation results. The average results are automatically displayed if the Multi Measurement Count parameter is set to a number > 1.
 

2.       The parameter Measurement Result Type has been added to the test steps ACLR and Waveform Quality since the WCDMA TA’s do not automatically return the average measurement values for these two measurements with a standard fetch when Multi Measurement Count is set to a number > 1.
 

3.       The global parameter WCDMA Channel Type and the parameter New Channel Type in the test step WCDMA Change Channel Type have new choices in the range corresponding to the four new asymmetric channel types in the WCMA TA’s:

a.       RMC AM 1264, RMC AM 12144, RMC AM 12384, and RMC AM 64384

 

4.       The following test steps have been modified to take advantage of new features in the E1963A and E1985B TA’s 

a.       WCDMA Change Channel Type now handles both the symmetrical and asymmetrical RMC channel types.

b.       WCDMA Initiate Maximum Input Level BER, WCDMA Initiate Reference Sensitivity Level BER, WCDMA Measure Maximum Input Lever BER, and WCDMA Measure Reference Sensitivity Level BER can now use the confidence level functionality.

c.        WCDMA Phase Discontinuity can now be set to use the power control patterns 5UP/4DOWN or 5DOWN/4UP.
 

5.       The WCDMA Inner Loop Power Control test step has been modified to align with the 34.121-550 standard section 5.4.2 Inner Loop Power Control in the Uplink by using the max and min power threshold  to determine valid and invalid slots to apply test limits to.
 

6.       The following test step has been added: 

a.        WCDMA Power Control along with the new parameter Power Control Multi Measurement Count and specification Power Error (dB).
 

7.       The following global parameters have been added: 

a.        WCDMA PS Domain Information

b.        WCDMA DRX Cycle Length

c.         WCDMA Cell Identity

d.        WCDMA Handoff Allowed
 

8.       The following test step parameters have been renamed to better align them with the test set TA nomenclature: 

a.       Number of ACLR Measurement Averages has been renamed to ACLR Multi Measurement Count.

b.       Number of Maximum Power Averages has been renamed to Maximum Power Multi Measurement Count.

c.        Number of Spectrum Emission Mask Averages has been renamed to Spectrum Emission Mask Multi Measurement Count.

d.       Number of Averages for Waveform Quality has been renamed to Waveform Quality Multi Measurement Count.

e.       Number of Minimum Power Averages has been renamed to Minimum Power Multi Measurement Count.

f.         Number of Occupied Bandwidth Averages has been renamed to Occupied Bandwidth Multi Measurement Count.
 

9.       The parameter Retry Test if Call is Dropped has been added to the WCDMA Inner Loop Power Control test step.
 

10.    The new test step parameters Bad DUT Factor and BER Confidence Level (Percent) have been added to the WCDMA Initiate Maximum Input Level BER, WCDMA Initiate Reference Sensitivity Level BER, WCDMA Measure Maximum Input Lever BER, and WCDMA Measure Reference Sensitivity Level BER test steps.
 

11.    The new test step parameters Number of Pattern Repetitions and Power Control Pattern have been added to the WCDMA Phase Discontinuity test step.
 

12.    The default upper and lower specification limits for the Inner Loop Power Control test step have been changed to match the test requirements and not the minimim requirements specified in 34.121.

 

13.    The default upper and lower specification limits for the Maximum Output Power test step have been changed to match the test requirements and not the minimim requirements specified in 34.121.

 

14.    The Channel Pair table window is no longer launched by pressing a toolbar icon. It is now launched through a parameter in the Start Loop test step called Channel Pair. The Exec now supports parameter

tables.

 

15.    The WCDMA Registration test step now only waits for one registration instead of two before continuing. It also has a new parameter called “Time To Wait After Registration (Sec)”. This parameter allows the user to force a wait after the first registration in cases where the phone does a second registration when the LAC (local area code) and downlink primary scrambling code are returned to their original values

after the phone registers.

 

16.    The range for the Measurement Interval parameter in the Phase Discontinuity test step has been increased to 2 to 90.

 

17.    The upper limit of the range for the Number Of BER Bits to Test parameter in the BER test steps has been increased to 999999999.

 

18.    The parameter 'Display Turn On Message' has been added to both the WCDMAOpenLoopPowerControl and WCDMATransmitOnOffPower test steps to allow the user to specify if the phone should be power cycled at the beginning of these two test steps.

 

19.    The specification WCDMA BER (Percent) has been moved from the test step WCDMA Fetch Reference Sensitivity Level BER to the test step WCDMA Initiate Reference Sensitivity Level BER.

 

20.    The specification WCDMA BER (Percent) has been moved from the test step WCDMA Fetch Maximum Input Level BER to the test step WCDMA Initiate Maximum Input Level BER.

 

Supported 8960 Test Applications

 

The following TA’s are supported by the C.01.01 release of the E6562C.
 

E1987A

A.01.21 or later

E1963A

A.06.17 or later

E1985B

B.05.18 or later

 

Known Issues

 

Installation Issues
 

Uninstalling older software versions
 

If the non-NET versions of Wireless Test Manager are uninstalled after the NET version of Wireless Test Manager is installed, the non-NET Wireless Test Manager selection will remain in the Start Programs Menu. You can safely delete this menu item if you desire.
 

Uninstalling all software versions
 

To completely remove both non-NET versions of Wireless Test Manager and the NET version of Wireless Test Manager, first uninstall all versions of the NET version of Wireless Test Manager (See ReadMe.txt section 1.3) prior to uninstalling the non-NET Wireless Test Manager.
 

The USB security key is not recognized after installation
 

Situation: You try to run Wireless Test Manager(WTM), but WTM prompts you with the message "No security or incorrect security key found." even though the security key is inserted into a USB port; or when you insert the security key into a USB port, the Windows Found New Hardware Wizard appears and wants you to install a device driver for the security key.
 

Solution: This problem is usually caused when the key was in the USB port during the WTM installation. This interferes with the installation of the Rainbow Technologies Security Key files.  Perform the following steps to correct the problem:

a.       Cancel or exit from any prompts.

b.       Remove the USB security key from the USB port.

c.        Close all applications that are running.

d.       Check to see that the sx32w.dll and sp32w.dll is installed in the Windows System32 directory.  If the file is not present in the System32 directory, copy the sx32w.dll and the sp32w.dll from the Rainbow Technologies directory on the Wireless Test Manager installation CD to the Windows System32 directory on your PC.  

e.       Run the SSD5411-32bit.exe program in the Rainbow Technologies directory on the WTM installation CD to reinstall the drivers.

f.         Insert the Security Key into a USB port on your PC.   

g.       The Security Key should be recognized next time you run Wireless Test Manager.   

 

Back-up language files
 

Back-up files were created for the language files located in the directories below the ".../WirelessTestManager/Common/" level in case they are written over when installing an older version of the Wireless Test Manager. The release date of this version of the WTM is appended to the name of these language files.

 

??? <reference number> being displayed in the WTM UI
 

Situation1: If any E656xA application (VB6 WTM) is installed after an E656xC/N588xA application (.NET WTM) has been installed, the Agilent WTM framework language files (.lng) will be overwritten by the older language files. This will result in ‘??? <reference number>’ showing up on some WTM user interface objects. This is due to old language files not containing the new messages added in .NET WTM.
 

Situation2: If E6560C 1.0 application is installed after any newer E656xC/N588xA application has been installed.
 

Solution: Restore the backup language file for the appropriate UI (Exec & wizard) that was created when the E656xA or E6560C 1.0 application was installed.

 

Example: If the E6562A application is installed after the E6562C then a file called 'English10152004.lng' (where 10152004 is the file date of the E6562C installed language file) will need to be renamed or copied to replace the 'English.lng' in the default installation directory 'C:\Program Files\Agilent\WirelessTestManager\Common\ExecLocalization'. The 'English10152004.lng' file in the default installation directory 'C:\Program Files\Agilent\WirelessTestManager\Common\WizardLocalization' will also need to be renamed or copied to replace the 'English.lng' in that directory.

 

Other Issues


Issues known at shipment release
 

The localization utility tool (LocalizeUtility.exe) may not work if Visual Studio .Net is not installed.
 

Issues discovered after release

 

Situation: When setting the 8960 downlink and uplink channels in both the Call Parms/UARFCN Parms and Physical Channel Reconfig Setup, an error can be generated if a new UL Separation is used and the downlink channel is set before the uplink channel. This error prevents the downlink channel from being changed. The reason is that the uplink channel fields now default to Auto and the 8960 requires that the uplink channel be taken out of Auto before either the UL Separation field is changed or a downlink channel in a new band is set. If the WTM software just happens to set the uplink channel first then there is no error generated. What this means is that the first channel change in a test plan that changes to a new band will fail since the downlink channel is always changed first. There should be no channel change errors after this since the uplink channel has been taken out of Auto by this failed channel change.

 

Solution: QFE (Quick Fix Engineering) patchs are provided at the web site http://wireless.agilent.com/rfcomms/dloads/wtm/  that replace the Method Of Measurement assemblies: Agilent.WTM.wmmtMoM.dll for the E6562C, Agilent.WTMwmctaMoM.dll for the E6568C, and Agilent.WTM.wmltMoM.dll for the N5882A. These replacement assemblies have a fix that force the Uplink Channel fields in the 8960 to the field's background channel (out of Auto mode) the first time a test plan is run.
 

 

Situation: In the Phase Discontinuity test step, if the parameter "Uplink Closed Loop Power Control" is set to anything other than ‘Active Bits’ when the parameter "Power Control Pattern" is set to ‘Five Up Four Down’ or ‘Five Down Four Up’ the measurement results can be erroneous.

 

Solution: Make sure the parameter "Uplink Closed Loop Power Control" is set to ‘Active Bits’ (the default value) when the parameter "Power Control Pattern" is set to ‘Five Up Four Down’ or ‘Five Down Four Up’

 

 

Situation: The Phase Discontinuity measurement can time-out if the parameter "Power Control Pattern" is set to ‘Five Up Four Down’ or ‘Five Down Four Up’, the parameter "Number Of Pattern Repetitions" is set to a number greater than three and the parameter “Measurement Interval” is left at the default value of two. Even though the parameter “Measurement Interval” is not used for the measurement when the parameter "Power Control Pattern" is set to ‘Five Up Four Down’ or ‘Five Down Four Up’, it is still and incorrectly used to calculate the measurement timeout.

 

Solution: When setting the parameter "Power Control Pattern" to ‘Five Up Four Down’ or ‘Five Down Four Up’ then set the parameter “Measurement Interval” to a value equal to the “Number Of Pattern Repetitions” times ten (10). An example would be if the “Number Of Pattern Repetitions” is set to five then set the “Measurement Interval” to 50. If the “Number Of Pattern Repetitions” is set to nine or ten then set the “Measurement Interval” to 90.

 

 

Situation: When the ‘Select new WTM application’ button is pressed in any WTM application toolbar and the E6568C is selected from the list (assuming it is installed), it will not switch to the E6568C but instead do nothing but shut down the current application.  The reason is that the path entry to the executable in the registry under ‘HKEY_LOCAL_MACHINE/SOFTWARE/Agilent/Wireless/Wireless Test Manager Selectable Applications/E6568C/CurrentVersion/Path’ is incorrect.

 

Solution: Modify the value for the registry key: ‘HKEY_LOCAL_MACHINE/SOFTWARE/Agilent/Wireless/Wireless Test Manager Selectable Applications/E6568C/CurrentVersion/Path' so that the name of the executable is E6568C_WCDMA_GSM_GPRS_EGPRS_SAM_Net.exe instead of E6568C_WCDMA_GSM_GPRS_SAM_Net.exe.


 

To find the latest information about component and application release notes, visit the following Agilent Technologies web site http://www.agilent.com/find/wtmanagers and select the ‘E6562C WCDMA Wireless Test Manager’ product and then the ‘E6562C Release Notes’ link.            

 

Component Release Information

 

The following components will be installed with the Development installation of this release:

 

<Target Directory>\E6562C\RunTime

              E6562C_WCDMA_SAM_Net.exe

              Agilent.WTM.wmmtMoM.dll

 

Revision 1.1.0.0

Revision 1.1.0.0

 

 

<Target Directory>\Common

              Agilent.WTM.wmmtMoM.dll

              TestPlanMover.exe

              LocalizeUtility.exe

 

Revision 1.1.0.0

Revision 1.3.0.0

Revision 1.1.0.0

 

 

<Target Directory>\Common\NETWizards

              Agilent.WTM.AddInstrumentControl.dll

              Agilent.WTM.AddWirelessTest.dll

 

Revision 1.1.0.0

Revision 1.1.0.0

 

 

<Target Directory>\Common\NetWTMVersion1.X\Assemblies

              Agilent.WTM.Exec.dll

              Agilent.WTM.ag34970MoM.dll

              Agilent.WTM.gpioMoM.dll

              Agilent.WTM.psmtMoM.dll

              Agilent.WTM.MoMMUIServices.dll

              Agilent.WTM.MSJRO.Interop.dll

              Agilent.WTM.PathEffectServices.Interop.dll

              ScDerivedControls.dll

              ScUserControls.dll

 

Revision 1.4.0.0

Revision 1.1.0.0

Revision 1.1.0.0

Revision 1.2.0.0

Revision 1.0.0.0

Revision 2.6.0.0

Revision 1.0.0.0

Revision 1.0.1389.23550

Revision 1.0.1389.23557

 

 

<Target Directory>\WINNT\Assembly (Win2k)

<Target Directory>\WINDOWS\Assembly (XP)

              Agilent.WTM.ag34970MoM.dll

              Agilent.WTM.Exec.dll

              Agilent.WTM.gpioMoM.dll

              Agilent.WTM.psmtMoM.dll

              Agilent.WTM.MoMMUIServices.dll

              Agilent.WTM.MSJRO.Interop.dll

              Agilent.WTM.PathEffectServices.Interop.dll

              policy.1.0. Agilent.WTM.ag34970MoM

              policy.1.0. Agilent.WTM.ag34970MoM

              policy.1.0. Agilent.WTM.Exec

              policy.1.0. Agilent.WTM.Exec

              policy.1.1. Agilent.WTM.Exec

              policy.1.2. Agilent.WTM.Exec

              policy.1.3. Agilent.WTM.Exec

              policy.1.0. Agilent.WTM.gpioMoM

              policy.1.0. Agilent.WTM.gpioMoM

              policy.1.0. Agilent.WTM.MoMMUIServices

              policy.1.0. Agilent.WTM.PathEffectServices.Interop

              policy.1.0. Agilent.WTM.psmtMoM

              policy.1.0. Agilent.WTM.psmtMoM

              policy.1.1. Agilent.WTM.psmtMoM

              policy.2.6. Agilent.WTM.MSJRO.Interop

              ScDerivedControls.dll

              ScUserControls.dll

 

 

Revision 1.1.0.0

Revision 1.4.0.0

Revision 1.1.0.0

Revision 1.2.0.0

Revision 1.0.0.0

Revision 2.6.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.1.0.0

Revision 1.0.0.0

Revision 1.4.0.0

Revision 1.4.0.0

Revision 1.4.0.0

Revision 1.4.0.0

Revision 1.0.0.0

Revision 1.1.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.2.0.0

Revision 1.2.0.0

Revision 2.6.0.0

Revision 1.0.1389.23550

Revision 1.0.1389.23557

 

 

C:\Program Files\Common Files\Agilent Shared\Wireless

              PathEffectSvc.dll

 

Revision 1.1.0.0

 

 

C.01.00 Release – July 2004

 

C.01.00 Release – Overview

WCDMA Wireless Test Manager Modifications

Supported 8960 Test Applications

 

Known Issues

Installation Issues

Uninstalling older software versions

Uninstalling all software versions

The USB security key is not recognized after installation

Back-up language files

??? <reference number> being displayed in the WTM user interface

Other Issues

Issues known at shipment release

Issues discovered after release

Administrator Password Security Loophole

 

Component Release Information

 

 

C.01.00 Release – Overview

 

This software represents the initial release of the Agilent Technologies E6562C WCDMA Wireless Test Manager. It is a conversion of the E6562A software to Visual Basic .Net 2003 with user interface and functional enhancements. To see the latest release notes for the E6562A (includes revision information) go to the Agilent Technologies web site http://www.agilent.com/find/E6562A and select ‘E6562A Release Notes’.

 

W-CDMA Wireless Test Manager Modifications

1.       Several of the test step and parameter names have been modified to make them WCDMA specific to make it clear which mobile format they apply to.

 

2.       Several of the test steps that did not have any specifications now have a Passed/Failed string specification. This was necessary because of the way Maximum failed repeats now works in the executive.

 

3.       Several of the test plan steps have been modified to fix bugs or take advantage of new features in the E1963A and E1985B TA’s:

a.       WCDMA Change Channel Type will now change the channel type with the call connected or not.

b.       WCDMA Page and Origination can now be done with MS Loopback Type set to ‘Type 1’ or ‘Type 2’ and the Uplink DTCH RMC CRC Present set to ‘Present’ or ‘Used for Data’.

c.        WCDMA Page can be set to establish either an AMR Voice or RB Test Mode call.

d.       WCDMA Voice Quality  will now put the call back on an RB Test Mode call at the end of the test if the test was entered in that service type.

e.       WCDMA Open Loop Power has a new parameter ‘Cell Off Time Period While Switching Cell Power Levels’ and the test method has been modified to make it work more reliably.

f.         WCDMA Registration has a new parameter that allows the user to set the time to wait for a registration to occur.

 

4.       The following test steps have been added:

a.       WCDMA Initiate Loopback BLER

b.       WCDMA Fetch Loopback BLER

c.        WCDMA Measure Loopback BLER

d.       WCDMA Phase Discontinuity

e.       WCDMA Change Service Type

f.         WCDMA Concurrent RX TX

 

5.       The following global parameters have been added:

a.       Restore Amplitude Offsets

b.       WCDMA Security Operations

c.        WCDMA Authentication Algorithm

d.       WCDMA Authentication Key, Upper

e.       WCDMA Authentication Key, Upper Middle

f.         WCDMA Authentication Key, Lower Middle

g.       WCDMA Authentication Key, Lower

h.       WCDMA RLC Reestablish

i.         WCDMA IMSI Attach Flag

j.         WCDMA BCCH Update Page

k.        WCDMA Maximum Uplink Transmit Power

l.         WCDMA Repeat Paging

m.     Use IMEI in Results File Name

 

Supported 8960 Test Applications

 

The following TA’s are supported by the C.01.00 release of the E6562C.

             

E1985B

B.04.35 or later

 

E1963A

A.05.33 or later

 

 

Known Issues

 

Installation Issues

 

Uninstalling older software versions

 

If the non-NET versions of Wireless Test Manager are uninstalled after the NET version of Wireless Test Manager is installed, the non-NET Wireless Test Manager selection will remain in the Start Programs Menu. You can safely delete this menu item if you desire.

 

 

Uninstalling all software versions

 

To completely remove both non-NET versions of Wireless Test Manager and the NET version of Wireless Test Manager, first uninstall all versions of the NET version of Wireless Test Manager (See ReadMe.txt section 1.3) prior to uninstalling the non-NET Wireless Test Manager.

 

 

The USB security key is not recognized after installation

 

Situation: You try to run Wireless Test Manager(WTM), but WTM prompts you with the message "No security or incorrect security key found." even though the security key is inserted into a USB port; or when you insert the security key into a USB port, the Windows Found New Hardware Wizard appears and wants you to install a device driver for the security key.

 

Solution: This problem is usually caused when the key was in the USB port during the WTM installation. This interferes with the installation of the Rainbow Technologies Security Key files.  Perform the following steps to correct the problem: 

a.       Cancel or exit from any prompts.

b.       Remove the USB security key from the USB port.

c.        Close all applications that are running.

d.       Check to see that the sx32w.dll and sp32w.dll is installed in the Windows System32 directory.  If the file is not present in the System32 directory, copy the sx32w.dll and the sp32w.dll from the Rainbow Technologies directory on the Wireless Test Manager installation CD to the Windows System32 directory on your PC.  

e.       Run the SSD5411-32bit.exe program in the Rainbow Technologies directory on the WTM installation CD to reinstall the drivers.

f.         Insert the Security Key into a USB port on your PC.

g.       The Security Key should be recognized next time you run Wireless Test Manager.   

 

Back-up language files

 

Back-up files were created for the language files located in the directories below the ".../WirelessTestManager/Common/" level in case they are written over when installing an older version of the Wireless Test Manager. The release date of this version of the WTM is appended to the name of these language files.

 

??? <reference number> being displayed in the WTM user interface

  

Situation1: If any E656xA application (VB6 WTM) is installed after an E656xC application (.NET WTM) has been installed, the Agilent WTM framework language files (.lng) will be overwritten by the older language files. This will result in ‘??? <reference number>’ showing up on some WTM user interface objects. This is due to old language files not containing the new messages added in .NET WTM.

 

Situation2: If E6560C 1.0 application is installed after any newer E656xC application has been installed.

 

Solution: Restore the backup language file that was created when the E656xA or E6560C 1.0 application was installed.

 

Example: If the E6562A application is installed after the E6562C then a file called 'English09152004.lng' will be created in the default installation directory 'C:\Program Files\Agilent\WirelessTestManager\Common\ExecLocalization'. Delete (or rename) the 'English.lng' file in this directory and rename the 'English09152004.lng' file to 'English.lng'.

 

 

Other Issues

 

Issues known at shipment release

 

No known issues.

 

Issues discovered after release

 

To find the latest information about component and application release notes, visit the following Agilent Technologies web site http://www.agilent.com/find/wtmanagers and select the ‘E6562C WCDMA Wireless Test Manager’ product. Then select desired release note link.

 

1.   Situation: If a region or language setting that uses a space as the Digit Grouping Symbol (e.g. French) is used, then an exception will be generated when WTM attempts to read the test set TA revision number.
Solution: Go to the Wireless Test Manager Software Downloads site http://wireless.agilent.com/rfcomms/dloads/wtm/ and download the file E6562C_QFE2.exe. Open the E6562C_QFE2_ Readme.txt file and follow the installation instructions provided.

 

2.   Situation: If using a National Instruments GPIB card with NI 488.2 driver version 1.7, then an exception may be generated when WTM attempts to use the VISA viRead() function and convert the returned data into a Double or Integer data type.
Solution: Go to the Wireless Test Manager Software Downloads site http://wireless.agilent.com/rfcomms/dloads/wtm/ and download the file E6562C_QFE2.exe. Open the E6562C_QFE2_ Readme.txt file and follow the installation instructions provided.

 

3.   Situation: The TA Model and TA Revision are displayed incorrectly as TA Model=TA Model and TA Revision=TA Revision in the header of the Previous test results files in addition to the xml and “normal” csv formatted data collection files.

 

Solution: Modify the following two lines of code in FlowControl.vb/Sub StartOfTestPlan from

 

DataLogging.AddTestConditionInformation("TA Model", wcdma.InstrumentIdentity.CurrentTAModel, WCDMALOCALIZE + 10600)

DataLogging.AddTestConditionInformation("TA Revision", wcdma.InstrumentIdentity.CurrentTARevision, WCDMALOCALIZE + 10602)

 

to:

 

DataLogging.AddTestConditionInformation("TA Model", wcdma.InstrumentIdentity.CurrentTAModel, "TA Model", WCDMALOCALIZE + 10600)

DataLogging.AddTestConditionInformation("TA Revision", wcdma.InstrumentIdentity.CurrentTARevision, "TA Revision", WCDMALOCALIZE + 10602)

 

or simply remove the localization parameter (, WCDMALOCALIZE + 10600) if localization is not needed:

 

DataLogging.AddTestConditionInformation("TA Model", wcdma.InstrumentIdentity.CurrentTAModel)

DataLogging.AddTestConditionInformation("TA Revision", wcdma.InstrumentIdentity.CurrentTARevision)

 

 

Administrator Password Security Loophole

 

Under certain circumstances, it is possible for a user in Operator (Locked) mode to wander back into the Administrator (Unlocked) mode. This only happens when someone has correctly entered the Administrator password, entered Administrator mode during a “session”, AND did not shut WTM down as part of leaving Administrator mode.

 

The work-around for this issue is to ALWAYS close down WTM after being in Administrator mode in one of the following two ways:

1.    Close down WTM while you’re still in Administrator mode (after you’ve made changes/viewed settings or whatever you wanted to accomplish)

2.    Close down WTM just after you’ve left the Administrator mode and returned to Operator mode by pressing the ‘Lock’ button.

 

This loophole will be fixed in an upcoming WTM Exec release.

  

Component Release Information

 

The following components will be installed with the Development installation of this release:

 

<Target Directory>\E6562C\RunTime

              E6562C_WCDMA_SAM_Net.exe

              Agilent.WTM.wmmtMoM.dll

 

Revision 1.0.0.0

Revision 1.0.0.0

 

 

<Target Directory>\Common

              Agilent.WTM.wmmtMoM.dll

              TestPlanMover.exe

              LocalizeUtility.exe

 

Revision 1.0.0.0

Revision 1.1.0.0

Revision 1.1.0.0

 

 

<Target Directory>\Common\NETWizards

              Agilent.WTM.AddInstrumentControl.dll

              Agilent.WTM.AddWirelessTest.dll

 

Revision 1.0.0.0

Revision 1.0.0.0

 

 

<Target Directory>\Common\NetWTMVersion1.X\Assemblies

              Agilent.WTM.Exec.dll

              Agilent.WTM.ag34970MoM.dll

              Agilent.WTM.gpioMoM.dll

              Agilent.WTM.psmtMoM.dll

              Agilent.WTM.MoMMUIServices.dll

              Agilent.WTM.MSJRO.Interop.dll

              Agilent.WTM.PathEffectServices.Interop.dll

              ScDerivedControls.dll

              ScUserControls.dll

 

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 2.6.0.0

Revision 1.0.0.0

Revision 1.0.1389.23550

Revision 1.0.1389.23557

 

 

<Target Directory>\WINNT\Assembly (Win2k)

<Target Directory>\WINDOWS\Assembly (XP)

              Agilent.WTM.ag34970MoM.dll

              Agilent.WTM.Exec.dll

              Agilent.WTM.gpioMoM.dll

              Agilent.WTM.psmtMoM.dll

              Agilent.WTM.MoMMUIServices.dll

              Agilent.WTM.MSJRO.Interop.dll

              Agilent.WTM.PathEffectServices.Interop.dll

              policy.1.0. Agilent.WTM.ag34970MoM

              policy.1.0. Agilent.WTM.Exec

              policy.1.0. Agilent.WTM.gpioMoM

              policy.1.0. Agilent.WTM.MoMMUIServices

              policy.1.0. Agilent.WTM.PathEffectServices.Interop

              policy.1.0. Agilent.WTM.psmtMoM

              policy.2.6. Agilent.WTM.MSJRO.Interop

              ScDerivedControls.dll

              ScUserControls.dll

 

 

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 2.6.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 2.6.0.0

Revision 1.0.1389.23550

Revision 1.0.1389.23557

 

 

C:\Program Files\Common Files\Agilent Shared\Wireless

              PathEffectSvc.dll

 

Revision 1.1.0.0

 

 

Contact Information

 

Service and Support

 

To find information about technical support, equipment service and repair, and training, visit the following Agilent Technologies web site:

 

For product information:                 http://www.agilent.com/find/wtmanagers

 

For Agilent contact information:      http://www.agilent.com/find/contactus