E6568C Web Release Notes - United States Home | Keysight …€¦ · Web view · 2009-07-27WCDMA...

E6568C WCDMA/GSM/GPRS/EGPRS Wireless Test Manager Revision Information Last updated: Jun/2009(C) Copyright 2005-2009 Agilent TechnologiesAll Rights Reserved This document describes the features that are in the Agilent Technologies E6568C WCDMA/GSM/GPRS/EGPRS 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/E6568C and click on the Frequently-Asked-Questions (FAQs) link below the Key Library Information table. Select the appropriate link below to view the required release.C.02.03 Release - Jun 2009

C.02.02 Release - Feb 2009 C.02.01 Release - Dec 2007 C.02.00 Release - Nov 2006 C.01.00 Release - May 2005 (initial release) Contact Information

Service and Support

C.02.03 Release - Jun 2009

C.02.0 3 Release - Overview WCDMA/GSM/GPRS/EGRPS Wireless Test Manager ModificationsSupported 8960 Test Applications

Known Issues

Installation IssuesUninstalling older software versionsUninstalling all software versionsThe USB security key is not recognized after installationBack-up language files??? <reference number> being displayed in the WTM UIInstalling older software versions

Other IssuesIssues known at shipment releaseIssues discovered after release

Component Release Information

C.02.03 Release - Overview This software release provides GPRS EGPRS class 12, AMR and WB-AMR supporting and some new global parameters. This release also fixed some defects existing in theprevious release.

http://www.agilent.com/find/E6568C

WCDMA/GSM/GPRS/EGPRS Wireless Test Manager Modifications

1. The following GSM GPRS EGPRS global parameters have been added:a. GPRS EGPRS Uplink Data Timeoutb. WCDMA Frequency Band Indicatorc. Prefix of Results File Name.

2. Added the new parameter of “Phase Error Filter Type” which affects the following test steps:a. EGPRS Modulation Accuracyb. EGPRS Fast General Test

3. Added the new parameter of “Burst Capture Range” which affects the following test steps:a. GSM GPRS EGPRS Power vs Timeb. EGPRS Fast General Testc. GPRS Fast General Test

4. Added new parameters listed below each of the following test step:a. GSM Voice Quality

1) Logical Speech Channel2) AFS Codec Setup3) AHS Codec Setup4) WFS Codec Setup

b. WCDMA Voice Quality1) AMR Radio Access Bearer2) WDMA Speech Echo Loopback Delay (mSec)

5. Measurement Burst is enhanced to support the selection of Three, Four, AllBursts. This affects the following test steps:a. GSM GPRS EGPRS Output RF Spectrumb. GSM GPRS EGPRS Phase and Frequency Errorc. EGPRS Modulation Accuracyd. EGPRS Fast General Teste. GPRS Fast General Test

6. The following specification names are modified:a. “PvT EPSK Mask Guard Period when First Burst is Higher(dbC Rel to Burst 1)” to “PvT

EPSK Mask Guard Period when Burst n is Higher(dbC Rel to Burst n)” b. “PvT EPSK Mask Guard Period when First Burst is Lower(dbC Rel to Burst 2)” to “PvT

EPSK Mask Guard Period when Burst n is Lower(dbC Rel to Burst n+1)” c. “PvT GMSK Mask Guard Period when First Burst is Higher(dbC Rel to Burst 1)” to “PvT

GMSK Mask Guard Period when Burst n is Higher(dbC Rel to Burst n)” d. “PvT GMSK Mask Guard Period when First Burst is Lower(dbC Rel to Burst 2)” to “PvT

GMSK Mask Guard Period when Burst n is Lower(dbC Rel to Burst n+1)”These changes affect the following test steps:a. GSM GPRS EGPRS Power vs Timeb. EGPRS Fast General Testc. GPRS Fast General Test

7. Resolved the defect of Visa32.dll is overwritten.Supported 8960 Test Applications The following TA’s are supported by the C.02.00 release of the E6568C.

E1987A A.08.14 or later E1968A A.09.13 or later E1963A A.13.13 or later

Known Issues

Installation Issues

Uninstalling older software versionsIf 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 versionsTo 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 installationSituation: 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:

1. Cancel or exit from any prompts.2. Remove the USB security key from the USB port.3. Close all applications that are running.4. 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.

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

6. Insert the Security Key into a USB port on your PC. 7. The Security Key should be recognized next time you run Wireless Test Manager.

Back-up language filesBack-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 UISituation1: 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 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 E6560C then a file called ' Englishxxxxxxxx.lng ' (where xxxxxxxx is the file date of the E6560C 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 'Englishxxxxxxxx.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 .

Installing older software versionsSituation: Installing the E6564C 1.0 after installing the E6568C will corrupt the WTM E6568C registry entry. The entry for the Agilent Wireless Test Manager (E6568C) in the Windows Add/Remove Programs window will also be removed. Solution: reinstall the E6568C application.

Other Issues

Issues known at shipment releaseCompatibility issue - When testing with Wireless Test Manager E6568C C.02.02 or C.02.03,

the test plan will be aborted if the Agilent 8960 test set doesn’t have any HSUPA license. The reason is: the Wireless Test Manager sends out a HSUPA dedicated GPIB command to the 8960 before any test plan is carried out. If the 8960 has no HSUPA license, a timeout error happens and the test plan is aborted.

Solution: install the required HSUPA license on the Agilent 8960 test set.

Issues discovered after releaseTo 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 ‘E6568C WCDMA/GSM/GPRS/EGPRS Wireless Test Manager’ product. Then select desired release note link.

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

<Target Directory>\E6568C\RunTime E6568C_WCDMA_GSM_GPRS_EGPRS_SAM_Net.exe Revision 2.3.0.0 Agilent.WTM.dmctaMoM.dll Revision 2.3.0.0 Agilent.WTM.wmctaMoM.dll Revision 2.3.0.0 <Target Directory>\Common Agilent.WTM.dmctaMoM.dll Revision 2.3.0.0 Agilent.WTM.wmctaMoM.dll Revision 2.3.0.0 TestPlanMover.exe Revision 1.5.0.0 LocalizeUtility.exe Revision 1.1.0.0 WTMDataAnalyzer.exe Revision 1.5.0.0 <Target Directory>\Common\NETWizards Agilent.WTM.AddInstrumentControl.dll Revision 1.2.0.0 Agilent.WTM.AddWirelessTest.dll Revision 1.2.0.0 Agilent.WTM.AddInstrumentControl05.dll Revision 1.0.0.0 Agilent.WTM.AddWirelessTest05.dll Revision 1.0.0.0 <Target Directory>\Common\NetWTMVersion1.X\Assemblies Agilent.WTM.Exec.dll Revision 1.9.1.0 Agilent.WTM.ag34970MoM.dll Revision 1.1.0.0 Agilent.WTM.gpioMoM.dll Revision 1.1.0.0 Agilent.WTM.psmtMoM.dll Revision 1.3.0.0 Agilent.WTM.MoMMUIServices.dll Revision 1.0.0.0 Agilent.WTM.MSJRO.Interop.dll Revision 2.6.0.0 Agilent.WTM.PathEffectServices.Interop.dll Revision 1.0.0.0 ScDerivedControls.dll Revision 1.0.1389.23550 ScUserControls.dll Revision 1.0.1389.23557 Agilent.WTM.ag14656BMoM.dll Revision 1.1.0.0 ag14565BSignedInterop.dll Revision 1.1.0.0

http://www.agilent.com/find/wtmanagers

\WINNT\Assembly (Win2k) \WINDOWS\Assembly (XP) Agilent.WTM.Exec.dll Revision 1.9.1.0 Agilent.WTM.ag34970MoM.dll Revision 1.1.0.0 Agilent.WTM.gpioMoM.dll Revision 1.1.0.0 Agilent.WTM.psmtMoM.dll Revision 1.3.0.0 Agilent.WTM.MoMMUIServices.dll Revision 1.0.0.0 Agilent.WTM.MSJRO.Interop.dll Revision 2.6.0.0 Agilent.WTM.PathEffectServices.Interop.dll Revision 1.0.0.0 policy.1.0. Agilent.WTM.ag34970MoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.ag34970MoM Revision 1.1.0.0 policy.1.0. Agilent.WTM.Exec Revision 1.0.0.0 policy.1.0. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.1. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.2. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.3. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.4. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.5. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.6. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.7. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.8. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.9. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.0. Agilent.WTM.gpioMoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.gpioMoM Revision 1.1.0.0 policy.1.0. Agilent.WTM.MoMMUIServices Revision 1.0.0.0 policy.1.0. Agilent.WTM.PathEffectServices.Interop Revision 1.0.0.0 policy.1.0. Agilent.WTM.psmtMoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.1.1. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.1.2. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.2.6. Agilent.WTM.MSJRO.Interop Revision 2.6.0.0 ScDerivedControls.dll Revision 1.0.1389.23550 ScUserControls.dll Revision 1.0.1389.23557 Agilent.WTM.ag14656BMoM.dll Revision 1.1.0.0 ag14565BSignedInterop.dll Revision 1.1.0.0 C:\Program Files\Common Files\Agilent Shared\Wireless PathEffectSvc.dll Revision 1.1.0.0

C.02.02 Release – Feb 2009

C.02.02 Release – OverviewWCDMA/GSM/GPRS/EGRPS 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 interfaceInstalling older software versionsVisa32.dll is overwritten

Other IssuesIssues known at shipment release Issues discovered after release


C.02.02 Release – Overview This software release adds support for HSUPA 10ms and 2ms, adds WCDMA and GGE SMS supports, add two HSDPA new measurements, Band VII IX and X supports and fixes some defects.


1. New HSUPA Test Steps added a. WCDMA Maximum Output Power with HSUPAb. WCDMA Adjacent Channel Leakage with HSUPAc. WCDMA Spectrum Emission Mask with HSUPAd. WCDMA RCDE with HSUPAe. WCDMA RCDPA with HSUPA

2. Test Steps modified for HSUPA supportsa. WCDMA Transport Channel Reconfigurationb. Start Loop

3. New HSUDPA Test steps are addeda. WCDMA RCDE with HSDPAb. WCDMA EVM and Phase Discontinuity with HSDPA

4. New WCDMA Test steps are addeda. WCDMA Receiver Sensitivity Level Searchb. WCDMA SMS Mobile Originatedc. WCDMA SMS Mobile Terminated

5. Test Steps modified for WCDMA: adds IQ gain imbalance, IQ phase imbalance and Peak EVM measurement

a. WCDMA Waveform Quality6. One Generic test step is added

a. Wait7. New GGE Test Steps are added

a. GSM GPRS EGPRS SMS Mobile Originatedb. GSM GPRS EGPRS SMS Mobile Terminated

8. Defects or Enhancementsa. The USB security key is slower than Parallel Keyb. Define “Enter Key” as the shortcut key for running WTM c. Global parameter “WCDMA Internal TCR Timing Indication” is open to customer to

choose the timing indication during internal handover.

Supported 8960 Test Applications The following TA’s are supported by the C.02.00 release of the E6568C.


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.


1. Cancel or exit from any prompts.2. Remove the USB security key from the USB port.3. Close all applications that are running.4. 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.


6. Insert the Security Key into a USB port on your PC. 7. 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 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 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 E6560C then a file called ' Englishxxxxxxxx.lng ' (where xxxxxxxx is the file date of the E6560C 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 'Englishxxxxxxxx.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 .

Installing older software versions Situation: Installing the E6564C 1.0 after installing the E6568C will corrupt the WTM E6568C registry entry. The entry for the Agilent Wireless Test Manager (E6568C) in the Windows Add/Remove Programs window will also be removed. Solution: reinstall the E6568C application.

Visa32.dll is overwrittenWhen this installation package is run, it overwrites the visa32.dll file in the system32 directory with the Agilent version of this file. This issue has impacts to both Agilent

GPIB driver users and NI GPIB driver users: 1. For Agilent GPIB driver users, the Agilent visa32.dll may be changed to a different revision. Some software dependent on the previous visa32.dll could be impacted. 2. For NI GPIB driver users, the NI visa32.dll is replaced with the Agilent version of this file, and causes WTM communicating with 8960 fail or wrongly. Other NI visa32.dll dependent software may also be impacted. The issue can be solved by reinstalling the previous GPIB driver or Agilent GPIB driver.

Other Issues

Issues known at shipment release Compatibility issue - When testing with Wireless Test Manager E6568C C.02.02 or C.02.03,

the test plan will be aborted if the Agilent 8960 test set doesn’t have any HSUPA license. The reason is: the Wireless Test Manager sends out a HSUPA dedicated GPIB command to the 8960 before any test plan is carried out. If the 8960 has no HSUPA license, a timeout error happens and the test plan is aborted.

Solution: install the required HSUPA license on the Agilent 8960 test set.

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 ‘E6568C WCDMA/GSM/GPRS/EGPRS Wireless Test Manager’ product. Then select desired release note link.


<Target Directory>\E6568C\RunTime E6568C_WCDMA_GSM_GPRS_EGPRS_SAM_Net.exe Revision 2.2.0.0 Agilent.WTM.dmctaMoM.dll Revision 2.2.0.0 Agilent.WTM.wmctaMoM.dll Revision 2.2.0.0 <Target Directory>\Common Agilent.WTM.dmctaMoM.dll Revision 2.2.0.0 Agilent.WTM.wmctaMoM.dll Revision 2.2.0.0 TestPlanMover.exe Revision 1.5.0.0 LocalizeUtility.exe Revision 1.1.0.0 WTMDataAnalyzer.exe Revision 1.5.0.0 <Target Directory>\Common\NETWizards Agilent.WTM.AddInstrumentControl.dll Revision 1.2.0.0 Agilent.WTM.AddWirelessTest.dll Revision 1.2.0.0 Agilent.WTM.AddInstrumentControl05.dll Revision 1.0.0.0 Agilent.WTM.AddWirelessTest05.dll Revision 1.0.0.0 <Target Directory>\Common\NetWTMVersion1.X\Assemblies Agilent.WTM.Exec.dll Revision 1.9.1.0 Agilent.WTM.ag34970MoM.dll Revision 1.1.0.0 Agilent.WTM.gpioMoM.dll Revision 1.1.0.0 Agilent.WTM.psmtMoM.dll Revision 1.3.0.0 Agilent.WTM.MoMMUIServices.dll Revision 1.0.0.0 Agilent.WTM.MSJRO.Interop.dll Revision 2.6.0.0 Agilent.WTM.PathEffectServices.Interop.dll Revision 1.0.0.0 ScDerivedControls.dll Revision 1.0.1389.23550 ScUserControls.dll Revision 1.0.1389.23557


Agilent.WTM.ag14656BMoM.dll Revision 1.1.0.0 ag14565BSignedInterop.dll Revision 1.1.0.0 \WINNT\Assembly (Win2k) \WINDOWS\Assembly (XP) Agilent.WTM.Exec.dll Revision 1.9.1.0 Agilent.WTM.ag34970MoM.dll Revision 1.1.0.0 Agilent.WTM.gpioMoM.dll Revision 1.1.0.0 Agilent.WTM.psmtMoM.dll Revision 1.3.0.0 Agilent.WTM.MoMMUIServices.dll Revision 1.0.0.0 Agilent.WTM.MSJRO.Interop.dll Revision 2.6.0.0 Agilent.WTM.PathEffectServices.Interop.dll Revision 1.0.0.0 policy.1.0. Agilent.WTM.ag34970MoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.ag34970MoM Revision 1.1.0.0 policy.1.0. Agilent.WTM.Exec Revision 1.0.0.0 policy.1.0. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.1. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.2. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.3. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.4. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.5. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.6. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.7. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.8. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.9. Agilent.WTM.Exec Revision 1.9.1.0 policy.1.0. Agilent.WTM.gpioMoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.gpioMoM Revision 1.1.0.0 policy.1.0. Agilent.WTM.MoMMUIServices Revision 1.0.0.0 policy.1.0. Agilent.WTM.PathEffectServices.Interop Revision 1.0.0.0 policy.1.0. Agilent.WTM.psmtMoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.1.1. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.1.2. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.2.6. Agilent.WTM.MSJRO.Interop Revision 2.6.0.0 ScDerivedControls.dll Revision 1.0.1389.23550 ScUserControls.dll Revision 1.0.1389.23557 Agilent.WTM.ag14656BMoM.dll Revision 1.1.0.0 ag14565BSignedInterop.dll Revision 1.1.0.0 C:\Program Files\Common Files\Agilent Shared\Wireless PathEffectSvc.dll Revision 1.1.0.0

C.02.01 Release – Dec 2007


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 interfaceInstalling older software versions



C.02.01 Release – Overview This software release provides modifications to test plan steps, new test steps and additional enhancements including new global parameters.

WCDMA/GSM/GPRS/EGPRS Wireless Test Manager

1. The following GSM GPRS EGPRS global parameters have been added:a. Down 1 Up 3, Down 1 Up 4 and Down 2 Up 3 are selectable in GPRS EGPRS Initial

Multislot Configuration setting.

2. The following features have been added to several test steps to reflect new features in E1968A or E1987A TAs:

a. Down 1 Up 3, Down 1 Up 4 and Down 2 Up 3 are selectable. This affects the following test steps:

1. GPRS Handover2. EGPRS Handover3. GRPS Start Data Connection 4. EGRPS Start Data Connection

b. MS TX Level Burst 3 and MS TX Level Burst 4 are selectable. This affects the following test steps:

1. Start Loop2. GRPS Start Data Connection 3. EGRPS Start Data Connection 4. GPRS EGPRS Change Channel5. GPRS Handover6. EGPRS Handover

c. Manual Modulation Format of Burst 3 and Manual Modulation Format of Burst 4 are selectable in the following test steps:

1. EGPRS Start Data Connectiond. Three, Four and AllBursts of Measurement Burst are selectable. This affects the

following test steps:1. GSM GPRS EGPRS TX Power2. GPRS Fast General Test3. EGPRS Fast General Test4. GSM GPRS EGPRS Output RF Spectrum5. GSM GPRS EGPRS Phase and Frequency Error6. EGPRS Modulation Accuracy

Note: Three, Four and AllBursts are only available for TX Power measurement. If you select them in other tests, you will get an error.

e. Add new test steps named Remark.f. Add 14565B Power Supply test steps to support Agilent 14565B Device

Characterization Software.3. The upper limit of the following parameters is changed to 10838 from 10875

a. WCDMA Initial Downlink Channel With No Looping in global parametersb. Downlink Channel in WCDMAChangeChannelc. Registration DL Channel in WCDMARegistrationd. Downlink in the Channel Pair table of Start Loop

4. A new parameter “WCDMA Page Timeout (Seconds)” is added in the “WCDMA Page” Step



Known Issues Installation Issues


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.



1. Cancel or exit from any prompts.2. Remove the USB security key from the USB port.3. Close all applications that are running.4. 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.


6. Insert the Security Key into a USB port on your PC. 7. The Security Key should be recognized next time you run Wireless Test

Manager.


??? <reference number> being displayed in the WTM UI 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 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 E6560C then a file called ' Englishxxxxxxxx.lng ' (where xxxxxxxx is the file date of the E6560C 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 'Englishxxxxxxxx.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 No known issues.



<Target Directory>\E6568C\RunTime E6568C_WCDMA_GSM_GPRS_EGPRS_SAM_Net.exe Revision 2.1.0.0 Agilent.WTM.dmctaMoM.dll Revision 2.1.0.0 Agilent.WTM.wmctaMoM.dll Revision 2.0.0.0 <Target Directory>\Common Agilent.WTM.dmctaMoM.dll Revision 2.1.0.0 Agilent.WTM.wmctaMoM.dll Revision 2.0.0.0 TestPlanMover.exe Revision 1.5.0.0 LocalizeUtility.exe Revision 1.1.0.0 WTMDataAnalyzer.exe Revision 1.4.0.0 <Target Directory>\Common\NETWizards Agilent.WTM.AddInstrumentControl.dll Revision 1.2.0.0 Agilent.WTM.AddWirelessTest.dll Revision 1.2.0.0 Agilent.WTM.AddInstrumentControl05.dll Revision 1.0.0.0 Agilent.WTM.AddWirelessTest05.dll Revision 1.0.0.0 <Target Directory>\Common\NetWTMVersion1.X\Assemblies Agilent.WTM.Exec.dll Revision 1.9.0.0 Agilent.WTM.ag34970MoM.dll Revision 1.1.0.0 Agilent.WTM.gpioMoM.dll Revision 1.1.0.0 Agilent.WTM.psmtMoM.dll Revision 1.3.0.0 Agilent.WTM.MoMMUIServices.dll Revision 1.0.0.0 Agilent.WTM.MSJRO.Interop.dll Revision 2.6.0.0 Agilent.WTM.PathEffectServices.Interop.dll Revision 1.0.0.0 ScDerivedControls.dll Revision 1.0.1389.23550 ScUserControls.dll Revision 1.0.1389.23557 Agilent.WTM.ag14656BMoM.dll Revision 1.1.0.0 ag14565BSignedInterop.dll Revision 1.1.0.0 \WINNT\Assembly (Win2k) \WINDOWS\Assembly (XP)


Agilent.WTM.Exec.dll Revision 1.9.0.0 Agilent.WTM.ag34970MoM.dll Revision 1.1.0.0 Agilent.WTM.gpioMoM.dll Revision 1.1.0.0 Agilent.WTM.psmtMoM.dll Revision 1.3.0.0 Agilent.WTM.MoMMUIServices.dll Revision 1.0.0.0 Agilent.WTM.MSJRO.Interop.dll Revision 2.6.0.0 Agilent.WTM.PathEffectServices.Interop.dll Revision 1.0.0.0 policy.1.0. Agilent.WTM.ag34970MoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.ag34970MoM Revision 1.1.0.0 policy.1.0. Agilent.WTM.Exec Revision 1.0.0.0 policy.1.0. Agilent.WTM.Exec Revision 1.9.0.0 policy.1.1. Agilent.WTM.Exec Revision 1.9.0.0 policy.1.2. Agilent.WTM.Exec Revision 1.9.0.0 policy.1.3. Agilent.WTM.Exec Revision 1.9.0.0 policy.1.4. Agilent.WTM.Exec Revision 1.9.0.0 policy.1.5. Agilent.WTM.Exec Revision 1.9.0.0 policy.1.6. Agilent.WTM.Exec Revision 1.9.0.0 policy.1.7. Agilent.WTM.Exec Revision 1.9.0.0 policy.1.8. Agilent.WTM.Exec Revision 1.9.0.0 policy.1.0. Agilent.WTM.gpioMoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.gpioMoM Revision 1.1.0.0 policy.1.0. Agilent.WTM.MoMMUIServices Revision 1.0.0.0 policy.1.0. Agilent.WTM.PathEffectServices.Interop Revision 1.0.0.0 policy.1.0. Agilent.WTM.psmtMoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.1.1. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.1.2. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.2.6. Agilent.WTM.MSJRO.Interop Revision 2.6.0.0 ScDerivedControls.dll Revision 1.0.1389.23550 ScUserControls.dll Revision 1.0.1389.23557 Agilent.WTM.ag14656BMoM.dll Revision 1.1.0.0 ag14565BSignedInterop.dll Revision 1.1.0.0 C:\Program Files\Common Files\Agilent Shared\Wireless PathEffectSvc.dll Revision 1.1.0.0

C.02.00 Release – Nov 2006


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 interfaceInstalling older software versions



C.02.00 Release – Overview This software release provides modifications to test plan steps, new test steps and additional enhancements including new global parameters and Microsoft® Visual Studio® 2005 Professional and Standard Edition compatibility changes.

WCDMA/GSM/GPRS/EGPRS Wireless Test Manager

Changes to allow the project to be loaded into and converted by Microsoft® Visual Studio® 2005 Professional and Standard Edition. If a backup is created when converting to Microsoft® Visual Studio® 2005, the Backup directory will need to be moved to the same level as the Development directory prior to running the old Microsoft® Visual Studio®.NET 2003 project. During the conversion, if the Security Warning message box is displayed, select ‘Load project normally’ and press the OK button. 1. The following GSM GPRS EGPRS global parameters have been added:

a. GSM GPRS EGPRS IMSI Attach State – Determines whether the Attach routine should be performed after the phone is powered on.

b. Cell Parameter 3 Digit PCS Mobile Network Code – Defines the 3-digit mobile network code (MNC). This global parameter is used on the PCS BCCH instead of the 2-digit MNC only when the current cell band is PCS and the "Cell Parameter Use 3 Digit MNC for PCS" global parameter is set to On.

2. The following features have been added to several test steps to reflect new features in E1968A or E1987A TAs:

a. The Speech Loopback Delay in the GSM Voice Quality test is settable between 0 and 1 second.

b. The method of demodulation for the Phase and Frequency Error tail bit is selectable. This affects the following test steps:

1. GSM GPRS EGPRS Phase and Frequency Error2. GSM Fast General Test3. GPRS Fast General Test4. EGPRS Fast General Test

c. The ORFS test can use either a digital or analog measurement filter. The digital filter provides faster measurement speed with reduced accuracy in some conditions. The affects the following test steps:

1. GSM GPRS EGPRS Output RF Spectrum 2. GSM Fast General Test3. GPRS Fast General Test4. EGPRS Fast General Test

d. The GSM Transmitter Power measurements permit the specification for maximum power level to change based on the power class of the mobile. This affects the following test steps:

1. GSM GPRS EGPRS TX Power2. GSM GPRS EGPRS PowervsTime3. GSM GPRS EGPRS Output RF Spectrum4. GSM Fast General Test5. GPRS Fast General Test6. EGPRS Fast General Test

e. The TX Power test step will automatically range if the power level specification limits are greater than the range of the Test Sets expected input level.

f. The method of determining how bad blocks are handled is selectable for the GPRS BLER and BER test steps. The affects the following test steps:

1. GPRS EGPRS Measure Block Error 2. GPRS EGPRS Initiate Block Error3. GPRS Measure Bit Error4. GPRS Initiate Bit Error5. GPRS Fast General Test6. EGPRS Fast General Test

g. The T-GSM810 frequency band is supported. This affects all test steps that have frequency band parameters.

3. The following parameters have been added or modified to reflecting new features in the E1968A or E1987A TAs:

a. Speech Echo Loopback Delay – Sets the Speech Loopback Delay between 0 and 1 in the GSM Voice Quality test step.

b. Filter Type – Selects the demodulation filter type for the Output RF Spectrum measurement.

c. Tail Bit Demodulation Type – Sets method of tail bit demodulation for the Phase and Frequency Error measurements.

d. Read Power Class to determine Max TX Level – Directs the software to read the power class from the mobile to determine which specifications are used for the maximum power level in the TX power measurements.

e. Get Alternate GSM Power Class from – Sets the method of determining the GSM power class if the mobile does not report the power class.

f. Alternate GSM Power Class – If the mobile doesn’t report the power class and Get Alternate GSM Power Class from is set to parameter, the value of this parameter determines the power class of the mobile.

g. TXP GMSK Max TX Level with Specs. – GMSK maximum power specifications based on power class and band.

h. TXP EPSK Max TX Level with Specs – EPSK maximum power specifications based on power class and band.

i. Bad Block Handling – Sets the method of handling bad block errors for the GPRS bit error tests. This parameter supersedes and replaces the Zero Bad Blocks parameter.

j. BLER Bad Block Handling – Sets the method of handling bad block errors for the BLER tests.

k. Block Polling Interval for ETSI B Ack Connections – Changed from Block Polling Interval for Other Connections

l. All frequency band parameters have theT-GSM810 band added to the selection list.

4. The implementation of the 3 Digit PCS Mobile Network Code was incomplete and has been fixed with the addition of the Cell Parameter 3 Digit PCS Mobile Network Code global parameter.

5. The EGPRS Fast General Test returns proper test results with all mixed burst measurements.

6. Moved the WCDMA to GSM Handoff from the WCDMACallProcessing to the

WCDMAGSMCallProcessing class module.

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

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

Channel State'.

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

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

11. Modified the WCDMA 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.

12. Changed the MS Target Power in the WCDMA Maximum Output Power test step from 24 to 21

dBm.

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

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



Known Issues

Installation Issues


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.



1. Cancel or exit from any prompts.2. Remove the USB security key from the USB port.3. Close all applications that are running.4. 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.


6. Insert the Security Key into a USB port on your PC. 7. The Security Key should be recognized next time you run Wireless Test

Manager.


??? <reference number> being displayed in the WTM UI 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 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 E6560C then a file called ' Englishxxxxxxxx.lng ' (where

xxxxxxxx is the file date of the E6560C 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 'Englishxxxxxxxx.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 No known issues.



<Target Directory>\E6568C\RunTime E6568C_WCDMA_GSM_GPRS_EGPRS_SAM_Net.exe Revision 2.0.0.0 Agilent.WTM.dmctaMoM.dll Revision 2.0.0.0 Agilent.WTM.wmctaMoM.dll Revision 2.0.0.0 <Target Directory>\Common Agilent.WTM.dmctaMoM.dll Revision 2.0.0.0 Agilent.WTM.wmctaMoM.dll Revision 2.0.0.0 TestPlanMover.exe Revision 1.5.0.0 LocalizeUtility.exe Revision 1.1.0.0 WTMDataAnalyzer.exe Revision 1.3.0.0 <Target Directory>\Common\NETWizards Agilent.WTM.AddInstrumentControl.dll Revision 1.2.0.0 Agilent.WTM.AddWirelessTest.dll Revision 1.2.0.0 Agilent.WTM.AddInstrumentControl05.dll Revision 1.0.0.0 Agilent.WTM.AddWirelessTest05.dll Revision 1.0.0.0 <Target Directory>\Common\NetWTMVersion1.X\Assemblies Agilent.WTM.Exec.dll Revision 1.8.0.0 Agilent.WTM.ag34970MoM.dll Revision 1.1.0.0 Agilent.WTM.gpioMoM.dll Revision 1.1.0.0 Agilent.WTM.psmtMoM.dll Revision 1.3.0.0 Agilent.WTM.MoMMUIServices.dll Revision 1.0.0.0 Agilent.WTM.MSJRO.Interop.dll Revision 2.6.0.0 Agilent.WTM.PathEffectServices.Interop.dll Revision 1.0.0.0 ScDerivedControls.dll Revision 1.0.1389.23550 ScUserControls.dll Revision 1.0.1389.23557 \WINNT\Assembly (Win2k) \WINDOWS\Assembly (XP)


Agilent.WTM.Exec.dll Revision 1.8.0.0 Agilent.WTM.ag34970MoM.dll Revision 1.1.0.0 Agilent.WTM.gpioMoM.dll Revision 1.1.0.0 Agilent.WTM.psmtMoM.dll Revision 1.3.0.0 Agilent.WTM.MoMMUIServices.dll Revision 1.0.0.0 Agilent.WTM.MSJRO.Interop.dll Revision 2.6.0.0 Agilent.WTM.PathEffectServices.Interop.dll Revision 1.0.0.0 policy.1.0. Agilent.WTM.ag34970MoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.ag34970MoM Revision 1.1.0.0 policy.1.0. Agilent.WTM.Exec Revision 1.0.0.0 policy.1.0. Agilent.WTM.Exec Revision 1.8.0.0 policy.1.1. Agilent.WTM.Exec Revision 1.8.0.0 policy.1.2. Agilent.WTM.Exec Revision 1.8.0.0 policy.1.3. Agilent.WTM.Exec Revision 1.8.0.0 policy.1.4. Agilent.WTM.Exec Revision 1.8.0.0 policy.1.5. Agilent.WTM.Exec Revision 1.8.0.0 policy.1.6. Agilent.WTM.Exec Revision 1.8.0.0 policy.1.7. Agilent.WTM.Exec Revision 1.8.0.0 policy.1.0. Agilent.WTM.gpioMoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.gpioMoM Revision 1.1.0.0 policy.1.0. Agilent.WTM.MoMMUIServices Revision 1.0.0.0 policy.1.0. Agilent.WTM.PathEffectServices.Interop Revision 1.0.0.0 policy.1.0. Agilent.WTM.psmtMoM Revision 1.0.0.0 policy.1.0. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.1.1. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.1.2. Agilent.WTM.psmtMoM Revision 1.3.0.0 policy.2.6. Agilent.WTM.MSJRO.Interop Revision 2.6.0.0 ScDerivedControls.dll Revision 1.0.1389.23550 ScUserControls.dll Revision 1.0.1389.23557 C:\Program Files\Common Files\Agilent Shared\Wireless PathEffectSvc.dll Revision 1.1.0.0

C.01.00 Release – May 2005

C.01.00 Release – OverviewWCDMA/GSM/GPRS/EGPRS Wireless Test Manager Modifications Supported 8960 Test Applications

Known Issues Installation Issues

Uninstalling older software versionsUninstalling all software versionsThe USB security key is not recognized after installationBack-up language files??? <reference number> being displayed in the WTM UI

Other IssuesIssues known at shipment releaseIssues discovered after release


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

http://www.agilent.com/find/E6568B


1. The following test steps have been added:a. EGPRS Start Data Connectionb. EGPRS End Data Connectionc. EGPRS Handoverd. EGPRS Initiate SRB Bit Errore. EGPRS Fetch SRB Bit Errorf. EGPRS Measure SRB Bit Errorg. EGPRS Fast General Testh. EGPRS Modulation Accuracyi. EGPRS Detachj. GPRS Detachk. WCDMA Power Controll. WCDMA Initiate Loopback BLERm. WCDMA Fetch Loopback BLERn. WCDMA Measure Loopback BLERo. WCDMA Phase Discontinuityp. WCDMA Change Service Typeq. WCDMA Concurrent RX TX

2. The following global parameters have been added:a. Restore Amplitude Offsetsb. Test Set Partial Presetc. Wait for Test Set Setup to Completed. Use IMEI in Results File Namee. EGPRS Data Rate Configurationsf. EGPRS Demodg. EGPRS Uplink Frame Segmentationh. GSM GPRS EGPRS DCS Max CCH Power Offseti. GSM GPRS EGPRS MS TX Power Max CCH for Initial Cell Bandj. GSM GPRS EGPRS MSC Revisionk. GSM GPRS EGPRS Custom Payload Patternl. WCDMA PS Domain Informationm. WCDMA DRX Cycle Lengthn. WCDMA Cell Identityo. WCDMA Handoff Allowedp. WCDMA Authentication Algorithmq. WCDMA Authentication Key Lowerr. WCDMA Authentication Key Middle Lowers. WCDMA Authentication Key Middle Uppert. WCDMA Authentication Key Upperu. WCDMA Repeat Pagingv. WCDMA BCCH Update Pagew. WCDMA Security Operationsx. WCDMA IMSI Attach Flagy. WCDMA RLC Reestablishz. WCDMA Maximum Uplink Transmit Poweraa. WCDMA Always Display Remote Messages on Test Set

3. Several of the test step and parameter names have been modified to make them WCDMA or GSM/GPRS/EGPRS specific to make it clear which mobile format they apply to:

a. GSM GPRS EGPRS Change Cell Power Levelb. GPRS EGPRS Fetch Block Errorc. GPRS EGPRS Initiate Block Errord. GPRS EGPRS Measure Block Errore. GPRS EGPRS BLER Reportf. GPRS EGPRS Burst Timing Errorg. GPRS EGPRS Change Downlink Traffic Powerh. GSM GPRS EGPRS Change Cell Bandi. GSM GPRS EGPRS Power vs Time

j. GSM GPRS EGPRS Output RF Spectrumk. GSM GPRS EGPRS TX Powerl. GSM GPRS EGPRS Phase and Frequency Errorm. GPRS EGPRS Change Channeln. GSM GPRS EGPRS TX Current Drain at Levelo. WCDMA Change Cell Power Level

4. Several of the test plan steps have been modified to fix bugs, or take advantage of

the tables parameter functionality that was added to E6568C, or support banded specifications, or to reflect new features in E1968A or E1985B TAs:

a. GSM GPRS EGPRS Output RF Spectrumb. GSM GPRS Power vs Timec. GSM GPRS EGPRS TX Powerd. Start Loope. GPRS EGPRS Initiate Block Errorf. GPRS EGPRS Measure Block Errorg. GSM GPRS EGPRS Phase and Frequency Errorh. GSM Fast General Testi. GPRS Fast General Testj. GPRS EGPRS Change Channelk. GSM Change Channell. GPRS Handoverm. GSM Handovern. GPRS Start Data Connectiono. GSM Base Station Initiated Callp. GSM Mobile Initiated Callq. GSM GPRS EGPRS Change Cell Bandr. WCDMA Registrations. WCDMA Adjacent Channel Leakage Ratiot. WCDMA Maximum Output Poweru. WCDMA Minimum Output Powerv. WCDMA Waveform Qualityw. WCDMA Inner Loop Power Controlx. WCDMA Occupied Bandwidthy. WCDMA Change Channel Typez. WCDMA Initiate Maximum Input Level BERaa. WCDMA Initiate Reference Sensitivity Level BERbb. WCDMA Measure Maximum Input Level BERcc. WCDMA Measure Reference Level BERdd. WCDMA Open Loop Power Controlee. WCDMA Transmit On Off Power

5. New testplans:a. EGPRS test planb. WCDMA & GSM Testsc. WCDMA Manufacturingd. WCDMA Parametrice. WCDMA Quick RX TX

6. Special Notesa. There is a major change in Power vs Time measurement found in test steps GSM GPRS EGPRS Power vs Time, GSM Fast General, GPRS Fast General and EGPRS Fast General.

User can choose to use the test set pre-defined ETSI mask or a custom mask. In either way, the method of specifying the specification/mask has changed.

The change consists in defining the test specification by entering the end points of a level of the PvT mask.

A mask point is defined by a pair (offset, limit value). For upper mask, it would be a pair of (offset, upper limit) and for lower mask, a pair of (offset, lower limit).

To define a mask, WTM will use Stop-Point approach, which means that user needs to specify end points of one section of the mask. The starting point is always located at -50us relative to the middle of the zero-th symbol.

An illustration of how the Stop-Point logic works would be:

-6(dBc) o-------------# | PT3 |-30 o------------# | PT2 |-59 o----------------# PT1 -28 -18 -10 (offset in us)

In order to specify this mask using the Stop-Point logic, users need to define PT1, PT2 and PT3, which are respectively the stop points of levels -59, -30 and -6 dBc. So, the offsets of PT1, PT2 and PT3 should be entered in column ‘Mask Level End Point Offset’. If this mask refers to upper mask, the respective levels should be entered in ‘Upper Limit’ column:

Mask Level End

Point OffsetUpper Limit

-28 -59 -18 -30 -10 -6

b. 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.

c. The parameter Measurement Result Type has been added to the test steps ACLR, Waveform Quality, Phase and Frequency Error, Output RF Spectrum and Power vs Time, since the WCDMA/GSM/GPRS 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.

d. 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: RMC AM 1264, RMC AM 12144, RMC AM 12384, and RMC AM 64384

e. 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.

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

g. The Channel Pair and MS TX Level Pair table windows are no longer launched by pressing a toolbar icon. It is now launched through a parameter in the Start Loop test step called Channel Pair and MS TX Level Pair, respectively. The Exec now supports parameter tables.

h. 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.

i. 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.

j. 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


E1987A A.01.21 or later E1968A A.04.18 or later E1985B B.05.18 or later E1985C C.03.18 or later E1963A A.06.17 or later

Known Issues

Installation Issues

Uninstalling older software versionsIf 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 versionsTo 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 installationSituation: 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 filesBack-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 UISituation1: 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 releaseThe localization utility tool (LocalizeUtility.exe) may not work if Visual Studio .Net is not installed.

Issues discovered after release Situation: Even if a test plan only calls for W-CDMA test steps, the test plan will abort if it is run with a TA that is W-CDMA only (E1963A). The problem is that the GSM/GPRS/EGPRS MoM (Agilent.WTM.dmctaMoM.dll) is sending GSM specific commands to the test set during a reset routine that are rejected by the W-CDMA TA. Solution: A QFE-2 (Quick Fix Engineering) is provided at the web site http://wireless.agilent.com/rfcomms/dloads/wtm/ that replaces the Method of Measurement assemblies: Agilent.WTM.wmctaMoM.dll (E6568C QFE-1) and Agilent.WTM.dmctaMoM.dll, the development class modules: AssemblyInfo.vb and SAMUtilities.vb, and the runtime executable E6568C_WCDMA_GSM_GPRS_EGPRS_SAM_Net.exe. The Agilent.WTM.dmctaMoM.dll replacement assembly has a fix that allows E6568C W-CDMA test plans to work with a WCDMA only TA. The Agilent.WTM.wmctaMoM.dll replacement assembly is the E6568C QFE-1 fix. The class module SAMUtilities.vb has a change that fixes undefined header errors that occur after the E6568C QFE-1 is installed and a GSM/GPRS test plan is run with a GSM/GPRS only TA. The class module AssemblyInfo.vb contains QFE-2 version changes. The runtime executable is a re-compiled .exe that includes the changes to the class modules for those who only have the runtime version of the E6568C. 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: Uninstalling the E6568C (WCDMA GSM GPRS EGPRS) will not remove the ‘HKEY_LOCAL_MACHINE/SOFTWARE/Agilent/Wireless/Wireless Test Manager/E6568C’ and ‘HKEY_LOCAL_MACHINE/SOFTWARE/Agilent/Wireless/Wireless Test Manager Selectable Applications/E6568C’ registry key entries. What this means is that any WTM SAL (N588xA) installed will not show up in the ‘Select new WTM application’ list after the E6568C is uninstalled. Solution: Remove these two keys from the registry manually after the E6568C is uninstalled. 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 ‘E6568C W-CDMA/GSM/GPRS/EGPRS Wireless Test Manager’ product and then the ‘E6568C Release Notes’ link.


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

<Target Directory>\E6568C\RunTime E6568C_WCDMA_GSM_GPRS_EGPRS_SAM_Net..exe

Agilent.WTM.dmctaMoM.dllAgilent.WTM.wmctaMoM.dll

Revision 1.0.0.0Revision 1.0.0.0Revision 1.0.0.0

<Target Directory>\Common Agilent.WTM.dmctaMoM.dll

Agilent.WTM.wmctaMoM.dll TestPlanMover.exe

Revision 1.0.0.0Revision 1.0.0.0Revision 1.3.0.0


LocalizeUtility.exe Revision 1.1.0.0 <Target Directory>\Common\NETWizards Agilent.WTM.AddInstrumentControl.dll Agilent.WTM.AddWirelessTest.dll

Revision 1.1.0.0Revision 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.0Revision 1.1.0.0Revision 1.1.0.0Revision 1.2.0.0Revision 1.0.0.0Revision 2.6.0.0Revision 1.0.0.0Revision 1.0.1389.23550Revision 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.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.0Revision 1.4.0.0Revision 1.1.0.0Revision 1.2.0.0Revision 1.0.0.0Revision 2.6.0.0Revision 1.0.0.0Revision 1.0.0.0Revision 1.0.0.0Revision 1.4.0.0Revision 1.4.0.0Revision 1.4.0.0Revision 1.4.0.0Revision 1.0.0.0Revision 1.1.0.0Revision 1.0.0.0Revision 1.0.0.0Revision 1.0.0.0Revision 1.2.0.0Revision 1.2.0.0Revision 2.6.0.0Revision 1.0.1389.23550Revision 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

© Agilent 2000-2009

http://www.agilent.com/find/contactus


E6568C Web Release Notes - United States Home | Keysight …€¦ · Web view · 2009-07-27WCDMA...

Documents

Transcript of E6568C Web Release Notes - United States Home | Keysight …€¦ · Web view · 2009-07-27WCDMA...