advanced design system 2003a release...

Advanced Design System 2003A

Release Notes

June 2003

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 © 1998-2003, Agilent Technologies. All Rights Reserved.

Acknowledgments

Mentor Graphics is a trademark of Mentor Graphics Corporation in the U.S. andother countries.

Microsoft®, Windows®, MS Windows®, Windows NT®, and MS-DOS® are U.S.registered trademarks of Microsoft Corporation.

Pentium® is a U.S. registered trademark of Intel Corporation.

PostScript® and Acrobat® are trademarks of Adobe Systems Incorporated.

UNIX® is a registered trademark of the Open Group.

ii

ContentsADS 2003A Release NotesInstallation ................................................................................................................ 5Design Environment ................................................................................................. 6

ADS crashes on HPUX 11 when remotely logged in from SUN 5.x .................. 9Data Display ....................................................................................................... 10Electronic Notebook ........................................................................................... 12Physical Design .................................................................................................. 12

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

Agilent Ptolemy Simulation....................................................................................... 16HDL Cosimulation............................................................................................... 25ISS Cosimulation ................................................................................................ 27

Examples.................................................................................................................. 28Momentum................................................................................................................ 31Exporting ADS Designs ........................................................................................... 34SPICE Translation ................................................................................................... 34Wireless Design Libraries ........................................................................................ 35

3GPP W-CDMA Design Library.......................................................................... 36Design Kits ............................................................................................................... 37Instrument Server ..................................................................................................... 39Printing/Plotting ........................................................................................................ 40DesignGuides ........................................................................................................... 41Search ...................................................................................................................... 43Documentation/Online Help...................................................................................... 44

Index

iii

ADS 2003A Release Notes

ADS 2003A Release NotesThis document describes known defects in Advanced Design System 2003A and,wherever possible, provides a workaround. It also identifies errors and omissions inthe documentation. The following table shows the version history for this document:

Installation

Incorrect command to mount CD-ROM on HP-UX

The Installation on UNIX Systems manual uses an incorrect command option tomount the CD-ROM on HP-UX platforms (HP-UX 11.0 and 11i). In the section,Installing Advanced Design System > Installation Steps, use the following commandoptions in step 2 to mount the CD-ROM as shown in this example:

mount -rF cdfs /dev/dsk/c201d2s0

Incorrect documentation for License Preference Tool

In Installation > Installation on UNIX Systems and in Installation on PC Systems inUsing Advanced Design System > Running Advanced Design System > Using theAgilent License Preference Tool, information about the associated environmentvariable is incorrect. Please change the information in this and other locations whereit appears in the documentation.

Version Date Revised/New Issue Title

Initial Release 3/06/03

Web Release May 02, 2003

Update 1 May 19, 2003 New “Incorrect command to mount CD-ROM onHP-UX”“Incorrect documentation for LicensePreference Tool”

Update 2 June 19, 2003 New “Installation on PA-RISC 1.1 machines”

Installation 5


For UNIX and Windows, change the environment variable name from:

AGILEESOFD_LICENSE_PREFERENCEtoAGILEESOFD_LICPREF_<hostname>

where hostname is the name of the machine on which ADS is running.

Change the variable's location in the Windows Registry from:

My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License ManagertoMy Computer\HKEY_CURRENT_USER\SOFTWARE\FLEXlm License Manager

Installation on PA-RISC 1.1 machines

If you have a PA-RISC 1.1 machine, and you intend to install ADS 2003A, you mustinstall the PA-RISC 1.1 hotfix if you install from the disk labeled:

ADS HP-UX 11.0/11.i Program Disk dated May 2003 - Part No. E8900-10200

No hotfix is necessary if you install from the disk labeled:

ADS HP-UX 11.0/11.i Program Disk dated June 2003 - Part No. E8900-10203

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.

6 Design Environment


Save As command may be slow

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 file name Test. This is thename of a Signal Processing component and therefore is not allowed on eitherplatform 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.

Design Environment 7


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.

DSP designs are not updated with new symbols

In DSP designs, when a new symbol is created for an existing component orsubcircuit, instances placed in a design before the new symbol was created willcontinue using the original symbol. Closing and reloading the design, or restartingADS will not update these instances with the new symbol. Only instances added tothe design after the new symbol was created will use the new symbol. There is noworkaround for this problem.

Pin numbers for component instances and their symbols may bemismatched in DSP designs

Designs created prior to the ADS 1.3 release allowed pin number values to be set tozero or negative numbers. In ADS 2003A, the automatic symbol update featuremigrates these older designs so pin numbers will match. However, automatic symbolupdating is available only for A/RF designs. DSP designs created prior to the ADS 1.3release may contain components with mismatched pin numbers between theirinstances and symbols when opened in ADS 2003A.

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 bydeselecting the New/Open Design in New Window option in the Main Preference dialogbox (Main window > Options > Preferences).

New GDSII option will not work in previous versions of ADS

When exporting ADS designs that contain rectangles to GDSII files using the newoption “Rectangles as boxes”, you will not be able to import the resulting GDSII fileinto previous ADS releases.



Non-orthogonal rotations can put pins off grid

If the rotation increment is not a multiple of 90 degrees, it is possible to get symbolpins off the grid. This typically happens when the rotation angle is set to 45 degrees.When objects are rotated 45 degrees and then rotated again for another 45 degrees,the resulting instances may have their pins slightly off the grid. It is stronglyrecommended that users should check the Options > Preferences Entry/Edit RotationAngle and set it to 90 degrees.

ADS crashes on HPUX 11 when remotely logged in from SUN 5.x

When logging on to a Sun workstation, either Solaris 7 or Solaris 8 and then remotelylogging to an Hpux 11 machine and running ADS with the DISPLAY set to the sun,the ADS main window comes up. However, when you try and open a new project, thewindow will freeze for a few minutes, then vanish and ADS crashes.

This process works in ADS 2002 but fails in ADS 2002C and ADS 2003A.

Workaround: First, copy all the font directories found on the HP machine but notpresent on the SunOS workstation over to the SunOS workstation. Next, run thefollowing script which installs the fonts on the Sun workstation before you rlogin toan HP workstation. Once the HP fonts are installed by the script, ADS will run on HPworkstation through the Sun workstation.

#!/bin/sh

# setfonts

# Set fonts to avoid ADS Layer_API problem when rlogin from SunOS to HP

# J. T., 2-20-2003

# Your paths and values may be different!

# restore to default before setting fp to avoid xset coredump

xset fp default

xset fp rehash

for fntDir in /usr/openwin/lib/X11/fonts/FontsOnHP/hp_kana8 \

/usr/openwin/lib/X11/fonts/FontsOnHP/hp_roman8/75dpi \

/usr/openwin/lib/X11/fonts/FontsOnHP/iso_8859.1/100dpi \









/usr/openwin/lib/X11/fonts/FontsOnHP/misc \

/usr/openwin/lib/X11/fonts/FontsOnHP/ms.st/licenses/STSYSTEM/DISPLAYS \

/usr/openwin/lib/X11/fonts/FontsOnHP/ms.st/licenses/STSYSTEM/PRINTERS \

/usr/openwin/lib/X11/fonts/FontsOnHP/ms.st/typefaces \



/usr/openwin/lib/X11/fonts/FontsOnHP/type1.st/licenses/STSYSTEM/DISPLAYS \

/usr/openwin/lib/X11/fonts/FontsOnHP/type1.st/typefaces

do

xset +fp $fntDir

xset fp rehash

done

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 is invoked by the command hpads_verbose. If possible, do not usethe debug mode on the PC.

Reverting to the old Fill Patterns

The default fill patterns used by ADS have changed. The new patterns are designedto be more suitable for MMIC design than the old patterns. The old patterns are stillavailable if desired.

The fill pattern file is identified in the ADS environment variable %HPEEFILL. TheHPEEFILL environment variable is defined in the file hpeesof.cfg, which is found inthe $HPEESOF_DIR/config directory.

The default value of the HPEEFILL variable is $HPEESOF_DIR/config/hpeefill.cfg.The old fill patterns are specified in the file $HPEESOF_DIR/config/hpeefill_old.cfg.

To restore the old fill patterns open the file hpeesof.cfg in a text editor and find thefollowing line.

HPEESOF_FILL = $HPEESOF_DIR/config/hpeefill.cfg

Change the name of the fill pattern file to hpeefill_old.cfg.

The line should now be:

HPEESOF_FILL = $HPEESOF_DIR/config/hpeefill_old.cfg

This change will cause all designs to use the old set of fill patterns when you nextlaunch ADS.



UNIX setup information missing from Expressions documentation

The Expressions, Measurements, and Simulation Data Processing manual, in “Usingthe MeasEqn Function Reference” > “Manipulating Simulation Data with Equations”> “User-Defined Functions”, documents the setup only for PC systems. If you areusing 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:

load("myfile")

where myfile is the name of your AEL file.

4. Restart ADS.

S-parameter data are read as a matrix, not as individual S-parameters

When an S2P data file name contains a hyphen (-), the data is read as an S-array andnot as individual S-parameters. This causes traces to appear incorrectly on a plot.Hyphens in file names of other data types may cause similar problems.

Workaround: Do not use hyphens in file names.

Documentation in Data Display Manual “Setting Trace Preferences”incorrect

In Chapter 3 of the Data Display manual in the section called, "Setting TracePreferences", step 7 should read:

Click the Parameter Sweeps tab and set the options that control the appearance ofswept data (subtraces). The Automatic Sequencing options are:



Line Type - Overrides the default Line Type of the trace and automatically usesdifferent line types for each sweep of the data.

Symbol Type - Overrides the default Symbol Type of the trace and automatically usesa different symbol for each sweep of the data.

Line Color - Overrides the default Line Color of the trace and automatically usesdifferent colors for each sweep of the data.

One or all of the Automatic Sequencing options described above can be enabled at anyone time. If all three options are selected, the order in which they are sequenced isLine Type, Symbol Type and Line Color.

Note If you check more than one option, you will not see sequencing for the nextoption start until you have exhausted the previous option. There are many line andsymbol types. Be aware that if you check all three options, trace color won't start tochange until over a hundred subtraces exist, which is not a practical configuration.

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

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.



Push/Pop performance problem after importing dxf file

After importing a hierarchical layout (i.e., DXF, GDSII, etc.), if you push into a subcircuit and then pop out of it, there may be a long delay (several minutes) before thepop out operation is completed. The same delay can exist when invoking thecommand Edit > Component > Update Component Definitions.

Workaround: After importing the layout, go to the Main window and select File >Save All.

Problems in placing parametric subcircuit in layout

A problem has been identified when placing a parametric subcircuit in Layout. Thevalue of a passed parameter is not passed into the lower levels of a multilevelsubcircuit. This can cause artwork macros to not update shape and size as expected.

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.

ParamSweep component cannot sweep temperature

Do not use the Ptolemy ParamSweep component to sweep temperature (temp) whenusing cosimulation or fast cosimulation modes. It does not sweep temp correctly.

Incorrect documentation about GlobalNode

In Simulation > Circuit Simulation > Preparing a Circuit for Simulation > NamingNodes, replace the third paragraph about using a GlobalNode with the following:

By placing a GlobalNode component on a sub-level or top-level schematic of a design(Insert > Global Node), you can select and edit the name of a node that will maintainthe same identity throughout the entire hierarchy of designs. In other words, thenodes with the same name as the global node name in other designs are allelectrically connected. This facilitates the interconnection of boards, IC chips, andconnectors.

Analog/RF Simulation 13


New system environment added to specify the path to UCM Model

A new system environment has been added to specifiy the path to UserCompiledModel.

; USER_MODEL_PATH can be used as a shell environment variable which

defines

; the path to UserCompiled Models.

MASTER_MODEL_PATH=$USER_MODEL_PATH:%USER_MODEL_PATH:%EESOF_MODEL_PATH

Nonlinear Devices

Do not use Mixer2 or MixerIMT2 with Budget Analysis

Budget simulation in Harmonic Balance has no knowledge that a frequencyconversion takes place in the SDD-based Mixer2 and MixerIMT2 components. Thisleads to a frequency conflict and no plan is generated.

Diode model may cause simulation to fail on Windows XP

A defect in the Diode model may cause a memory error on the Windows XP platform.A workaround for this problem is to set a value for the Diode model parameterRs=<value>, where <value> should be no less than 1e-4.

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.

14 Analog/RF Simulation


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.

Transformer and TransformerG obsoleted

The Transformer and TransformerG components have been obsoleted but are stillavailable for backwards compatibility. For ADS version 2003A substitute the TFcomponent instead of Transformer and TransformerG.

Harmonic Balance parameter “KrylovUseGRMES_Float” no longersupported

The Harmonic Balance parameter "KrylovUseGRMES_Float" is no longer supported.A warning message will be issued in the status window in the case that thisparameter is set by the user, and the simulation will procede as usual.

Modified exp() fnction can interact with user-defined functions

Simulator Expressions (modification to the exp() function)

The exp() simulator expression was modified in order to make symbolically defineddevice (SDD) modeling more robust. However, the new default behavior can interactand break existing user implementations of soft_exp() or equivalent functions.

For real values, it is now always a soft limited exponential that turns into a linearfunction above the maximum argument value.

exp(x,[max_arg]) = if (x < max_arg) then exp(x) else (1 + x - max_arg)*exp(max_arg)

It is only continuous to the first derivative. The maximum argument value can beexplicitly specified by the optional second argument to the exp() function. If thisargument is not provided, it uses a global gCircuit value that can be set by theOptions parameter MaxExpArg. The default value for this is 60.0. The MaxExpArgparameter must be entered using the Other = parameter.

Analog/RF Simulation 15


Function add_tr_inductor() interface has been changed in ADS 2003A

The return value of the function add_tr_inductor() has been changed to integer inADS 2003A. Both add_tr_inductor() and add_tr_lossy_inductor() return a positiveinteger upon the sucessful completion. The integer is the inductor index which can bepassed to add_tr_mutual_inductor() as an inductor ID. 0 is returned when thefunction call fails.

MixerIMT2 may not generate correct IMD levels

The MixerIMT2 documentation (in Components > Circuit Components > SystemModels > System Data Models), describes the MixerIMT2 component. It includes adescription that explains how the values in the table are used to determine the levelsof the IMD when the RF and LO signals are different from the reference levelsdefined on the IMT table. Please be aware that the simulated signal levels of the IMDtones from the MixerIMT2 component may not follow this description when the RFsignal levels are different from the reference given in the IMT table.

Agilent Ptolemy Simulation

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.

16 Agilent Ptolemy Simulation


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

Workaround: Use only defined variables and equations.

TimedExpression component ignores imaginary parts of expressionwhen FCarrier=0

In releases prior to ADS 2002C, the TimedExpression component (Timed SourcesLibrary) allowed non-zero imaginary parts for the Expression parameter even whenFCarrier=0, which resulted in generating complex envelope signals withcharacterization frequency equal to 0. Now, when FCarrier=0 the imaginary part ofthe Expression will be ignored.

Input requirements have changed for FreqMultiplier component

The FreqMultiplier component (Timed Nonlinear Library) no longer accepts timedbaseband signal inputs.

Agilent Ptolemy Simulation 17


FCarrier in CxToTimed component accepts positive values only

In previous releases, the CxToTimed component’s FCarrier=0 setting allowedgeneration of a complex envelope signal with characterization frequency equal to 0.FCarrier now accepts positive values only. If there is a need to assign a timestamp toa numeric complex envelope signal so that it can be stored in a TimedSink andplotted in the data display with time as the X-axis, set FCarrier to any positive value.

NumericSink component is a multiport

The NumericSink component (Sinks Library) was converted to a multiport; it nowaccepts busses at its input.

Picture equations not properly displayed in Internet Explorer

Some picture equations in the online help are not properly displayed in InternetExplorer.

Workaround: The workaround for this problem is to print the documentation for thecomponent in question. This can be accomplished by doing a search for thecomponent in ADS and then printing the topic.

SpectrumAnalyzer component output may differ from ADS 2002

The SpectrumAnalyzer component (Sinks Library) output may differ by a scalingfactor from the output obtained in ADS 2002 when FStart, FStop, and NumFreqsparameters are given values other than the default values.

Connectivity error when DSP subnetwork uses an iterated port

Ptolemy subnetworks do not support iterated ports. If a DSP subnetwork uses aniterated port, a connectivity error will be generated. 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. This creates a single multiport in thesubnetwork.

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

Incorrect overflow percentage reported

When the UseArrivingPrecision parameter of AddFix, AddFix2, MpyFix, or MpyFix2is set to YES and the ReportOverflow parameter is set to REPORT, the reportedoverflow percentage (percent of fixed-point calculations that resulted in overflow) iswrong.

Sink data or variable value is missing from generated dataset

When a sink's instance name is the same as the name of a variable defined in a VARblock, the sink's data or the variable's value (if the variable is exported to the dataset)may be missing from the generated dataset.

Inadequate warning messages

MixerRF and MultiplierRF do not display warnings when signals of incorrect type(baseband or complex envelope) are connected to their inputs.

Warning message missing when cosimulation uses default carrierfrequency value

If the EnvOutSelector component’s OutFreq parameter is set to Bandpass, you mustspecify an output frequency value. If the frequency specified is not within 0.01% ofthe fundamental, a default value of 100 MHz is used, but a warning message aboutthe change is not displayed.

File readers do not read input file incrementally

The SDFRead, TimedDataRead, and TimeFile components allow users to readsignals saved in various file formats (tim, bintim, sig, asgsig, dat) into ADS. These filereaders will read the whole content of the user specified file at the beginning of thesimulation even if the simulation does not need to use the whole signal saved in thefile (simulation stop time is smaller than the length of the signal saved in the file).This may slow down short simulations.



ControlSimulation=NO does not always give expected behavior

For some sink components used with multi-rate designs, the parameterControlSimulation=NO does not always result in the correct number of data pointscollected. The recommendation is to be aware of this limitation and setControlSimulation=YES.

MSK_Recovery causes inversion of data

The MSK_Recovery component will sometimes cause recovered data to be inverted.The recommendation is to be aware of this limitation and invert data as neededoutside the output pins of MSK_Recovery.

NumericSource cannot read data of type Matrix

The NumericSource component is not able to read Matrix type data that was storedin the referenced dataset. The recommendation is to not use Matrix type data from adataset with the NumericSource component.

DNL parameter of ADC_Timed and DAC_Timed does not work correctly

The parameter DNL in ADC_Timed and DAC_Timed does not work correctly. Thisparameter has been disabled in these two models (only the value of 0 is allowed).

Red “anytype” pins do not work properly with timed signals

Components with “anytype” input pins will not propagate “timed” signals properly.These “anytype” components should only be used with numeric signals (int, float,fixed-point, complex, and matrix). This restriction applies to the components in theNumeric Control library, such as the Commutator component.

Windows are improperly defined and applied to Timed Filters

The window specified in the Window parameter for all LPF and BPF filters is appliedto the filter’s impulse response and not its frequency response. For filters that do nothave a symmetric impulse response, that is, all filters except RaisedCosine andGaussian, using a window other than Rectangular may lead to unexpected results.



ADS2003A Digital Filter Designer cannot open files created with ADS2002C

Trying to open a filter design created with ADS2002C in ADS2003A gives an errorstating that the filter design was created using version 160.400 but the currentversion is 160.300.

Workaround: Change the lineUse the a text editor to modify the the design file.Change the line:

dfuiuser_version ( “160.400” ) ;

todfuiuser_version ( “160.300” ) ;

Multiple DF controllers are not allowed on the same schematic

An abnormal simulation termination will occur when two DF controllers are in adesign. The recommendation is to use only one DF controller in a DSP Schematicdesign.

Cluster Loop and Acyclic Loop scheduler may take very long toschedule a complex multi-rate design

The DF controller's Cluster Loop Scheduler and Acyclic Loop Scheduler may take anexcessive amount of time to schedule a complex multi-rate design.

Workaround: Use the Classical Scheduler.

Misleading error message appears if DF controller is missing

When starting a Ptolemy simulation, the following, misleading, error message mayappear:

Error detected by HPEESOFSIM during netlist parsingUndefined parameter ‘DefaultROut’ used by ‘.X ’

This message indicates that the design is missing a DF controller.

Modifications in MATLAB script files are not updated

When running Ptolemy simulations using MATLAB models in Windows, valuemodifications in external .m function files are not updated between successivesimulations. The workaround is to type anything in the MATLAB command windowto refresh the .m files.



Limitation on naming user-defined models

User-defined Ptolemy models cannot have the same name as standard ADS Ptolemymodels. Creating a user-defined Ptolemy model with the same name as a standardADS Ptolemy model may cause the simulator to crash when that model is used.

Renamed Instrument Link models

The following Instrument Link Models have been renamed for ADS 2003A(PC/Windows only):

ESG4438CSink renamed ESG_E4438C_Sink

ESGInterface renamed ESG_E443xB_Sink

ArbInterface renamed AFG_E1445A_Sink

VSA89600 renamed VSA_89600_Sink

VSA89600Source renamed VSA_89600_Source

VSA89600_1 renamed VSA_89600_1_Sink

VSA89600_2 renamed VSA_89600_2_Sink

VSA89400 renamed VSA_89400_Source

PatternGen renamed PatGen_16522A_Sink

Note For a list of supported GPIB interfaces for SICL/VISA IO-based components,see the Using Instruments documentation in chapter 1, “Using InstrumentInterfaces” > “GPIB Interfaces”.

Instrument models missing in UNIX

For UNIX platforms the following models have been removed in ADS 2003A:

ESGInterface

ArbInterface

VSA89400

PatternGen



VSA_89600_Sink models cause Tk plots to hang

If you are using VSA_89600_Sink models in a simulation with Tcl/Tk models and youminimize a Tcl/Tk dialog box or window you will be unable to reopen that dialog boxor window. The result is, you must exit the VSA 89600 software, which in turn causesADS to hang, forcing you exit ADS.

Workaround: Pause the measurement using the pause icon on the VSA 89600 UItoolbar and then maximize the Tcl/Tk dialog box or window.

VSA_89600_Source component does not work properly whenAutoCapture=YES

The VSA_89600_Source component in Ptolemy does not work correctly whenAutoCapture=Yes. When a simulation containing a component setup like this isexecuted, hpeesofsim.exe crashes on the second and subsequent tries. This fix will beavailable in the next maintenance release (post version 4.00) of the VSA 89600software.

Uninstalling a prior ADS installation after installing ADS 2003A causeserror in ESG_E4438C_Sink

When the ESG_E4438C_Sink model is used to communicate with an ESG E4438Cinstrument after a prior version of ADS has been uninstalled, ADS reports “E1:Error,Class not registered.” This occurs because the ADS uninstall process deletes thewindows registry entry made for the EsgCom.dll COM object.

Workaround: Execute the following from the command line:

regsvr32 /s <ADS_INSTALL_DIR>/bin/EsgCom.dll

where <ADS_INSTALL_DIR> is the absolute path to the ADS 2003A root directory.

Using ESG4438CSink in ADS 2002 (with instruments upgrade) afteradding an installation of ADS 2003A causes ADS to crash

When installing ADS 2003A, the registry entry is updated to point to the newerversion of EsgCom.dll. Trying to use ESG4438CSink in ADS 2002 with the newerversion of EsgCom.dll containing ESG_E4438C_Sink will cause ADS to crash.

Workaround: Execute the following from the command line:

regsvr32 /s <ADS_INSTALL_DIR>/bin/EsgCom.dll



where <ADS_INSTALL_DIR> is the absolute path to the ADS 2002 root directory.

Note The registry entry must be manually modified by running one of the twopreceding commands every time you switch between ESG4438CSink in ADS 2002and ESG_E4438C_Sink in ADS 2003A.

Using latest version of Agilent IO Libraries recommended

We strongly recommend using the latest available version of the IO Libraries, whichis downloadable from:

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

VeeLink Component Support

The VeeLink component in ptolemy is supported on Windows NT/2000/XP.

IO can fail when using VeeLink with Agilent 82357A USB/GPIB converter

Using the Agilent 82357A USB/GPIB converter while running the Vee Service underthe system account can cause IO to fail when using the Ptolemy VeeLinkcomponent.

Workaround: When using the 82357A with the VeeLink, run the Vee service under anamed account, when setting up the VEE Service Manager, instead of the SystemAccount.

VeeLink component can cause internal error in VEE

Using the Ptolemy Vee Link component on a workstation that has a numericcharacter as the first letter of the host name causes an internal error in Vee. Forexample, if the PC you are using to run a simulation has a host name of 99Agent, thesimulation status window will record an error with the text Internal error, specifyingthe VeeLink component as the error source.

Workaround: Change the host name to have an alpha character first (i.e., Agent99) oruse the IP Address in the HostName field when configuring the VeeLink component.



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.

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.



Cosimulation wrapper generates improper VHDL code and compilationfails

If user-written VHDL source code has a top level HDL source file containing acomma-separated list of libraries, the cosimulation wrapper does not generate properVHDL code. The compilation fails. The following example shows a comma-separatedlist:

library IEEE, test;use IEEE.std_logic_1164.all;use IEEE.std_logic_arith.all;use test.all;

The workaround is to use only one library name per library declaration, as shownhere:

library IEEE;use IEEE.std_logic_1164.all;use IEEE.std_logic_arith.all;library test;use test.all;

Non-interactive HDL Cosimulation with ModelSim SE/EE 5.6b or higherfails on UNIX machines

On any UNIX machine the cosimulation will fail if you use ModelSim 5.6b or higherwith the HdlCosim component when HdlSimulatorGUI=Off. To avoid this problem,use one of the following workarounds:

• Set the HdlCosim component parameter HdlSimulatorGUI=On. This opens theModelSim GUI making the cosimulation interactive. You will need to enter thefollowing run command (or similar run commands) in the ModelSim GUI:

run -all

You will also need to exit using the following quit command:

quit -f

• You can avoid the interactive mode and cause the GUI to open, then closeautomatically. Set the HdlCosim parameters HdlSimulatorGUI=On andCmdArgs="-do test.do". Then create a ModelSim script file test.do under theproject's data directory. Add the following lines to the file:

run -allquit -f



During HDL cosimulation the HDL simulator processes must be stoppedmanually to release licenses

If during HDL cosimulation, a component other than an HDL cosimulationcomponent on the Ptolemy schematic causes a simulation to stop the HDL simulatorprocesses invoked must be stopped manually to release the product licenses.

HDL Cosimulation (non-UI) with multi-threaded scheduler may hang-upH

On Windows 2000/XP dual processor PC’s using any HDL cosimulation component innon-UI mode (setting the parameter HdlSimulatorGUI=Off) with the DF controllermulti-threaded scheduler option selected, may cause the cosimulation to hang.

Workaround: Do not use the multi-threaded option with HDL Cosimulation in GUImode or identify the started processes and manually kill them.

VxlCosim does not support Verilog-XL 5.0 (LDV 5.0)

Using VerilogXL cosimulation component VxlCosim with VerilogXL 5.0 will coredump on Solaris 2.7, 2.8 and 2.9.

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

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.

AmplifierS2DandP2D_prj default frequencies appear to be setinconsistently

The frequency options in the design circuit_level_amp_P2D_1_tone.dsn exampleproject BehavioralModels > AmplifierS2DandP2D_prj are set as follows:

28 Examples


Freq_Start=850 MHzFreq_Stop=850 MHzFreq_Step=1 GHz

This does not impede the performance of the circuit. The start and stop frequenciesare set to the same value to indicate that data needs to be extracted at a singlefrequency, (i.e., 850 MHz). Under this condition, the value of Freq_Step isdisregarded.

The reason for choosing a single frequency of extraction is to allow direct comparisonof the datasets, circuit_level_amp_P2D_1_tone.ds andbehavioral_level_amp_P2D_1_tone.ds

Although the extractor AmplifierP2D_Setup can collect data over a range offrequencies and input powers, the AmplifierP2D model is also capable of imitatingthe power response of one frequency, denoted by Freq, at a time. In this example, thecapability of the AmplifierP2D_Setup component is also restricted to allow directcomparison of the circuit and datamodel plots for the test amplifier that are provided.

You are encouraged to change Freq_Start, Freq_Stop and Freq_Step values onAmplifierP2D_Setup component to capture the behavior of other, preferablywideband, amplifier circuits. The AmplifierP2D datamodel component can then betuned via its Freq parameter to select the prefered operational frequency forvalidation.

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.

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.

DNL modeling is incorrect

The DSP example AtoDDtoA_prj illustrates the use of the ADC_Timed andDAC_Timed components. Both components include the DNL (DifferentialNon-Linearity) parameter. In this release, the DNL modeling is incorrect. If it is set

Examples 29


to a non-zero value on the schematic, ADS will set it to zero at the time of simulation.In this case, the following message will appear:

DNL is incorrectly modeled and will be forced to 0 for this release.

Eye parameter calculation functions included as ADS expressions

The Eye parameter calculation functions eye_rise_time, eye_fall_time, eye_amplitude,eye_closure, eye_height and cross_hist are included as ADS expressions. You are nolonger required to cut and paste these functions from Wireline Application Guide touser_defined_fun.ael files.

Wireline Application Guide documentation has changed

The wireline application guide documentation is updated. The updateddocumentation can be viewd from the ADS Schematic window DesignGuides >Wireline Application > Wireline Applications Overview.

Wireline Applications Guide installed automatically

The Wireline Applications Guide will be installed automatically upon installation ofRFIC examples and does not require a separate installation. All the design and datadisplay pages available under the Wireline Applications Guide can also be accessedfrom example project $HPEESOF_DIR/examples/RFIC/Wireline_Application_prj.

Radar Applications guide installed automatically

The Radar Applications Guide will be installed automatically upon installation ofCom_Sys examples. The Radar Applications Guide project is included as$HPEESOF_DIR/examples/Com_Sys/Radar_Applications_prj example project.

Loadpull Applications Guide installed automatically

The Loadpull Applications Guide will be installed automatically upon installation ofthe RF Board examples and does not require a separate installation. All of the designand data display pages available under the Loadpull Applications Guide can also beaccessed from the $HPEESOF_DIR/examples/RF_Board/LoadPull_prj exampleproject.

30 Examples


Example Search is case insensitive

Example search is not case sensitive. For example, searching for the word “Amplifier”will yield the same results as searching for the word “amplifier”.

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.

Momentum 31


Visualizing surface currents of existing projects

The Momentum manual 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 fromADS 1.1 and 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.

32 Momentum


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.

Note This condition only applies to Model Composer (Schematic window > Tools >Model Composer) and to Advanced Model Composer (Layout window > Momentum >Component > Advanced Model Composer).

Setting absolute limits for layout parameters

You cannot set an absolute upper or lower limit for layout parameters that aredefined for Momentum Layout Components. You should check to see whether or not aspecific value is physically meaningful.

Component updating does not work properly

In an ADS schematic, selecting Edit > Component > Edit Update ComponentDefinitions for designs containing Momentum Layout Components with modifieddefinitions may cause ADS to crash.

Workaround: Delete and re-insert the modified component in the schematic.

Can’t run Momentum simulations on Windows 2000 after installingJapanese Service Pack 3 for Windows 2000

If you attempt to run any Momentum simulations after installing Japanese ServicePack 3 for Windows when running ADS 2002 on Windows 2000 you will receive thefollowing error:

internal error -- segmentation violation

This problem is caused by a bug in Japanese Service Pack 3.

Workaround: If you are using ADS 2002C or an earlier version the only knownsolution is to uninstall Japanese Service Pack 3.

If you using ADS 2003A you can set an environment variable to disable the memorystatistics feature in Momentum.

1. Exit ADS

Momentum 33


2. Go to the directory HOME/hpeesof/config

3. Create a file named “momentum.cfg”

4. Edit the file and write the line:MOM3D_SWITCHOFF_MEMORYSTATISTICS=TRUE to be followed by“enter” on the next line.

5. Save the file

6. Restart ADS

This function is used is used to check the total memory usage so that it can be writtenin the Summary Window. After disabling this feature you will not be able to getmemory statistics in Momentum but the simulation will run.

Exporting ADS Designs

GDSII option will not work in previous versions of ADS

A GDSII file created when exporting ADS designs that contain rectangles using theoption “Rectangles as boxes” will not import into previous versions of ADS.

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.

Translator appends extra parentheses

The translator creates an SDD to simulate non-linear HSpice resistors. The In[1,0]noise equation inadvertently appends two extra “))” at the end of the equation.Simply remove the extra “))” from the translated netlist to fix the problem.

34 Exporting ADS Designs


New log file name for Netlist Translator

The log file name for the Netlist Translator has changed from spctoiff.log tonettrans.log. The Netlist Translator for SPICE and Spectre manual does not includethe new log file name.

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

Wireless Design LibrariesFor the wireless design libraries listed below, the standard ADS recommendedcomputer configurations are typically acceptable. However, when more complexsystems are simulated, the computer memory requirements may increase. 500 MBswap space on UNIX machines and a 300 MB paging file size on PC machines may berequired to run large designs.

• 3GPP W-CDMA

• TD-SCDMA

• WLAN

• 1XEV

• cdma2000

• DTV

• EDGE

• GSM

Improving performance of computationally intensive designs. End-to-end BER andBLER simulations involving thousands of bursts and including framing, encoding,multipath Rayleigh channel, bit synchronization, and equalization arecomputationally intensive. The platform of choice and simulation parameter settingsin the design can be optimized for improved performance in these cases.

Wireless Design Libraries 35


3GPP W-CDMA Design Library

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 isreleased to support 3GPP TDD (1.28 Mcps option).

This release has the following known problems.

• BS_Tx_SpurEmissions.dsn and UE_Tx_SpurEmissions.dsn need reference datafiles (.tim) in WCDMA3G_SignalSource_prj/data. The entireWCDMA3G_SignalSource_prj can be copied to the same directory level ofWCDMA3G_BS_Tx_prj or WCDMA3G_UE_Tx_prj (or both). After the signalsource designs have been modified and simulated, SpurEmission tests can thenbe made without any changes.

• For models that have the parameter DataPattern, there is a small problem ifDataPattern is set to UserFile. If blank lines appear at the end of UserFile, themodel will output the first point twice each time the waveform is repeated. Theworkaround is to remove blank lines at the end of UserFile.

• Under certain circumstances, model 3GPPFDD_Synch may not be able toachieve correct synchronization. As a result, some user configured 3GPP EVMand Code Domain Error measurements may not work properly. Thesemeasurements are performed using models 3GPPFDD_EVM and3GPPFDD_CodeDomainError. Each of these models use 3GPPFDD_Synch,which limits user defined EVM and Code Domain Error measurements. TheADS 2003A pre-configured 3GPP examples demonstrating 3GPP EVM andCode Domain Error measurements work properly and may be used to test otheruser RF designs.

Note The problem with the 3GPPFDD_Synch model and limitations in userdefined 3GPP EVM and Code Domain Error measurements will be fixed in anADS 2003A Hot Fix. To check the availabilty of this Hot Fix go to:http://eesof.tm.agilent.com/support/supp202.html

• In the newer 3GPP Technical Specification (March 2002 or later), a normalizingstep of factor sqrt(SF), where SF means Spreading Factor, has been added. Tobe compliant with the latest specification, a 10 x log(SF) dB can be subtractedfrom the simulation results.

36 Wireless Design Libraries


Design Kits

New environment variable for data file search path

There is a new environment variable in hpeesofsim.cfg which is the search path fordata files. To make use of this with design kits that contain simulation data files inthe circuit/data directory of the design kit, set the two variables below in$HOME/hpeesof/config/hpeesofsim.cfg.

DESIGN_KIT_DATA_PATH=<path to design kit>/circuit/data

SIM_FILE_PATH=.:..:../data:../networks:%DESIGN_KIT_DATA_PATH

Agilent Technologies recommends that the starting value of SIM_FILE_PATH iscopied from $HPEESOF_DIR/config/hpeesofsim.cfg. It is not necessary to restart thesoftware for this path to take effect. Resimulating the design will cause the file to beread.

Model Translation: New functions for Spectre/Hspice compatibility

There are a number of Spectre/Hspice compatibility functions that have been addedinto design kits so they can maintain their equations “as is” between differentsimulators. The simulator team at Agilent Technologies has now added some of thosefunctions into the simulator itself. If you have made your own compatibilityfunctions, you will need to remove those functions to work with ADS 2003A or RFDesign Environment, because they will now produce a redefinition error.

The functions implemented are:

asinh(x) - similar to arcsinh(x)

Purpose Returns the inverse or arc hyperbolic sine value of an integer, real or complexnumber.

Synopsis y=asinh(x)

Examples y=asinh(polar(1,0)) returns 0.881y=asinh(complex(1,-1)) returns 2.693/-113.207

atan(x) - similar to arctan

Purpose Returns the inverse tan, or arc tan of a integer or real number.

Design Kits 37


Synopsis y=atan(x)

Examples y=atan(1) returns 0.785

ceil(x)

Purpose Returns the ceil of an integer or real number.

Synopsis y=ceil(x)

Examples y=ceil(10.23) returns 11 y=ceil(-10.23) returns -10.0

fmod(x,y)

Purpose Returns the floating point modulo/remainder of a real number.

Synopsis z=fmod(x,y)

Examples fmod(1.23, 1.1) returns 0.13fmod(100.345, 34.6) returns 31.145fmod(-101.23, 20) returns -1.23

floor(x)

Purpose Returns the floor of an integer or real number.

Synopsis y=floor(x)

Examples floor(10.23) returns 10floor(-10.23) returns -11

hypot(x,y)

Purpose Returns the hypotenuse of an integer, real, or complex number.

Synopsis z=hypot(x,y)

Examples hypot(1,2) returns 2.236hypot(polar(1,2), polar(1,2)) returns 1.414/1.5

log10(x) - similar to log to base 10

Purpose Returns the log to base 10 of an integer, real, or complex number.

Synopsis y=log10(x)

Examples log10(10) returns 1.0log10(cmplx(2,1) returns 0.403/29.949

38 Design Kits


Additional information for “Merging an Encoded Library into a DesignKit” step 10

In Chapter 7 of the Design Kit Development documentation under Advanced Topics >The RF IP Encoder and Design Kits > Merging an Encoded Library into a Design Kit,step 10 should say:

10. Open your <design_kit_name>/de/ael/boot.ael file in a text editor and appendthe load statements provided at the bottom of the boot.ael file of your encoded library.These commands are used to load the circuit/ael files. You will also need to copy thefollowing path variable just before the appended load statements and assign it toyour design kit path variable.

decl <encoded lib path>_PATH = <design kit>_PATH;

Where <encoded lib path>_PATH is the path variable used in your load statements

and <design_kit>_PATH is the path variable used in your boot.ael file.

For more information on the boot.ael file, refer to Creating the boot.ael file.

Note You may also need to redefine your palette group ael files in order to displayyour encoded components in the design kit palette.

Instrument Server

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.

pow(x,y) - calculates x**y

Purpose Returns the power of x to y for an integer, real or complex number.

Synopsis z=pow(x,y)

Examples pow(4, 2) returns 16.0pow(cmplx(1,-1), cmplx(1,1)) returns 3.102/-25.143

Instrument Server 39


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.

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.

• 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

40 Printing/Plotting


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.

DeveloperStudio issues

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

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

DesignGuides 41


DeveloperStudio limitations not documented

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

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

Incorrect fundamental output power calculation in Power AmplifierDesignGuide

The following data displays in the Power Amplifier DesignGuide (ADS releases 1.5,2001, and 2002) improperly calculate fundamental output power:

• HB1ToneFPswp.dds

• HB1ToneFswp.dds

• HB1TonePAE.dds

• HB1TonePAE_Fswp.dds

• HB1TonePAE_Pswp.dds

• HB1TonePswp.dds

42 DesignGuides


These data displays all use the dBm() function, which allows you to enter animpedance “Zload” as the second argument. Unfortunately, in these data displays, theZload variable uses one too many indices. For example, dBm(Vload[1],Zload[0,0,0]) isused instead of dBm(Vload[1],Zload[0,0]). This makes the second argument of thedBm() function invalid and the impedance is replaced with its default value of 50Ohms. If you had set the load impedance to something other than 50 Ohms, anincorrect answer is given for the fundamental output power.

Workaround: To correct the problem in these data displays, reduce the number of 0'sin the index specification for Zload by 1, as shown above, within the dBm() function.

Note This DesignGuide was renamed “Amplifier” in the ADS 2002 release and theproblem has been fixed in ADS 2003A. However, if the data displays listed above arealready in your working directories, you must fix them manually.

IFM_CORR_modified.dsn generates connectivity error during simulation

In the Radar Application Guide, Single Tone Simulation of IFM circuit does notsimulate. This circuit IFM_CORR_modified.dsn is accessed fromRadar_Application_prj.

Workaround: To simulate this circuit, delete all the RF components and the envelopecontroller then add the IFM Correlator component available from the RadarApplication Guide.

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.

Search 43


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.

Documentation/Online Help

Connection Manager documentation not applicable

From an ADS 2003A window select Help > Topics and Index > Manuals >Components > Signal Processing Components. Under the Topics tab selectInstruments, the entry labeled Connection Manager is not applicable for this release;it is planned as an addon for 2003A.

44 Documentation/Online Help

Index
Numerics3GPPFDD EVN/PCDE
problem and hot fix 36

AAcyclic Loop Scheduler 21ADC_Timed component 20Amplifier DesignGuide 42arrow plots, information for surface currents 32auto-routing and connectivity 8

BBER

enhancing accuracy of value 28improving simulation performance 35incorrect values 29

BLER, improving simulation performance 35BSIM3SOI values 14BSIM4 values 15Budget analysis and Mixer components 14

CCDMA 2000 standards 28Cluster Loop Scheduler 21color differences 40color printing 40compatibility functions 37Connection Manager 44connections

maintaining during rerouting 8ControlSimulation parameter 20convergence

problems with HICUM 14problems with VBIC 15

copying library group information 7corrupted files 6crashes 23, 33custom HDLCosim component support 25CW tones display problem in sinks 16CxToTimed component 18

DDAC_Timed component 20data

inverted 20misread 11

deactivated ground 7debug mode on PC 10design kit environment variable 37design libraries, memory requirements 35DesignGuide issues 41, 42designs

invalid names 7memory issues on Windows 8opening in existing window 8

DeveloperStudio issues 41DF controller 21Diode model 14disk space 6DNL parameter 20, 29DSP target limitations 27DXF

importing 13

Eenvelope data, simulation problem with TimedSource17environment variable for design kits 37ESG_E4438C_Sink model (ADS 2002C) 23ESG4438CSink (ADS 2002) 23EVM

missing magnitude sequence 18missing phase error sequence 18value incorrect 28

expressions, setup information for UNIX 11extensions, writing to files 39

FFER, enhancing accuracy of value 28files

corruption on saving 6data misread 11delay in saving 7information lost in copying 7invalid design names 7not found message 28saving item definitions 7valid names 11

fill patterns 10FreqMultiplier component 17functions, simulator compatibility 37

Index-1

Ggauss function 34GDSII

exporting 34importing 13option 8

GPIB 22

HHDL cosim

component hangs in non-UI mode 27custom component support 25non-interactive cosim problem 26updating parameter values 25

HdlCosim component 26HICUM values 14HPGl/2 fonts 40

Iinstallation 23instrument interfaces 22Instrument Link models 22Instrument models 22Internet Explorer and search 43ISS cosim, error messages 27item definitions, saving changes 7iterated port support 18

Llayers, changing for ports 12Layout Components 33log file for Netlist Translator 35

Mmagnitude sequence missing in EVM 18Matrix data type 20memory issues on Windows 8mesh computation, precompute substrate error 31Mixer components and budget analysis 14MixerRF component 19ModelSim SE/EE 26Momentum

Layout Components 33stopping simulation on Solaris 31

MSK_Recovery component 20multidimensional data, reading problems 16multiple windows, preferences 8MultiplierRF component 19

Nnames, resolving conflicts 7Netlist Translator log file 35notebook pages, adding 12NumericExpression, simulation failure with undefinedparameter 17NumericSink component 18NumericSource component 20

Oonline help for subnetworks 41overflow percentage 19

Pparameter value updates 25parametric subcircuit 13PC, compiling user-defined models 13PER, incorrect values 29performance improvement 35phase error sequence missing in EVM 18pin numbers mismatched 8plots hang 23ports, changing layers 12Power Amplifier DesignGuide 42printers, installing on Solaris 40

Rreading units, errors in time domain 40real ports, initialization requirement for VHDL 25RFIC information access 35

SSave As command 7schedulers slow 21SDFRead component 19search using IE 43simulation

improving performance 35problem with complex envelope data 17problem with Diode model 14problem with undefined parameter 17recognizing deactivated ground 7reserved words 34running too slow 19stops abnormally 21

sink components 19, 20slot number setting 29Solaris

Index-2

installing printers 40stopping Momentum simulation 31

S-parameter and visualization issues 31SpectrumAnalyzer component 18SpectrumAnalyzer display problems 16stray processes, terminating manually 25subnetwork information 41substrate

error in mesh computation 31layer list discrepancies 32

surface current visualization information 32symbols 8

Ttarget limitations for ISS cosim 27TimedDataRead compnent 19TimedDataRead problems with multidimensional data16TimedExpression component 17TimedExpression, simulation failure with undefined pa-rameter 17TimedSource, simulation problem with complex enve-lope data 17TimeFile component 19TimeFile problems with multidimensional data 16Tk plots 23Transient results for BSIM4 15TrueType fonts 40

Uunarchiving files 6uninstalling 23UNIX setup information for expressions 11unsupported small data types 27user-defined models

compiling on PC 13

Vvariable values 19VBIC values 15visualization

density incorrect 31information for surface currents 32

VSA_89600_Sink model 23VxlCosim

problem with Solaris 27

Wwires

rerouting automatically 8

Index-3

Index-4

advanced design system 2003a release...

Documents