Last updated: Dec/2012
(C) Copyright 2012
Agilent Technologies
All
Rights Reserved
This document describes the features that are in the Agilent Technologies E6568D 2G/3G/LTE 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/E6568D or http://www.agilent.com/find/E6568E 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.
E.03.00 Release Dec 2012 (Support E6621A PXT LTE4
release, additional LTE Bandwidth: 1.4MHz, 3MHz, 15.MHz, LTE Blind Channel/BW
Handover, LTE Loop for channel/band handovers, new LTE TCs support)
E.02.00
Release June 2012 (Support E5515E 8960 WCDMA release, WCDMA
DC-HSDPA HBLER
measurements and more)
E.01.00 Release May 2012 (Support E6621A PXT LTE3 release, LTE TDD measurements and more)
E.03.00 Release Overview
This release includes all of the features and
functionality present in the E.02.00 Release (See E.02.00 Release July 2012), and the
features described below. To see the latest information for the E6568E, please
go to the Agilent Technologies web site http://www.agilent.com/find/E6568E.
E6621A/PXT Requirements:
WTM E.03.00 is compatible with E6621A release versions v6.4.1.x (LTE4 releases)
The following TAs and LAs are supported by the E.03.00 release of the E6568E.
|
E1963A |
A.19.14 or
later |
|
E1987A |
A.14.14 or
later |
|
E6703H |
H.01.14 or
later |
|
E6785H |
H.01.15 or
later |
·
LTE Blind Channel Handover
This test step has been added to perform blind frequency/channel handovers on the same LTE operating band using LTE4 PXT feature.
The blind handover works with one scenario and using the destination channel/frequency message overwrites.
·
LTE Channel Bandwidth
Handover
This test step has been added to perform channel bandwidth on the same LTE operating band/frequency
The bandwidth handover works with one PXT scenario having one handover RRC Message per channel bandwidth.
· LTE General On/Off Time Mask
This test step has been added to support test case 6.3.4.1 General ON/OFF time mask defined in TS 36.521-1.
· LTE Aggregate Power Control Tolerance
This test step has been added to support test case 6.3.5.3 Aggregate Power Control Tolerance defined in TS 36.521-1.
·
LTE Initial Setup
Channel bandwidth setting has been extended to include all the bandwidths: 1.4MHz, 3.0MHz, 5MHz, 10MHz, 15MHz, 20MHz.
Transmission Mode has been added: TM1, TM2, TM3, TM4, TM6.
·
Start Loop
Start Loop has been extended for LTE channel and band handovers.
The new Loop Parameters implying a blind handover at every loop iteration are:
- LTE DL EARFCN: indicating new DL EARFCN
- LTE DL/UL EARFCN Table: each entry in the table indicates new DL/UL EARFCN
-
LTE Band Table: each entry in the table
indicates new Band and DL/UL EARFCN
3.
New Wcdma Test Plan
4.
Modified WCDMA HSUPA Test Plan/Steps
Remove subtest 5 from WCDMA HSUPA
Test Plan for WCDMA RCDE With HSUPA and WCDMA RCDPA with HSUPA do not support
subtest 5 in the 3GPP TS 34.121 v910.
The following five HSUPA test
steps were compliant with 3GPP TS 34.121 v810 in former
E6568 Wireless Test Manager releases. As the standard
evolves, the test steps below are modified to be consistent with the 3GPP TS
34.121 v910.
o
WCDMA RCDPA with HSUPA is compliant with 3GPP TS
34.121 v910, section 5.2
o
WCDMA RCDE With HSUPA is compliant with 3GPP TS
34.121 v910, section 5.13
o
WCDMA Spectrum Emission Mask with HSUPA is
compliant with 3GPP TS 34.121 v910, section 5.9
o
WCDMA Maximum Output Power with HSUPA is compliant
with the 3GPP TS 34.121 v910, section 5.2
o
WCDMA Adjacent Channel Leakage with HSUPA is
compliant with 3GPP TS 34.121 v910, section 5.10
None
DC-HSDPA test plans in E6568E_03_00 would run with 8960 without doing HW
upgrade, but only the following revisions are supported.
|
E1963A |
A. 18. 07 |
|
E1987A |
A. 13. 07 |
|
E6703H |
H. 00. 06 |
|
E6785H |
H. 00. 06 |
E5515E Requirements: WTM E.02.00 is compatible with E5515E release application versions E1963A A.19.14, E1987A
A.14.14, E6703H H.01.14 and E6785H H.01.15.
Additional functionality to D.01.01 Release Feb 2012 as following:
·
WCDMA HSDPA FRC Type
This parameter is used to select
FRC Type when the menu of E5515 test set RB Test HS-DSCH Configuration Type
is set to FRC Type. These new FRC Types is about WCDMA DC-HSDPA.
|
Parameter Name |
Parameter Type |
Default |
Range |
|
WCDMA HSDPA FRC Type |
OOM
or Integer Enum |
H Set 1 QPSK |
New: H Set 3A QPSK : H Set 3A 16QAM : H Set 6A
QPSK : H Set 6A 16QAM : H Set 8A 16QAM : H Set 10A QPSK : H Set 10A 16QAM : H
Set 12 QPSK |
·
WCDMA Initial Secondary
Cell Power for Signaling
This
parameter is used to set the power of the secondary cell when establish
DC-HSDPA connection.
·
WCDMA Initial DCHSDPA
Secondary Cell Downlink URFCN
This parameter is used to set the URFCN of the secondary
cell when establish DC-HSDPA connection.
|
Parameter Name |
Parameter Type |
Default |
Range |
|
WCDMA
Initial Secondary Cell Power for Signaling |
Double |
-50 |
-130 : -15 |
|
WCDMA
Initial DCHSDPA Secondary Cell Downlink URFCN |
OOM
or Integer Enum |
Higher |
Higher : Lower |
·
WCDMA Change Channel
A new parameter with DC-HSDPA is added to this test step to support WCDMA DC-HSDPA.
·
Start Loop
Two new options with HSPA is added to loop parameter in this test step,
and some options information of loop parameters (such as Channel Pair Index,
DL Channel with UL Channel Set to Auto, HSPA TBI Value, Repeat Steps)
will be displayed in the end of WTM memo box during test plan is running.
|
Parameter Name |
Parameter Type |
Default |
Range |
|
Loop Parameter |
OOM
or Integer Enum |
Channel Number |
New: HSPA TBI Value |
·
WCDMA Measure HSDPA BLER
This test step name change to WCDMA Measure
HSPA BLER, some new parameters and specifications with DC-HSDPA are added to
this test step to test DC-HSDPA BLER and Throughput, a few lines of code are
added to support Channel Type 12.2K + HSPA and HSPA Only, so now this test step
supports channel type 12.2K + HSDPA, 12.2K + HSPA and HSPA Only. Currently this test step works
with HSPA setup and DCHSDPA setup test steps.
And a parameter is added to decide whether display HSUPA Throughput. The detail of new parameters and new specifications as below.
|
Parameter Name |
Parameter Type |
Default |
Range |
|
Secondary Cell Power for HSDPA BLER (dBm) |
Double |
-25.7 |
-130:-15 |
|
Blocks to Test Specified Per Serving Cell |
OOM or Integer Enum |
No |
No:Yes |
|
Serving Cell Number of HSDPA Block to Test |
Integer |
1000 |
1:99000 |
|
Secondary Cell Number of HSDPA Block to Test |
Integer |
1000 |
1:99000 |
|
Display HSUPA Throughput |
OOM
or Integer Enum |
No |
No:Yes |
|
Specification Name (Units) |
Lower Limit |
Upper Limit |
|
Serving Cell WCDMA HSDPA BLER (percent) |
None |
0.1 |
|
Serving Cell WCDMA Information Throughput (kbps) |
700 |
None |
|
Secondary Cell WCDMA HSDPA BLER (percent) |
None |
0.1 |
|
Secondary Cell WCDMA Information Throughput (kbps) |
700 |
None |
·
WCDMA HSDPA 14 Mbps
Downlink Setup
In this test step, downlink physical
channels configuration and channels code are removed and these settings are
instead of by test step Channel Code Setup for 15 HS PDSCH HSDPA.
·
WCDMA HSDPA 7 Mbps Downlink
Setup
In this test step, downlink physical
channels configuration and channels code are removed and these settings are
instead of by test step Channel Code Setup for 10 HS PDSCH HSDPA.
·
WCDMA HSDPA 14 Mbps HSUPA
Setup
In this test step, downlink physical
channels configuration and channels code are removed and these settings are
instead of by test step Channel Code Setup for E DCH With
15 HS PDSCH.
·
WCDMA HSDPA 7 Mbps HSUPA
Setup
In this test step, downlink physical
channels configuration and channels code are removed and these settings are
instead of by test step Channel Code Setup for E DCH With
10 HS PDSCH.
·
WCDMA HSPA Plus Downlink
Setup
This test step name is changed to WCDMA
HSPA 21Mbps Downlink Setup. In this test step, downlink physical channels
configuration and channels code are removed and these settings are instead of
by test step Channel Code Setup for 15 HS PDSCH HSDPA.
·
WCDMA HSPA Plus HSUPA Setup
This test step name is changed to WCDMA
HSPA 21Mbps HSUPA Setup. In this test step, downlink physical channels
configuration and channels code are removed and these settings are instead of
by test step Channel Code Setup for E DCH With 15 HS
PDSCH.
·
WCDMA Reference Sensitivity
Level with DCHSDPA
This test is derived from
step 6.2A of 3GPP TS 34.121-1 V9.2.0 (2010-09).
·
WCDMA Maximum Input Level
with 16QAM DCHSDPA
This test is derived from
step 6.3C of 3GPP TS 34.121-1 V9.2.0 (2010-09).
·
WCDMA Maximum Input Level
with 64QAM DCHSDPA
This test is derived from
step 6.3D of 3GPP TS 34.121-1 V9.2.0 (2010-09).
This test step has been
added to get the different throughput with DC-HSDPA RB Test
Mode connection by configuring the different parameters.
·
Clear WCDMA DCHSDPA Setup
This test step has been added to restore
some parameters default value after setting DC-HSDPA RB Test Mode connection
to avoid influence to another test plan.
·
WCDMA DCHSDPA Activate
Deactivate Secondary Cell
This test step
is used to activate or
deactivate the secondary serving cell by HS-SCCH order when DC-HSDPA call is
established.
·
Channel Code Setup for Non
HSDPA
This test is derived from E.6.1 of 3GPP TS 34.121-1 V9.2.0 (2010-09). It is used to setup downlink
physical channels code for non-HSDPA.
·
Channel Code Setup for 10
HS PDSCH HSDPA
This test is derived from E.6.2.1, E.6.2.2
of 3GPP TS 34.121-1 V9.2.0 (2010-09).It is used to setup downlink physical channels code for equal or less
than 10 codes HS-PDSCH HSDPA.
·
Channel Code Setup for 15
HS PDSCH HSDPA
This test is derived from E.6.2.3, E.6.2.4
of 3GPP TS 34.121-1 V9.2.0 (2010-09).It is used to setup downlink physical channels code for equal or less
than 15 codes HS-PDSCH HSDPA.
·
Channel Code Setup for E
DCH
This test is derived from E.6.3
of 3GPP TS 34.121-1 V9.2.0 (2010-09). It is used to setup downlink physical channels code for equal or less
than 5 codes HS-PDSCH HSPA.
·
Channel Code Setup for E
DCH With 10 HS PDSCH
This test step is used to setup downlink physical channels
code for equal or less than 10 codes HS-PDSCH HSPA.
·
Channel Code Setup for E
DCH With 15 HS PDSCH
This
test step is used to setup downlink physical
channels code for equal or less than 15 codes HS-PDSCH HSPA.
·
WCDMA Selectivity Characterization
This test step is used to measure either the loopback block error ratio
or the bit error rate of the mobile while changing the Cell Power, AWGN or DPCH
Level
Add test step Channel Code Setup for Non HSDPA to the first test step of this test
plan.
Add test step Channel Code Setup for Non HSDPA to the first test step of this test
plan.
Add test step Channel Code Setup for Non HSDPA to the first test step of this test
plan.
Add test step Channel Code Setup for 10 HS PDSCH HSDPA to the first test step of this test plan.
·
WCDMA HSDPA Test Plan for Multiple Sub Tests
Add test step Channel Code Setup for 10 HS PDSCH HSDPA
to the first test
step of this test plan.
Add test step Channel Code Setup for E DCH to the first test step of this test
plan.
Four new WCDMA test plans have been created and
database has been updated to allow the user to reuse this WCDMA test plan.
·
WCDMA Generic DCHSDPA Connection Test Plan
·
WCDMA Activate or Deactivate Sec Cell Test Plan
- Database: has been modified for new parameters and new default test
points
E6621A/PXT Requirements: WTM
E.01.00 is compatible with E6621A release versions v6.3.1.x (LTE3 releases)
Additional functionality to D.01.01 Release Feb 2012 as following:
·
LTE UE Maximum Output Power
·
LTE Maximum Power Reduction
·
LTE Minimum Output Power
·
LTE Frequency Error
·
LTE Error Vector Magnitude
·
LTE Carrier Leakage
·
LTE EVM Equalizer Spectrum Flatness
·
LTE Occupied Bandwidth
·
LTE Spectrum Emission Mask
·
LTE Adjacent Channel Leakage Power Ratio
·
LTE Reference Sensitivity Level
·
LTE Maximum Input Level
·
LTE Tiered RX Reference Sensitivity Search
·
LTE Tiered RX Reference Sensitivity Search AT UE Power
·
LTE Quick Test
·
LTE Initial Setup
·
LTE PXT Reset
·
LTE PXT Emulation Run State
·
LTE UE Connect
·
LTE UE Disconnect
·
LTE Channel Handover
·
LTE Band Handover
"Overwrite" means that the user can
set this parameter dynamically without change of the PXT user scenario.
For example, a user can use the same LTE
test plan for different LTE channel bandwidths, LTE operating bands, and so on.
The LTE
Initial Setup test step has been modified / extended for the following
parameters in table below.
|
DL Channel (extended) |
extended to support new LTE
bands 0:5379 or 5730:8689 or 36000:45589 |
|
E UTRA Band
(extended) |
extended to support new LTE
bands: 1.:25 or 33..43 |
|
Channel Bandwidth
(new) |
5 MHz, 10 MHz, 20 MHz |
|
Scenario File Name
Prefix (modified) |
new default PXT scenario: FDD_NonCombined_v6.3 |
|
pMax (new) |
-50..33 |
|
p0 NominalPUSCH (new) |
-126..24 |
|
P0 UE PUSCH (new) |
-8..7 |
|
NS Value Additional
Spectrum Emission (new) |
1..32 |
|
Sec Authentication Algorithm (new) |
Dummy,
MILENAGE |
|
Security Key Option (new) |
OP, OPc |
|
Sec OP Value (new) |
String
(128 bits) |
|
Sec OPc Value (new) |
String
(128 bits) |
·
LTE EVM Equalizer Spectrum
Flatness
This test step has been
modified to be aligned with 36.521-1 and display Range 1 and/or Range 2 Spectrum Flatness Max Peak
to Peak (dB) depending on the uplink signal frequency:
·
LTE Tiered RX Reference
Sensitivity Search
RSRP measurements have
been added so WTM user might wish to turn on/off the RSRP (reference signal
received power) UE measurements while searching for the reference sensitivity
of the device under test.
·
LTE Tiered RX Reference
Sensitivity Search AT UE Power
RSRP measurements have been
added so WTM user might wish to turn on/off the RSRP (reference signal received
power) UE measurements while searching for the reference sensitivity of the
device under test at a specified UE Power.
·
LTE Channel Handover
This test step has been added to perform blind frequency/channel handovers on the same LTE operating band
·
LTE Band Handover
This test step has been added to perform a band handover (blind frequency handover) to a specified new frequency of potentially a different LTE operating band.
·
Send Receive GPIB With Wait
Timer
This test step is similar to old Send Receive GPIB test step. The difference is that this new test step has a new table GPIB Commands with Specs and Wait Timer in which one column in the data base has been added Wait Time (Seconds). After executing the SCPI command WTM will wait the configured amount of time before proceeding to the next row in the table for the following SCPI command to send.
Two new LTE test plans have been created and
database have been updated to allow the user to reuse this LTE test plan for
any channel bandwidths and any LTE operating bands
- LTE FDD Test
Plan: standard
default LTE FDD testing
- LTE TDD Test Plan: standard
default LTE TDD testing
- Database: has been modified for new parameters and new default test
points
Wireless Test Manager Modifications
Supported 8960 Test Applications
Supported E6621A Firmware and Hardware
Uninstalling older software versions
Uninstalling all software versions
The USB security key is not recognized after installation
??? <reference number> being displayed in the WTM user interface
Issues known at shipment release
Issues discovered after release
Wireless
Test Manager Modifications
Supported 8960 Test Applications
Supported
E6621A Firmware and Hardware
Uninstalling older software versions
Uninstalling all software versions
The USB security key is not recognized after installation
??? <reference number> being displayed in the WTM user interface
Issues known at shipment release
Issues discovered after release
To see the latest
information for the E6568D go to the Agilent Technologies web site http://www.agilent.com/find/E6568D.
1.
Fix defect error "measurement burst setting is not suitable for multislot setting appears when running GSM test step.
2. Fix defect Code Collision Error appears when running existing WCDMA HSDPA Test Plan
3. Fix defect Code Collision Error appears when try to setup call with WCDMA HSDPA 7Mbps HSUPA setup and WCDMA
HSDPA 7Mbps Downlink Setup test step.
4.
Fixed WTM Fails to
Initialize (Fixed with WTM Framework 1.9.3 which is included in this
E6567D.01.01 release)
Issue details: If there are processes running
on the computer that have names longer than 15 characters, WTM fails with the
following message when trying to read those processes: "Error occurred during initialization of
WTM".
5.
Fixed
Send Receive GPIB with E6621A
6.
Fixed
E6621A setting of user defined security K value
The following TAs are
supported by the D.01.01 release of
the E6568D.
|
E1987A |
A.09.21 or later |
|
E1962B |
B.15.18 or later |
|
E1966A |
A.10.18 or later |
The new
HSPA Test Steps require options to the E1963A which are defined as follows:
|
HSPA Test Step |
Option 403 |
Option 405 |
Option 413 |
Option 423 |
|
WCDMA
HSDPA 7Mbps Downlink Setup |
X |
|
|
|
|
WCDMA
HSDPA 14Mbps Downlink Setup |
X |
X |
|
|
|
WCDMA
HSPA Plus Downlink Setup |
X |
X |
|
X |
|
WCDMA
HSDPA 7Mbps HSUPA Setup |
X |
|
X |
|
|
WCDMA
HSPA Plus HSUPA Setup |
X |
X |
X |
|
|
WCDMA
HSPA Plus HSUPA Setup |
X |
X |
X |
X |
E1963A-403 HSDPA Test Modes
E1963A-405 HSDPA 14.4 Mbps Test Modes
E1963A-413 HSUPA Test Modes
E1963A-423 HSPA+ Test Modes
|
The following is required for the E6621A
PXT to be supported by the D.01.01 release of the E6568D:
|
|
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.
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.
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 Sentinel 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 SentinelKeyW.DLL is
installed in the Windows System32 directory. If the file is not present
in the System32 directory, copy the SentinelKeyW.dll from the Sentinel
directory on the Wireless Test Manager installation CD to the Windows System32
directory on your PC.
e.
Run the SentinelSystemDriverInstaller.exe
program in the Sentinel 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 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.
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 .
The localization utility tool
(LocalizeUtility.exe) may not work if Visual Studio .Net is not installed.
To find the latest information about component
and application release notes, visit the following Agilent Technologies web
site http://www.agilent.com/find/E6568D and select the E6568D 2G/3G/LTE Wireless
Test Manager product. Then select desired release note link.
The following
components will be installed with the Development installation of this release:
|
<Target
Directory>\E6568D\RunTime |
|
|
E6568D_2G_3G_LTE_SAM_Net.exe |
Revision
1.0.0.0 |
|
Agilent.WTM.dmctaMoM.dll |
Revision
2.1.0.0 |
|
Agilent.WTM.wmctaMoM.dll |
Revision
3.0.0.0 |
|
|
|
|
<Target
Directory>\Common |
|
|
Agilent.WTM.dmctaMoM.dll |
Revision
2.4.0.0 |
|
Agilent.WTM.wmctaMoM.dll |
Revision
3.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.3.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 and Win7) |
|
|
Agilent.WTM.Exec.dll |
Revision
1.9.3.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.3.0 |
|
policy.1.1. Agilent.WTM.Exec |
Revision
1.9.3.0 |
|
policy.1.2. Agilent.WTM.Exec |
Revision
1.9.3.0 |
|
policy.1.3. Agilent.WTM.Exec |
Revision
1.9.3.0 |
|
policy.1.4. Agilent.WTM.Exec |
Revision
1.9.3.0 |
|
policy.1.5. Agilent.WTM.Exec |
Revision
1.9.3.0 |
|
policy.1.6. Agilent.WTM.Exec |
Revision
1.9.3.0 |
|
policy.1.7. Agilent.WTM.Exec |
Revision
1.9.3.0 |
|
policy.1.8. Agilent.WTM.Exec |
Revision
1.9.3.0 |
|
policy.1.9. Agilent.WTM.Exec |
Revision
1.9.3.0 |
|
policy.1.9.1 Agilent.WTM.Exec |
Revision
1.9.3.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 |
To see the latest
information for the E6568D go to the Agilent Technologies web site http://www.agilent.com/find/E6568D.
7. Added support for the E6621A PXT
8. Added new LTE Test Steps that use the E6621A PXT
9. Added new HSPA Test Steps
10. Added support for Windows 7 operation system
The following TAs are
supported by the D.01.00 release of the E6568D.
|
E1987A |
A.10.12 or later |
|
E1962B |
B.15.18 or later |
|
E1966A |
A.10.18 or later |
The new
HSPA Test Steps require options to the E1963A which are defined as follows:
|
HSPA Test Step |
Option 403 |
Option 405 |
Option 413 |
Option 423 |
|
WCDMA
HSDPA 7Mbps Downlink Setup |
X |
|
|
|
|
WCDMA
HSDPA 14Mbps Downlink Setup |
X |
X |
|
|
|
WCDMA
HSPA Plus Downlink Setup |
X |
X |
|
X |
|
WCDMA
HSDPA 7Mbps HSUPA Setup |
X |
|
X |
|
|
WCDMA
HSPA Plus HSUPA Setup |
X |
X |
X |
|
|
WCDMA
HSPA Plus HSUPA Setup |
X |
X |
X |
X |
E1963A-403 HSDPA Test Modes
E1963A-405 HSDPA 14.4 Mbps Test Modes
E1963A-413 HSUPA Test Modes
E1963A-423 HSPA+ Test Modes
|
The following is required for the E6621A
PXT to be supported by the D.01.00 release of the E6567D:
|
|
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.
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.
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 Sentinel Security Key files. Perform the following
steps to correct the problem:
h.
Cancel or exit from any prompts.
i.
Remove the USB security key from the USB
port.
j.
Close all applications that are running.
k.
Check to see that the SentinelKeyW.DLL is
installed in the Windows System32 directory. If the file is not present
in the System32 directory, copy the SentinelKeyW.dll from the Sentinel
directory on the Wireless Test Manager installation CD to the Windows System32
directory on your PC.
l.
Run the SentinelSystemDriverInstaller.exe
program in the Sentinel directory on the WTM installation CD to reinstall the
drivers.
m.
Insert the Security Key into a USB port on
your PC.
n.
The Security Key should be recognized next
time you run Wireless Test Manager.
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.
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 .
The localization utility tool (LocalizeUtility.exe) may not work if
Visual Studio .Net is not installed.
To find the latest information about component
and application release notes, visit the following Agilent Technologies web site
http://www.agilent.com/find/E6568D and select the E6568D 2G/3G/LTE Wireless
Test Manager product. Then select desired release note link.
The following
components will be installed with the Development installation of this release:
|
<Target
Directory>\E6568D\RunTime |
|
|
E6568D_2G_3G_LTE_SAM_Net.exe |
Revision
1.0.0.0 |
|
Agilent.WTM.dmctaMoM.dll |
Revision
2.1.0.0 |
|
Agilent.WTM.wmctaMoM.dll |
Revision
3.0.0.0 |
|
|
|
|
<Target
Directory>\Common |
|
|
Agilent.WTM.dmctaMoM.dll |
Revision
2.1.0.0 |
|
Agilent.WTM.wmctaMoM.dll |
Revision
3.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 |
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/E6568D
For Agilent contact information: http://www.agilent.com/find/contactus