ADS 2002 Release Notes - Keysightliterature.cdn.keysight.com/litweb/pdf/ads2002/pdf/relnotes.pdf · ADS 2002 Release Notes load ... modify the variable USER_LIBS, in ... It also works

Advanced Design System 2002

Release Notes

February 2002

Notice

The information contained in this document is subject to change without notice.

Agilent Technologies makes no warranty of any kind with regard to this material,including, but not limited to, the implied warranties of merchantability and fitnessfor a particular purpose. Agilent Technologies shall not be liable for errors containedherein or for incidental or consequential damages in connection with the furnishing,performance, or use of this material.

Warranty

A copy of the specific warranty terms that apply to this software product is availableupon request from your Agilent Technologies representative.

Restricted Rights Legend

Use, duplication or disclosure by the U. S. Government is subject to restrictions as setforth in subparagraph (c) (1) (ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS 252.227-7013 for DoD agencies, and subparagraphs (c) (1)and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR52.227-19 for other agencies.

Agilent Technologies395 Page Mill RoadPalo Alto, CA 94304 U.S.A.

Copyright © 2002, Agilent Technologies. All Rights Reserved.

ii

ContentsADS 2002 Release NotesDesign Environment ................................................................................................. 5

Data Display ....................................................................................................... 7Electronic Notebook ........................................................................................... 8Physical Design .................................................................................................. 8

Analog/RF Simulation............................................................................................... 8Nonlinear Devices .............................................................................................. 13

Agilent Ptolemy Simulation....................................................................................... 14HDL Cosimulation............................................................................................... 17ISS Cosimulation ................................................................................................ 18

Examples.................................................................................................................. 18Momentum................................................................................................................ 20Translation to ADS.................................................................................................... 23SPICE Translation .................................................................................................... 23Design Libraries........................................................................................................ 24

EDGE ................................................................................................................. 253GPP W-CDMA.................................................................................................. 26

Instrument Server ..................................................................................................... 26Printing/Plotting ........................................................................................................ 28DesignGuides ........................................................................................................... 29Search ...................................................................................................................... 31

Index

iii

iv

ADS 2002 Release Notes

ADS 2002 Release NotesThis document describes known defects in Advanced Design System 2002 and,wherever possible, provides a workaround. It also identifies errors and omissions inthe documentation.

Design Environment

Design file corrupted on saving

If you run out of disk space while saving a design on UNIX, the design file may getcorrupted. The corrupted file may cause ADS to fail when you open the design. Toavoid this problem, make sure you have enough disk space before running ADS.

Unarchiving .zap files on UNIX with insufficient disk space

ADS may hang if you attempt to unarchive an archived (.zap) project on UNIX and donot have sufficient disk space. This problem has been observed on HP-UX 10.20 butmay also occur on other operating systems.

Ensure that you have sufficient disk space before unarchiving a large project (a largeamount of RAM is also required). If necessary, try renaming the .zap file with a .zextension and use the unzip utility to decompress the project file.

Resolving design and component name conflicts

A delay of up to 20 seconds may occur the first time you use the Save As command inan ADS session. The delay occurs because the program checks for name conflictsbetween the design name and built-in component names. The length of the delay isbased on the number of libraries installed.

Invalid design names

Design names cannot be the same as the names of any built-in components. BecauseUNIX is case-sensitive, you may (although we do not recommend it) name designsafter components as long as you change the capitalization. This is not possible on thePC because the operating system is case-insensitive.

An example worth noting is the commonly used temporary filename Test. This is thename of a Signal Processing component and therefore is not allowed on either

Design Environment 5


platform with the capitalization shown. Using this name with different capitalizationis valid on UNIX, but is invalid on the PC.

Design-related AEL files not automatically updated on saving

When you make changes to an item definition using the Design Parameters dialogbox, the item definition changes are not automatically saved when you save thedesign.

To save the item definition changes you make in the Design Parameters dialog box,click the Save AEL File button before dismissing the dialog box.

Information on library_group is lost when design is copied

If you copy a design for which you have defined a library (the Library Name field inFile > Design Parameters), the library information will be lost.

The workaround is to open the copied design, choose File > Design Parameters, andenter the desired library name in the Library Name field. Alternatively, you canmanually edit the AEL file to add the desired library name.

Deactivated ground connected to named node prevents simulation

The design environment does not recognize a deactivated ground connected to anamed node as a valid condition and produces an error message that preventssimulation. The workaround is to delete the ground or break the connection(Edit > Move > Move & Disconnect) before simulating.

Auto routing may generate incorrect bus connectivity

If moving a component causes wires to be rerouted incorrectly, undo the move,deselect the Reroute entire wire option (Options > Reroute entire wire attached tomoved component), and try the move again.

If the wire is still rerouted incorrectly, undo the move, disconnect the wire(Edit > Move > Move & Disconnect), move the component, and reroute the wiremanually.

Opening multiple designs on Windows

On the Windows platform, ADS will run out of memory if you open multiple designwindows. As far as possible, open or create designs within the same window. You canset opening and creating designs in an existing window as your default option by

6 Design Environment


deselecting the New/Open Design in New Window option in the Main Preference dialogbox (Main window > Options > Preferences).

Data Display

Problem with debug mode on the PC

Using the HPEESOF_DEBUG_MODE on the PC may cause the Data Display serverto hang. This mode should not be used on the PC as far as possible.

Accessing information on trace options

The Help button in the Data Display window's Trace Options dialog does not work.To view the help topic:

ChooseHelp > Topics and Index

And click the links toManuals > Schematic Design and Display > Data Display

Then use the table of contents to open3 Traces > Editing Traces.

UNIX setup information missing from Expressions documentation

The section, “User-Defined Functions” Chapter 2 of the Expressions, Measurements,and Simulation Data Processing manual only documents the setup for PC systems. Ifyou are using UNIX, you cannot write to the installation directory or to the fileexpressions_init.ael. The setup for user-defined functions on UNIX is as follows:

1. Copy your AEL file containing the expression(s) to the folder:

$HOME/hpeesof/expressions/ael (user configuration)

or

$HPEESOF_DIR/expressions/ael (site configuration)

Create the folders if they don't exist.

2. Create a new file named user_defined_fun.ael in the same directory, if it doesn'talready exist.

3. Add the following line in the user_defined_fun.ael file:

Design Environment 7


load("myfile")

where myfile is the name of your AEL file.

4. Restart ADS.

Electronic Notebook

Adding Data Display pages to an existing Electronic Notebook

If you attempt to add a Data Display page (using Add Page and the New NotebookPage dialog box) to an existing notebook, and that page is actually a combination oftwo or more data display files (such as you might create using the Smart SimulationWizard), the Electronic Notebook may crash.

The workaround is to delete the existing /notebook directory in the project of interestand generate the notebook again.

Physical Design

Slow flattening of large designs

Flattening a design during a DRC operation can take very long, especially on slowmachines. In some cases it may help to optimize the DRC memory usage variables(Options > Preferences > Verification).

Moving ports to another layer

You cannot use the Move To Layer (Edit > Move) command to move a port to adifferent layer. Instead, choose Edit > Component > Component Parameters, select thePort, select the layer parameter, and select the desired layer from the drop-down list.

Analog/RF Simulation

Compiling user-defined models on AIX

To compile a user-defined model on IBM AIX 4.3, modify the variable USER_LIBS, inthe user.mak file, as follows:

USER_LIBS = -llinker

8 Analog/RF Simulation


Compiling models on the PC

Before you recompile a user-defined model on the PC,choose Simulate > Stop and Release Simulator from the Schematic window.

Environment variables for simulation, shared libraries, and dlls

To access dynamically loaded devices and to run the simulator you need to make surethe appropriate environment variables are set up as follows.

Before running the ADS Simulator, the following environment variables must be set:

To set the UNIX environment variables using the Korn Shell, add the following toyour ~/.profile.

export HPEESOF_DIR=<ADS_install_dir>export PATH=$PATH:$HPEESOF_DIR/bin

To set the UNIX environment variables using the C Shell, add the following to your~/.cshrc.

setenv HPEESOF_DIR <ADS_install_dir>setenv PATH $PATH:$HPEESOF_DIR/bin

In addition to HPEESOF_DIR and PATH, you also need to set COMPL_DIR. TheCOMPL_DIR variable should have the same value as HPEESOF_DIR. There aretimes when COMPL_DIR can be different than HPEESOF_DIR; however, themajority of users should set COMPL_DIR to be the same as HPEESOF_DIR.

Platform-Specific Variables

Also set the platform-specific variable before running the ADS simulator. The syntaxin the following lines uses the Korn Shell or Bourne Shell. Be sure to use theappropriate equivalent commands for the C Shell.

HP-UX:

export SHLIB_PATH="$HPEESOF_DIR/hptolemy/lib.hpux10:$SHLIB_PATH"

export SHLIB_PATH="$HPEESOF_DIR/lib/hpux10:$SHLIB_PATH"

Solaris 5.6:

Variable UNIX Setting

HPEESOF_DIR <ADS_install_dir>

PATH $PATH:$HPEESOF_DIR/bin

Analog/RF Simulation 9


export LD_LIBRARY_PATH="$HPEESOF_DIR/hptolemy/lib.sun56:$LD_LIBRARY_PATH"

export LD_LIBRARY_PATH="$HPEESOF_DIR/lib/sun56:$LD_LIBRARY_PATH"

Solaris 5.7:



Solaris 5.8:



IBM AIX:

export LD_LIBRARY_PATH="$HPEESOF_DIR/hptolemy/lib.aix4:$LD_LIBRARY_PATH"

export LD_LIBRARY_PATH="$HPEESOF_DIR/lib/aix4:$LD_LIBRARY_PATH"

MS Windows:

path %HPEESOF_DIR%/hptolemy/lib.win32;%PATH%

path %HPEESOF_DIR%/lib/win32;%PATH%

DividebyN component also used in Harmonic Balance

The description for the DividebyN component (Chapter 6, Phase Lock LoopComponents, of the System Models volume), indicates that it works for transient andcircuit envelope simulations. It also works for harmonic balance simulations.

Explanation of tolerances for Options component

The description of the relationships between tolerances in the Options component(Chapter 5, Simulation Control Items, of the Introductions and Simulation volume),is incomplete. Additional details follow.

The simulators work using an iterative method to solve the nonlinear equitations.Given an initial guess x_0, it computes a new guess x_1. From that, it computes x_2.This continues until convergence is reached. When x_j is close to x_j−1, the solutionstops changing. Close is defined as follows:

if (x_j− x_j−1 < reltol*x_j + abstol)

then convergedelse keeps iterating

If the difference between the two iterations is less than the relative tolerance timesthe solution plus an absolute tolerance, the convergence is effective.



Initial Guess setting in Harmonic Balance simulation

The description for the Use Initial Guess setting (Chapter 5, Simulation ControlItems, of the Introductions and Simulation Components volume), is not clear. A moreaccurate description follows.

In the dialog box for the harmonic balance controller, check the Use Initial Guess(Harmonic Balance) box to enter an initial guess for a simulation. This file istypically generated from a previous simulation by enabling Write Final Solution. Ifno initial guess filename is supplied, a default name is generated internally, using thedesign name and appending the suffix .hbs. A suffix is neither required nor added toany user-supplied filename. For example, if you have saved the harmonic balancesolution from a previous simulation, you can later do a nonlinear noise simulationand use this saved solution as the initial guess, removing the time required torecompute the nonlinear harmonic balance solution. Or you could quickly get to theinitial harmonic balance solution, then sweep a parameter to see the changes. In thislatter case, you will probably either want to disable the Write Final Solution option oruse a different filename for the final solution to avoid overwriting the initial guesssolution.

Revised information for System Model Hybrid180 (Ideal 180-degreeHybrid Coupler)

The documentation for this model has changed to the following.

Parameters

Loss = Insertion loss, in dB

GainBal = Gain balance between output ports, in dB

PhaseBal = Phase balance between output ports, in degrees

Rref = Port reference impedance, in specified units

Temp = Temperature, in ˚C

Delay = Time delay for output ports

Range of Usage

Loss >= 0 dB

Delay >= 1.0e-16 sec

-6 dB < GainBal < 6 dB



Notes/Equations/References

1. Although hybrid couplers are typically designed to give an equal power splitbetween the coupled and the direct ports, the choice of coupling coefficient hasbeen provided here for greater flexibility where a coupling of other than 3 dB isrequired.

2. The loss term is applied to both the coupling and the direct transmissioncoefficients.

3. Pin designations (directional coupler notation / sum-difference notation):(IN) = input port / input port #1(ISO) = isolated output / input port #2

( ) = coupled output / summation output

( ) = direct output / difference output

(dB) = -3.0103 dB - Loss(dB) - 0.5 x GainBal(dB)

(dB) = -3.0103 dB - Loss(dB) + 0.5 x GainBal(dB)

(dB) = -3.0103 dB - Loss(dB) + 0.5 x GainBal(dB)

(dB) = -3.0103 dB - Loss(dB) - 0.5 x GainBal(dB)

phase( ) = -360 x Delay x frequency - PhaseBal (degrees)

phase( ) = -360 x Delay x frequency (degrees)

phase( ) = -360 x Delay x frequency (degrees)

phase( ) = -360 x Delay x frequency - PhaseBal + 180 (degrees)

4. With the default setting of PhaseBal = 0, the transmission phase from the inputport to the direct output is the same as the phase from the input port to thecoupled output. This is the configuration of either a magic-T hybrid or a rat-racehybrid. In this configuration, input signals at the input and isolated ports arecombined at the output ports as the sum of the two inputs (on the port) andthe difference of the two inputs (on the port).

5. For time-domain analysis, the frequency-domain analytical model is used.

6. This component has no default artwork associated with it.

Σ∆

SΣ IN,S∆ IN,SΣ ISO,S∆ IN,

SΣ IN,S∆ IN,SΣ ISO,S∆ ISO,

Σ∆



Accessing vendor library component information

Help for Vendor Library components is only available from the Component Librarywindow. To display the documentation for a specific vendor component:

From the Component Library window, select a component and chooseHelp > Component Help.

Incorrect label name in NetListInclude component

The documentation for the NetlistInclude component in Chapter 1 of the Introductionand Simulation Components manual has a section that reads “Similarly, with the“SelectR” section designated, the simulator will see only the capacitor.”This “SelectR” should be “SelectC”.

Nonlinear Devices

Series IV compatible GaAsFET models

The Curtice2, Curtice3, Statz, and TOM GaAsFET models now support the Kf/Af/Ffeflicker noise model. Use the following settings for Series IV compatibility:

Set P=2/3, R=0, C=0, and Fnc=0.

Copy Kf, Af, and Ffe values from the Series IV model.

Don’t use Mixer2 or MixerIMT2 with Budget analysis

Budget Harmonic Balance has no knowledge that a frequency conversion takes placein the SDD-based Mixer2 and MixerIMT2 components. This leads to a frequencyconflict and no plan is generated.

Setting values for HICUM

The default values for HICUM have changed from those in the currentdocumentation, and the default parameter values in ADS reflect these changes.

• Setting Rbi0=0 produces the wrong results in small signal AC simulations. Youneed to set Rbi0>0 or leave it blank.

• Convergence problems may occur in Transient and Harmonic Balance when selfheating is on and the device is dissipating large amounts of power. Either turnoff self-heating (Rth=Cth=0) or try sweeping the source power levels.



Setting values for BSIM3SOI

Setting Rsh=0 produces the wrong results. You need to set Rsh>0 or leave it blank.

Convergence problems with VBIC

Convergence problems may occur in Transient and Harmonic Balance when selfheating is on and the device is dissipating large amounts of power. Either turn offself-heating (Rth=Cth=0) or try sweeping the source power levels.

Transient results for BSIM4

Transient results may differ from UCB spice3 results.

Missing information in Nonlinear device MM9 component

The documentation for the MM9 component in Chapter 5 of the Introduction andSimulation Components manual is missing the following information.

The version implemented is 903.

The address for further documentation from Philips is:http://www.semiconductors.philips.com/Philips_Models/documentation/mosmode19

The Philips JUNCAP model is implemented with the MM9 model to describe theJunction charges and leakage currents.

The parameters between Vr and Ng are JUNCAP parameters.

Agilent Ptolemy Simulation

Ptolemy Model builder error message

On all UNIX platforms you will see the following message during compilation ofuser-defined Ptolemy models:

hped-site: Command not found

Although this message does not affect the compilation, it can be eliminated by settingthe CEDA_SITE environment variable to Agilent.

14 Agilent Ptolemy Simulation


berMC, berMC4, and ErrVecMeas migration problem

The components berMC, berMC4, and ErrVecMeas did not migrate properly fromADS 1.3 to 1.5.

To fix this problem, read the value of the component’s TimeUnit parameter inADS 1.3 and append it to the value of the SymbolTime parameter in ADS 1.5.

If the SymbolTime parameter is set by an expression, the expression must beenclosed in parentheses followed by the unit. For example, if SymbolTime was set toSymTime+X and the ADS 1.3 time unit was msec, then the SymbolTime should be setto (SymTime+X) msec.

The same problem exists with the berMC and berMC4 DelayBound parameter.

Note: If you migrated from ADS 1.3 to ADS 1.5 and installed the ADS 1.5 ServicePack 1, or if you are migrating directly from ADS 1.3 to ADS 2001, ignore thisproblem.If you moved from ADS 1.3 to ADS 1.5 and did not install the ADS 1.5 Service Pack 1,please read this section to understand the problem and its workaround.

SpectrumAnalyzer sink containing CW tones may not display properly

The spectrum may not display properly if the input to the SpectrumAnalyzer sinkcontains CW tones and the NumFreqs parameter is set to a non-zero value.

TimeFile and TimedDataRead components cannot readmultidimensional data

The TimeFile component (Obsolete Sinks library) or TimedDataRead component(Sinks library) cannot read multidimensional data. Attempting to do so will display amisleading error message.

Multidimensional data can be generated using the OutFile or TimedDataWritecomponents when a ParamSweep or Optimization controller is used.

The workaround is to not use multidimensional data files with the TimeFile orTimedDataRead components.

Agilent Ptolemy Simulation 15


TimedSource component simulation problem when reading complexenvelope signal

The TimedSource component will not simulate properly if the Expression parameterreferences an RF timed (complex envelope) signal by its variable or sink name usedin the dataset named in the DataSet parameter.

The TimedSource component will not work with RF timed signals because it does notutilize the RF signal characterization frequency and propagates a zero valuefrequency instead. The component will work properly with baseband timed signals.

The workaround is to only use the TimedSource component with baseband timedsignals. For complex envelope signals, use TimedToCx followed by CxToTimed, whichspecifies the Fc.

Using undefined parameter with NumericExpression orTimedExpression component causes simulation failure

The simulator will fail if an undefined variable or equation is specified for theExpression parameter in the NumericExpression component (Numeric Sourceslibrary) or TimedExpression component (Timed Sources library).

Variables and equations are specified in a VAR component. Variables may also bedefined as design parameters (see the Parameters tab of the Design Parametersdialog box).

The workaround is to use only defined variables and equations.

No iterated bus support

Ptolemy subnetworks do not support iterated ports. The workaround for this is toconnect a Bus component (from the Numeric Control palette) to the port and specifythe bus width for the BusWidth parameter.

There is no way to output a bus as a vector to the dataset. You can use an iteratedinstance of a sink to output the individual values of each bus wire.

No magnitude and phase error sequences in EVM component

In the current implementation of the EVM component there is no way to obtain themagnitude or phase error sequences even with post-processing of data in the datadisplay. The options “Magnitude error sequence” and “Phase error sequence” will be

16 Agilent Ptolemy Simulation


added to the MeasType parameter of the component (and its documentation will becorrected) in the future.

The documentation for the EVM component (Sinks palette) incorrectly mentions that“The magnitude or phase error sequence can be obtained by applying the abs() orphase() functions, respectively, on the Error sequence in the data display.”

The magnitude and phase error sequences are not defined simply as the magnitude(abs) and phase of the Error sequence respectively. Figure 7-14 in the documentationshows the correct definition of the magnitude and phase error.

HDL Cosimulation

Real ports must be initialized for some ModelSim versions for VHDLentities

In a VHDL entity, the real ports must be initialized for certain versions of ModelSimSE (such as version 5.4d) or the ModelSim will fail with an out-of-range error.

Stray processes need to be terminated manually

• On Windows platforms, if an HDL cosimulation is interrupted or it errors out,stray processes may continue (and tie up the license).

• On all platforms, if any other component (non-HdlCosim component) causes aruntime error while simulating a design containing an HdlCosim componentand the ADS simulation stops, the HDL simulator may still be running (andtying up the license).

The workaround for both of these problems is to terminate the stray processesmanually. The processes that may need to be terminated are

vlm.exevsim.exevish.exe (for ModelSim®)verilog.exe (for VerilogXL®)hpeesofsim.exe

Custom HdlCosim components no longer supported

Custom HdlCosim components created using the ADS model builder are no longersupported.

Agilent Ptolemy Simulation 17


Parameter values of HdlCosim components may require updating

Because of changes made to the HdlCosim component parameters in ADS 2001,parameter values of HdlCosim components in your ADS 1.5 designs may need to bere-entered.

ISS Cosimulation

Data types smaller than four bytes cause error messages

Errors will occur if data types less than 4 bytes in size are used with the TI DSPC54x. Avoid using the data types char, uchar, double, long double, float, int, uint,long, ulong short, and ushort.

DSP target limitations on setup

A DSP target should be specified using the TI CCStudio Setup tool. Only one DSPtarget can be specified, and it is limited to the TMS320C6x/TMS320C54x simulators.(Hardware boards such as DSK or EVM cannot be used as the DSP target.)

• If you specify more than one target, the Parallel Debug Manager will openduring cosimulation and the cosimulation will fail.

• If you do not specify a DSP target during setup, a dialog box will pop up duringcosimulation and prompt you to select a target DSP board or simulator. You willthen have to select a configuration and double-click the TI CCStudio icon orrestart TI CCStudio.

File not found messages while running designs

The first time you simulate a design in the example project with theCCStudioGUI=On setting, you will be asked to open the correct TI project. You willalso be able to select the “Don’t ask me again” option. If you do neither, a largenumber of “File not found” messages will be generated during simulation.

Examples

Limitations not documented

On the IBM AIX platform, several application examples (MS_RxMRSL.dsn, forexample) and certain customer-designed complex EDGE systems may not

18 Examples


successfully simulate if the system limit and/or the hpeesofsim executable file headerare not set correctly. For details, refer to the topic, “IBM AIX Memory ProblemsSimulating Very Large Designs” in Chapter 2, Requirements on UNIX Systems, ofthe Installation on UNIX Systems manual.

IS95_Measure_prj generates incorrect EVM value

In the IS95_Measure_prj example, the SymbolTime parameter of model ErrVecMeas(which is now in Obsolete Sinks) is a number without a time unit. This results in anincorrect EVM value. To avoid this problem, manually add the msec time unit to thisparameter.

IS95A_ChnCodec_prj number of frames tested too small

In the example IS95A_ChnCodec_prj, the number of frames tested in the designs istoo small to produce an accurate BER/FER for a high SNR. Use a larger number toobtain good BER curves.

CDMA2K_Measurement_prj generates incorrect EVM value

In the CDMA2K_Measurement_prj example, the SymbolTime parameter of modelErrVecMeas (which is now in Obsolete Sinks) is a number without a time unit. Thisresults in an incorrect EVM value. To avoid this problem, manually add the msectime unit to this parameter.

CDMA2K_RC_TD_prj examples inconsistent with CDMA 2000 standard

In some examples of forward link in CDMA2K_RC_TD_prj, the scrambling mode bylong PN code and the data mapping for OTD mode are not consistent with the CDMA2000 standard. You can still use these examples as references because thisinconsistency has little influence on system performance.

PerchCH_prj data slot settings

In the PerchCH_prj example, the .dsn file has a setting for 1000 slots of data, but theassociated dataset (.dds) file was obtained using a setting of 100 slots. Using largerslot numbers provides more accurate results, but leads to significantly longersimulation times.

Examples 19


Incorrect BER and PER values in WLAN_80211a_PER_prj

In the WLAN_80211a_PER_prj example, the WLAN_80211a_24Mbps_System.dsnand WLAN_80211a_36Mbps_System.dsn files give wrong BER and PER values.

Momentum

Solving in RF mode then plotting S-parameters using the Visualizationtool

If you try to plot S-parameters using the Visualization option, for a project that waslast solved in RF mode, Visualization may crash. This is true when the S-parametersare in either the CITIfile format or the AFS (Adaptive Frequency Sweep) format. Theproblem is caused by the fact that the visualization option is expecting certain typesof data (GAMMA and Z0) that MomentumRF does not generate. The workaround isto display the S-parameters obtained from MomentumRF using the ADS DataDisplay.

Visualization current density off by a factor of 2

The actual current density in a plot is 2 times greater than the value reported byMomentum visualization.

MomentumRF mesh computation failure when substrate is notprecomputed

When simulating with Momentum in RF mode on PC, precomputation of the meshwill fail if the substrate has not been precomputed. The substrate precomputation isNOT invoked automatically during the mesh precomputation.

Stopping Momentum simulation process on Solaris 8

The Momentum simulation process does not automatically stop after selectingSimulation/Synthesis > Stop Simulation... in the simulation status window. Theworkaround is to manually terminate the Momentum simulation process fromcommand line.

20 Momentum


Visualizing surface currents of existing projects

The Momentum user guide does not describe how to visualize the surface currents ofexisting projects with Momentum Visualization.

The surface currents of projects solved with Momentum under ADS 1.0 or ADS 1.1can be visualized using Momentum Visualization. The surface currents shown arethe superposition of weighted port solutions. The definition of a port solution wasaltered in ADS 1.3/1.5. In ADS 1.1 and earlier, a port solution was defined as follows:

A voltage source is attached to the port under consideration and all other ports areleft open. Consequently, displaying individual port solutions will show standing wavepatterns. For the port solution definition in ADS 1.3/1.5, refer to the chapter,Displaying Surface Currents, in the Momentum manual. Port solutions from ADS 1.1and earlier can be transferred to the ADS 1.3 definition.

Contact Agilent technical support if you have trouble transferring port solutions.

Visualizing surface currents using discrete arrow plots

The Momentum documentation does not mention that arrow plots enable you tovisualize the surface currents using a vector representation.

On a dense, uniform grid, a vector represents the sampled surface current. Normally,the grid density should be appropriate. If not, the discrete arrow plot providesanother way to look at the surface currents. In a method of moments solution, yourcircuit is subdivided into a number of cells.

The surface current on each cell is expanded in a set of basis functions (Momentumuses rooftop basis functions). On a cell, there is a basis function associated with eachedge. The total current on a cell is the linear superposition of all basis functions withtheir appropriate amplitude. In the discrete arrow plot, a vector is shown in themiddle of all cell edges representing the basis function amplitude.

Incomplete/incorrect list of available substrate layers

In the Momentum substrate dialog box displayed from the Model Composer wizard,the list of available Layout Layers under the Metallization Layers tap is incompleteand partially incorrect.

The layers available in the schematic window are listed but you can only use thelayout layers because using schematic-only layers will cause errors.

Momentum 21


The workaround is to create a substrate definition for the desired layer in the layoutwindow under Momentum > Substrate > Create/Modify..., and save the substrate file(*.slm). You can then select this substrate file when you use the Model Composerwizard.

Accessing information on creating components

When opening the help topic for the Create Momentum Component dialog whenrunning ADS on HP-UX 10, the browser may crash. To open this topic,

1. Restart the browser from any ADS window (Help > Topics and Index)

2. Click Manuals

3. Click Simulation

4. Click Momentum

5. In the Momentum Topics tab, expand 7 Simulation > Momentum Components

6. Click Component Creation

Incorrect polarization information

The Polarization information in Figure 8-1 in Momentum chapter 8, RadiationPatterns and Antenna Characteristics > Polarization is incorrect. The correctinformation is as per the following figure.

22 Momentum


Translation to ADS

Some MDS components are not correctly placed in layout

When you use the MDS to ADS translator, the location and rotation parameters forsome components do not translate correctly in the layout. You can correct thesemanually by editing the layout drawing after translation. You can also force thetranslator to flatten any parametrically defined footprints/layouts. To translate usingthis option, set the configuration variable MIGRATION_MDS_FLATTEN_LAYOUTequal to TRUE in the configuration file migrate.cfg.

MDS design translation information

When you click the Help button in the MDS to ADS Import dialog box, the topic thatappears is “Translating Designs into ADS.” Note that the preceding topic “ExportingDesigns from MDS,” describes the actual first step of the process, which is using themigrate.ddl script, not the IFF export feature.

Some connections are broken during IFF import

When you use the MDS to ADS translator to translate both schematics and layouts,please check all connections in the imported designs to make sure all components areproperly connected. In some cases the IFF importer is unable to process both Layoutand Design objects at the same time.

SPICE Translation

Simulator error

The gauss() function in the spiceFunctions.net function mapping file is now a reservedword in the ADS simulator. Using the spiceFunctions.net function mapping file toresolve undefined functions during simulation will result in a simulator error.

This function can be disabled by preceding the gauss() entry in the spiceFunctions.netfile with the comment (;) character if the function is not needed. If it is needed, thegauss() function should be renamed hspice_gauss() in the SPICE netlist prior toimport or in the ADS netlist prior to simulation. It also needs to be renamed in thespiceFunctions.net file or directly in the ADS netlist file.

Translation to ADS 23


HSpice dependent resistor

Check the noise source for an HSpice dependent resistor translation for accuracy. Fornetlist translation the component name to check for is V-Source and for schematicimport the symbol name is V_Noise. In both cases check the V_Noise parametershould against the original HSpice netlist to be sure the correct equation is used togenerate the noise.

Pin calculations during import

When you import a netlist using the “ADS Netlist” option, a list of subcircuits showup in the dialog box along with the number of pins in the subcircuit. If your subcircuithas pins on continuation lines, it is possible that the wrong number of pins will becalculated. Be sure to verify and manually modify the number of pins for theNetlistInclude component after import.

Accessing RFIC dynamic link information

The Help button for the Netlist File Include component does not work. Assuming youhave installed the online documentation, you can access this information by bringingup the online documentation from any window (Help > Topics and Index) then usingthe following series of links: Manuals > Design Flow > RFIC Dynamic Link User’sGuide. Select the first topic from chapter 9, “Using the Netlist File IncludeComponent.”

Design LibrariesFor the design libraries listed below, the standard ADS recommended computerconfigurations are typically acceptable. However, when more complex systems aresimulated, the computer memory requirements may increase. 500 MB swap space onUNIX machines and a 300 MB paging file size on PC machines may be required torun large designs.

• cdma2000

• DTV

• EDGE

• 3GPP W-CDMA

• WLAN

24 Design Libraries


• 1XEV

• GSM

EDGE

Pins off the grid for some models

For some models in this Design Library, some pins are not located on the same grid,making it difficult to connect wires to them. Use one of the following methods as aworkaround:

• Reduce the grid interval

• Enable the snap-to-pin option through Options > Preferences

• Shift the model slightly when connecting the wire

Different simulation results depending on platform

The model EDGE_FreqErr_OffsetSupp_Meas may give slightly different simulationresults on SUN platforms than on PC and HP platforms. (This model is only used inthe EDGE_PA_MS_FreqErr_OffsetSupp design of the PA examples project.)EDGE_EVM_WithRef and EDGE_EVM_Meas components are used for EVMmeasurement.

• EDGE_EVM_WithRef is in compliance with the Agilent 89440 Vector SignalAnalyzer

• EDGE_EVM_Meas is in compliance with Option 202 of Agilent E4406A VectorSignal Analyzer that assumes a full structured burst (the 89440 does not).

Improving performance of computationally intensive designs

End-to-end BER and BLER simulations involving thousands of bursts and includingframing, encoding, multipath Rayleigh channel, bit synchronization, andequalization are computationally intensive. The platform of choice and simulationparameter settings in the design can be optimized for improved performance in thesecases.

Design Libraries 25


3GPP W-CDMA

Miscalculated BER for WCDMA3G_UE_FixedRateDemod component

The BER (bit error rate) calculation in the WCDMA3G_UE_FixedRateDemodcomponent is slightly off due to the use of the first frame of data output from thereceiver in the BER calculation. This problem will be corrected in a future release.

Additional information on the WCDMA3G_SignalSources_prj exampleproject

The WCDMA3G_SignalSources_prj Examples project is defined to show how tocreate 3GPP RF signals that model RF signals generated by the Agilent ESG SeriesSignal Generators (E443xB) and perform measurements on these signals includingSignal Power Spectrum, Peak to Mean Ratio, CCDF (complementary cumulativedistribution function) and EVM (error vector magnitude). Essentially, this projectprovides 3GPP signals that are compliant with those generated by the ESGinstrument option 100; it is not expected that signals generated in this project arecompliant with ESG option 200 at this time.

This 3GPP product contains content for the 3GPP FDD mode and does not includeany 3GPP TDD mode capability. A separate product with a separate license isplanned for a future release that will support the 3GPP TDD.

Instrument Server

Older versions cause application error in 89600 VSA link

The Agilent 89600 VSA link in the ADS 2002 release (agilent89600 Version 1.9.1) isonly compatible with Version 3.00 or later of the Agilent 89600 VSA software. Usingan older version of the VSA software results in an application error. In addition,setting the SendIDCommand parameter of the SCPI component to NO crashes thesimulator on the PC.

Problem writing Time Domain data with multiple variables

When you write time domain data in MDIF-TIM format from a dataset containingmore than one variable, only the first variable in the dataset is exported. You can’tselect the parameters that you want to export. This will be fixed in a future release.

26 Instrument Server


Do not use reserved variables with the instrument server

If you attempt to use an ADS reserved variable in the variable definitions in theGMDIF file for the instrument server, the first value in the dataset will be incorrect.

Multi-sweep MDIF files improperly created in instrument server

The instrument server will not write correct results to an MDIF file if the datasetincludes more than one sweep.

DC data improperly exports to CITI file

If you simulate a DC curve tracer, export the dataset to a CITI file, then import theCITI file into a dataset, the original data is not the same.

Workaround: The CITI standard only supports the real/imaginary format. If you setthe instrument server format selection to real/imaginary, the dataset will be properlyimported and exported.

Errors in Touchstone file generated from dataset

The Touchstone data format does not support S-parameter data with unequaltermination impedances; however, when using the instrument server to create aTouchstone file for this type of simulation data, the instrument server will not flagthe error and will incorrectly write the Touchstone file with the terminationimpedance incorrectly listed as R=50.

Problem with datasets using .ds extension

The instrument server does not overwrite existing dataset data blocks, thus a uniqueblockname is required for every read of an instrument or file. You will receive anerror message reporting the need for a unique blockname; however, on Win2000, ADSmay hang if you close the Instrument Server immediately after receiving this errormessage.

Improper reading of units in Time Domain measurements

The instrument server currently does not support time domain measurements from anetwork analyzer. If you attempt to enter these measurements, the stop/start unitswill be returned as Hz, when they should be in seconds.

Instrument Server 27


Reading and Writing Network Analyzer Data

ADS can now read and write data from the following Network Analyzers. This list isin addition to the one provided in the documentation.

Model Numbers added

Agilent E8356A, E8357A, E8801A, E8802A, E3381A, E3382A, E3383A

Description

300 kHz-3,6,9 GHz

Note: Data read-only support for 9 GHz. Two-port data read (S11, S12, S21, and S22)for the E338-series.

Printing/Plotting

Color images printed in black and white

Xprinter cannot print color graphics saved as EPS, PCL4, or PCL5 files. Try printingdirectly to the LaserJet 5M printer or assign the 5M to FILE instead of printer.

Printed and screen colors differ

The HP Color LaserJet printer has problems printing color hardcopy from UNIXinstallations using Xprinter if the PCL Cartridge driver is selected. The colors in thehardcopy produced using this driver do not match those displayed on the monitor.

Use the Color LaserJet PS driver when generating color hardcopy or print inmonochrome.

HPGL/2 output and TrueType fonts

If your design contains any TrueType fonts and you print to file using the HPGL/2format, your text will be lost. To preserve it, convert it to HersheyRomanNarrow asfollows:

• Component Text—Choose Select > Select All. Choose Edit > Component >Component Text Attributes. Select HersheyRomanNarrow from the Font typedrop-down list and click OK.

28 Printing/Plotting


• Other Text—Choose Select > Select All. Choose Edit > Edit Text. SelectHersheyRomanNarrow from the Font Type drop-down list and click OK.

Installing printers on Solaris8

To install a printer you need read and write permission for your$HOME/.Xprinterdefaults file. (The Install documentation incorrectly identifies thisas the .Xpdefaults file.)

For read and write permissions, type

chmod 777 $HOME/.Xprinterdefaults

DesignGuides

Context-sensitive help not enabled for all DesignGuide commands

PC only—If you are using the cascading menu configuration, and you attempt toaccess context-sensitive help (Help > What’s This?) for a command, you may not getthe requested information. Context-sensitive help is not enabled for a number ofcommands. Please refer directly to the documentation for the DesignGuide to displaythe desired information.

Missing help for DesignGuide subnetworks

Many DesignGuide schematics contain subnetworks. If the subnetwork has nomodifiable parameters, there is no online help available for it.

Context-sensitive help not enabled for some Filter DesignGuidecomponent palettes

For the Filter DesignGuide components, the context-sensitive help (Help > What’sThis?) for the component palette does not work for some components. Theworkaround is to place the component of interest in the drawing area, double-click itto access the parameters dialog box, and click the Help button.

DeveloperStudio issues

• The Palette Editor does not update the display of an edited bitmap until you logout and restart ADS (UNIX only)

DesignGuides 29


• There is a refresh problem in the Content Browser. If you map content to asubnetwork collector, it only displays the first nine characters in thesubnetwork name. If you collapse the subnetwork collector, and re-open it, thenthe full name is displayed.

• SUN OS—If you are editing the Palette Name in the Palette Editor, and youpress the down arrow on the keyboard, it produces an error.

• Report Summary for Palette (and others) has a sizing problem; it is not able toshow all of the information without cutting off some text.

• “Adding” a DesignGuide is different from “Building” one. When you “build” aDesignGuide, the files are copied to the $HPEESOF_DIR/designguides/projectsdirectory. This is a quick way to check your work of defining a DesignGuide andyou can remove the files from the project directory by “unbuilding” theDesignGuide. When you “Add” a DesignGuide, an entry for it is added to thestatus file in the $HPEESOF_DIR/tools/lib/dpkg directory. This status file isused to administer items that are installed and you can use it to remove aDesignGuide that you have “added.”

DeveloperStudio limitations not documented

• The Tab Dialog Editor is limited to nine buttons.

• The bitmap viewer in the dialog Insert Palette Item is not as wide as the windowwill permit. It wraps the bitmaps to a second row.

• You cannot use an underscore character (_) in the DesignGuide name forpackaging (packaging is the process of creating a DEBIAN archive file).

• The preview feature of the Bitmap Editor only works on the PC.

• The Palette Editor Insert Palette Item/Change Caption feature is only availableon the PC.

• The Content Editor & System Help Editor do not allow file browsing, so thesource ADS projects must reside at the top level of $HOME, and the startingHTML files must reside at the top level of studio_files/<project_name>/doc.

• The DesignGuide Developer Studio only supports a global build in$HPEESOF_DIR, and not a local build in the $HOME/hpeesof.

• When you package a design guide with the DG Developer Studio, you shouldproduce two packages; one for the PC and one for UNIX, to provide compatiblebitmaps.

30 DesignGuides


• UNIX—The background colors for the window pick up the user settings and donot use the ADS window colors. This sometimes makes the user interfacedifficult to view. The default background colors work best.

• When using the Menu Editor, after you have made a change to the name of amenu, there is a delay in the deselecting of one menu before selecting anothermenu is apparent. Please click once and be patient.

Search

Using Internet Explorer

If you are using MS Internet Explorer to view the ADS Documentation, a problemoccurs when using the Search feature. After entering queries for one or more terms, ifyou use the Back button or navigation tabs to open another page, then return to theSearch, the applet fails when you enter another query. The error message thatappears is:

Error occurred. Please relaunch your browser and try again.

The workaround is to close the browser, then reopen it from ADS usingHelp > Topics and Index.

Partial word queries

Using a partial word for a query entry could prevent the search engine from findingany matches. For example, when you perform a query, use a complete term such ashpeesofsim because no matches will be found for eesofsim.

The function(s) defined in your AEL file can now be used in MeasEqn items inschematic and in data display equations.

Search 31


32 Search

Index
Numerics3GPP FDD mode content 2689600 VSA link error 26AAIX, compiling user-defined models 8arrow plots, information for surface currents 21auto-routing and connectivity 6BBER
enhancing accuracy of value 19improving simulation performance 25incorrect calculations 26incorrect values 20

berMC, migrating 15berMC4, migrating 15BLER, improving simulation performance 25BSIM3SOI values 14BSIM4 values 14Budget analysis and Mixer components 13CCDMA 2000 standards 19CITI file data export issues 27color differences 28color printing 28components, accessing information for Momentum 22connections

issues for MDS IFF import 23maintaining during rerouting 6

convergenceproblems with HICUM 13problems with VBIC 14

copying library group information 6corrupted files 5custom HDLCosim component support 17CW tones display problem in sinks 15DDC data export to CITI file 27deactivated ground 6debug mode on PC 7design libraries, memory requirements 24DesignGuide issues 29, 30designs

invalid names 5memory issues on Windows 6opening in existing window 6

DeveloperStudio issues 29disk space 5DividebyN, using for Harmonic Balance 10DRC, optimizing memory 8DSP target limitations 18dynamically loaded devices, environment variables 9EEDGE, connecting wires 25envelope data, simulation problem with TimedSource16environment variables 9ErrVecMeas, migrating 15ESG instrument compliance in WCDMA3G 26EVM

missing magnitude sequence 16missing phase error sequence 16value incorrect 19

example limitations 18expressions, setup information for UNIX 7extensions, writing to files 27FFER, enhancing accuracy of value 19files

corruption on saving 5delay in saving 5information lost in copying 6invalid design names 5not found message 18saving item definitions 6

flattening large designs 8GGaAsFET model support 13gauss function 23HHarmonic Balance

initial guess option 11using DividebyN 10

HDL cosimcustom component support 17updating parameter values 18

HICUM values 13HPGl/2 fonts 28HSpice resistor noise source translation 24Iinitial guess option explanation 11

Index-1

instrument server, using reserved names 27Internet Explorer and search 31ISS cosim, error messages 18item definitions, saving changes 6iterated bus support 16Llayers, changing for ports 8layout translation of MDS components 23Mmagnitude sequence missing in EVM 16MDS translation

connection issues 23information issues 23of component layout 23

memory issues on Windows 6mesh computation, precompute substrate error 20migrating components 15Mixer components and budget analysis 13MM9 component information 14model builder error message 14Momentum

accessing information on creating components 22polarization information 22stopping simulation on Solaris 20

multidimensional data, reading problems 15multiple sweeps and incorrect results 27multiple variable issues in writing data 26multiple windows, preferences 6Nnames, resolving conflicts 5NetListInclude information 13network analyzers supported 28noise source translation accuracy 24notebook pages, adding 8NumericExpression, simulation failure with undefinedparameter 16Oonline help for subnetworks 29optimizing DRC memory 8Options component tolerance information 10Pparameter value updates 18PC, compiling user-defined models 9PER, incorrect values 20performance improvement 25phase error sequence missing in EVM 16pin calculations, verifying after import 24polarization information in Momentum 22

ports, changing layers 8printers, installing on Solaris 29Rreading units, errors in time domain 27real ports, initialization requirement for VHDL 17reserved names 27RFIC information access 24Ssearch using IE 31Series IV GaAsFET model support 13shared libraries, environment variables 9simulation

improving performance 25platform differences in results 25problem with complex envelope data 16problem with undefined parameter 16recognizing deactivated ground 6reserved words 23

simulator environment variables 9slot number setting 19Solaris

installing printers 29stopping Momentum simulation 20

S-parameter and visualization issues 20SpectrumAnalyzer display problems 15stray processes, terminating manually 17subnetwork information 29substrate

error in mesh computation 20layer list discrepancies 21

surface current visualization information 21System Model Hybrid180 information update 11Ttarget limitations for ISS cosim 18time domain data writing 26TimedDataRead problems with multidimensional data15TimedExpression, simulation failure with undefined pa-rameter 16TimedSource, simulation problem with complex enve-lope data 16TimeFile problems with multidimensional data 15tolerance information for Options component 10Touchstone file errors 27trace options, accessing information 7Transient results for BSIM4 14TrueType fonts 28

Index-2

Uunarchiving files 5UNIX setup information for expressions 7unsupported small data types 18user-defined models

compiling on AIX 8compiling on PC 9error message 14

VVBIC values 14vendor libraries, accessing information 13visualization

density incorrect 20information for surface currents 21

WWCDMA3G example information 26wires

connection issues 25rerouting automatically 6

3

Documents

ADS 2002 Release Notes - Keysightliterature.cdn.keysight.com/litweb/pdf/ads2002/pdf/relnotes.pdf · ADS 2002 Release Notes load ... modify the variable USER_LIBS, in ... It also works