E6566C GSM/GPRS/EGPRS Wireless Test Manager Revision Information

 

Last updated: 12/2007

© Copyright 2004-2007 Agilent Technologies

All Rights Reserved

 

This document describes the features that are in the Agilent Technologies E6566C 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/E6566C 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.01 Release - Dec 2007

 

C.02.00 Release - Nov 2006

 

C.01.01 Release - May 2005

 

C.01.00 Release - October 2004 (initial release)

 

Contact Information

Service and Support

 

C.02.01 Release – Dec 2007

 

C.02.01 Release – Overview

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 interface

Other Issues

Issues known at shipment release

Issues discovered after release

 

Component Release Information

 

C.02.01 Release – Overview

This software release provides modifications to test plan steps, new test steps and additional enhancements including new global parameters.

 

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 parameters have been added or modified to reflecting new features in the 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:

i.         GPRS Handover

ii.        EGPRS Handover

iii.      GRPS Start Data Connection

iv.       EGRPS Start Data Connection

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

i.         Start Loop

ii.        GRPS Start Data Connection

iii.      EGRPS Start Data Connection

iv.       GPRS EGPRS Change Channel

v.        GPRS Handover

vi.       EGPRS Handover

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

i.         EGPRS Start Data Connection

d.        Three, Four and AllBursts of Measurement Burst are selectable. This affects the following test steps:

i.         GSM GPRS EGPRS TX Power

ii.        GPRS Fast General Test

iii.      EGPRS Fast General Test

iv.       GSM GPRS EGPRS Output RF Spectrum

v.        GSM GPRS EGPRS Phase and Frequency Error

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

 

Supported 8960 Test Applications

 

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

 

 

              E1987A

A.05.28 or later

              E1968A

A.07.21 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:

 

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

 

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 ‘E6566C 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>\E6566C\RunTime

 

              E6566C_ GSM_GPRS_EGPRS_SAM_Net.exe

Revision 2.1.0.0

              Agilent.WTM.dmmtMoM.dll

Revision 2.1.0.0

 

 

<Target Directory>\Common

 

              Agilent.WTM.dmmtMoM.dll

Revision 2.1.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

 

 

\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

 

C.02.00 Release – Overview

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 interface

Other Issues

Issues known at shipment release

Issues discovered after release

 

Component Release Information

 

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.

 

GSM/GPRS/EGPRS Wireless Test Manager

 

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

 

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

 

5.       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:

i.         GSM GPRS EGPRS Phase and Frequency Error

ii.        GSM Fast General Test

iii.      GPRS Fast General Test

iv.       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:

i.         GSM GPRS EGPRS Output RF Spectrum

ii.        GSM Fast General Test

iii.      GPRS Fast General Test

iv.       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:

i.         GSM GPRS EGPRS TX Power

ii.        GSM GPRS EGPRS PowervsTime

iii.      GSM GPRS EGPRS Output RF Spectrum

iv.       GSM Fast General Test

v.        GPRS Fast General Test

vi.       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:

i.         GPRS EGPRS Measure Block Error

ii.        GPRS EGPRS Initiate Block Error

iii.      GPRS Measure Bit Error

iv.       GPRS Initiate Bit Error

v.        GPRS Fast General Test

vi.       EGPRS Fast General Test

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

 

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

 

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

 

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

 

 

Supported 8960 Test Applications

 

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

 

 

              E1987A

A.04.27 or later

              E1968A

A.06.56 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:

 

8.       Cancel or exit from any prompts.

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

10.    Close all applications that are running.

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

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

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

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

 

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 ‘E6566C 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>\E6566C\RunTime

 

              E6566C_ GSM_GPRS_EGPRS_SAM_Net.exe

Revision 2.0.0.0

              Agilent.WTM.dmmtMoM.dll

Revision 2.0.0.0

 

 

<Target Directory>\Common

 

              Agilent.WTM.dmmtMoM.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.01 Release – May 2005

 

C.01.01 Release – Overview

GSM/GPRS/EGPRS 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 represents the initial release of the Agilent Technologies E6566C GSM/GPRS/EGPRS Wireless Test Manager. It is a conversion of the E6566A software to Visual Basic .Net 2003 with user interface and functional enhancements. To see the release notes for the E6566A (includes revision information) go to the Agilent Technologies web site http://www.agilent.com/find/E6566A and select ‘E6566A Release Notes’.

 

GSM/GPRS/EGPRS Wireless Test Manager Modifications

 

1.       The following test steps have been added:

a.       EGPRS Detach

b.       GPRS Detach

 

2.       The following global parameters have been added:

a.       GSM GPRS EGPRS Custom Payload Pattern

 

3.       Several of the test plan steps have been modified to fix bugs, or take advantage of the tables parameter functionality that was added to E6566C, or support banded specifications, or to reflect new features in E1968A or E1985B TAs:

a.       GSM GPRS EGPRS Output RF Spectrum

b.       GSM GPRS Power vs Time

c.        GSM GPRS EGPRS TX Power

d.       Start Loop

e.       GPRS EGPRS Initiate Block Error

f.         GPRS EGPRS Measure Block Error

g.       GSM GPRS EGPRS Phase and Frequency Error

h.       GSM Fast General Test

i.         GPRS Fast General Test

j.         GPRS EGPRS Change Channel

k.        GSM Change Channel

l.         GPRS Handover

m.     GSM Handover

n.       GPRS Start Data Connection

o.       GSM Base Station Initiated Call

p.       GSM Mobile Initiated Call

q.       GSM GPRS EGPRS Change Cell Band

r.         GSM Voice Quality

s.       GPRS Measure Bit Error

t.         GPRS Initiate Bit Error

u.       GSM Power vs Level

 

4.       One new default EGPRS test plan.

 

5.       Special Notes:

a.       There is a 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. The default value of column ‘Mask Level End Point Offset’, in parameters ‘PvT GMSK Mask Time Offset with Specs’ and ‘PvT EPSK Mask Time Offset with Specs’, has changed.

 

b.       Support to 1Down, 2Up multislot configuration added.

 

c.        Output RF Spectrum measurement now supports ORFS due to Switching specifications for different MS TX Levels.

 

 

Supported 8960 Test Applications

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

 

              E1987A

A.01.21 or later

 

              E1968A

A.04.18 or later

 

              E1985B

B.05.18 or later

              E1985C

C.03.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 '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

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

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 ‘E6566C 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>\E6566C\RunTime

 

              E6566C_GSM_GPRS_EGPRS_SAM_Net.exe

Revision 1.1.0.0

              Agilent.WTM.dmmtMoM.dll

Revision 1.1.0.0

 

 

<Target Directory>\Common

 

              Agilent.WTM.dmmtMoM.dll

Revision 1.1.0.0

              TestPlanMover.exe

Revision 1.3.0.0

              LocalizeUtility.exe

Revision 1.1.0.0

 

 

<Target Directory>\Common\NETWizards

 

              Agilent.WTM.AddInstrumentControl.dll

Revision 1.1.0.0

              Agilent.WTM.AddWirelessTest.dll

Revision 1.1.0.0

 

 

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

 

              Agilent.WTM.Exec.dll

Revision 1.4.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.2.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

 

 

<Target Directory>\WINNT\Assembly (Win2k)

 

<Target Directory>\WINDOWS\Assembly (XP)

 

              Agilent.WTM.Exec.dll

Revision 1.4.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.2.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.4.0.0

              policy.1.1. Agilent.WTM.Exec

Revision 1.4.0.0

              policy.1.2. Agilent.WTM.Exec

Revision 1.4.0.0

 

              policy.1.3. Agilent.WTM.Exec

Revision 1.4.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.2.0.0

 

              policy.1.1. Agilent.WTM.psmtMoM

Revision 1.2.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 – October 2004

 

C.01.00 Release – Overview

GSM/GPRS/EGPRS 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

Administrator Password Security Loophole

 

Component Release Information

 

C.01.00 Release – Overview

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

 

GSM/GPRS/EGPRS Wireless Test Manager Modifications

 

1.       The following test steps have been added:

a.       EGPRS Handover

b.       EGPRS Start Data Connection

c.        EGPRS End Data Connection

d.       EGPRS Fast General Test

e.       EGPRS Initiate SRB Bit Error

f.         EGPRS Fetch SRB Bit Error

g.       EGPRS Measure SRB Bit Error

h.       GSM EGPRS TX Power
 

2.       The following global parameters have been added:

a.       Restore Amplitude Offsets

b.       Test Set Partial Preset

c.        Wait for Test Set Setup to Complete

d.       Use IMEI in Results File Name

e.       EGPRS Data Rate Configurations

f.         EGPRS Demod

g.       EGPRS Uplink Frame Segmentation

h.       GSM GPRS EGPRS DCS Max CCH Power Offset

i.         GSM GPRS EGPRS MS TX Power Max CCH for Initial Cell Band

j.         GSM GPRS EGPRS MSC Revision
 

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

 

2.       Several of the test plan steps have been modified to fix bugs, or take advantage of the tables parameter functionality that was added to E6566C, or support banded specifications, or to reflect new features in E1968A or E1985B TAs:

a.       GSM GPRS EGPRS Output RF Spectrum

b.       GSM GPRS Power vs Time

c.        GSM GPRS EGPRS TX Power

d.       Start Loop

e.       GPRS EGPRS Initiate Block Error

f.         GPRS EGPRS Measure Block Error

g.       GSM GPRS EGPRS Phase and Frequency Error

h.       GSM Fast General Test

i.         GPRS Fast General Test

j.         GPRS EGPRS Change Channel

k.        GSM Change Channel

l.         GPRS Handover

m.     GSM Handover

n.       GPRS Start Data Connection

o.       GSM Base Station Initiated Call

p.       GSM Mobile Initiated Call

q.       GSM GPRS EGPRS Change Cell Band

 

6.       One new default EGPRS test plan.

 

7.       Special Note

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. 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 Offset             Upper Limit

-28                                                -59

-18                                                -30

-10                                                  -6

 

Supported 8960 Test Applications

 

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

 

              E1985B

B.04.35 or later

              E1985C

C.02.33 or later

              E1968A

A.03.54 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 revision in the ReleaseNotes.htm that is installed with the E6566C 1.0 release into the …\E6566C\Help directory and the one shown (if user selects to view) during the installation shows the wrong information for the Agilent.WTM.AddInstrumentControl.dll and Agilent.WTM.AddWirelessTest.dll components. The correct revision information is shown below in the Components Release Information table.

Issues discovered after release 

1.       ORFS due to switching measurement specification values cannot be specified for different TX Level values.

2.       ORFS due to modulation measurement specification for +/- 400kHz offset is wrong when the measured burst modulation is 8PSK and the ‘ORFS Modulation Apply Min Abs Specs’ is set to ‘Yes’. The absolute specification gets overwritten by the relative one. If ‘ORFS Modulation Apply Min Abs Specs’ is set to ‘No’, WTM generates correct specification.

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

4.       The power supply MoM (psmtMoM) has string to double conversion problems when the OS regional setting is set to a region where its decimal symbol is not a period (“.”).

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.

         We will be closing this loophole in an upcoming WTM Exec release.

 

 

Component Release Information

 

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

 

<Target Directory>\E6566C\RunTime

                 E6566C_ GSM_GPRS_EGPRS_SAM_Net..exe

 Agilent.WTM.dmmtMoM.dll

 

Revision 1.0.0.0

Revision 1.0.0.0

 

 

<Target Directory>\Common

         Agilent.WTM.dmctaMoM.dll

Agilent.WTM.wmctaMoM.dll

         TestPlanMover.exe

         LocalizeUtility.exe

 

Revision 1.0.0.0

Revision 1.0.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.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.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

 

 

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