RF Design Environment 2003A. Release Notes

Transcription

1 RF Design Environment 2003A Release Notes May 2003

2 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 fitness for a particular purpose. Agilent Technologies shall not be liable for errors contained herein 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 available upon request from your Agilent Technologies representative. Restricted Rights Legend Use, duplication or disclosure by the U. S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS for DoD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR for other agencies. Agilent Technologies 395 Page Mill Road Palo Alto, CA U.S.A. Copyright , Agilent Technologies. All Rights Reserved. Acknowledgments Mentor Graphics is a trademark of Mentor Graphics Corporation in the U.S. and other 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

3 Contents RFDE 2003A Release Notes Installation... 5 Data Display... 6 Analog/RF Simulation... 6 Nonlinear Devices... 8 Examples... 9 Design Kits... 9 Instrument Server Printing/Plotting Search Index iii

4 iv

5 RFDE 2003A Release Notes This document describes known defects in RF Design Environment 2003A and, wherever possible, provides a workaround. It also identifies errors and omissions in the documentation. Version Date Revised/New Issue Title Inital Release 3/06/03 Web Release 4/21/03 Installation Installing RF Design Enviroment onto remote Solaris platform When installing RF Design Environment 2003A over a network onto a remote Solaris platform, do not use a remote X display on a local Linux or ReflectionX system. A segmentation fault may result if you use a browse button during the installation. This problem does not occur when installing via a remote X display on a local HP-UX system. Incorrect documentation for License Preference Too In Installation > Installation on UNIX Systems > Using RF Design Environment > Running RF Design Environment > Using the Agilent License Preference Tool, the name for the associated environment variable is incorrect. Please change the name in this and other locations where it appears in the documentation. Change the environment variable name from: AGILEESOFD_LICENSE_PREFERENCE to AGILEESOFD_LICPREF_<hostname> where hostname is the name of the machine on which RFDE is running. Installation 5

6 Data Display RFDE Snapshot mode must be enabled from CIW input line The RFDE Snapshot mode is not enabled when an RFDE session starts. If you try to take a snapshot during a simulation, you may notice the following message in the CIW: *Error* fprintf/sprintf: format spec. incompatible with data -nil You can start RFDE Snapshot mode manually each time an RFDE session starts. After starting an RFDE session, enter the following command in the CIW input line: rfdesnapshottimeout(900) You must enter this command each time an RFDE session starts. You can tell when an RFDE session starts when you see a statement in the CIW similar to this: RFDE<MP>: RF Design Environment (*) <revision> <date> Invoking RFDE Snapshot mode may cause loss of data If you invoke the RFDE Snapshot mode just when the simulation is finishing up, a GEMX error may occur. All data from this simulation will be lost. You will need to rerun this simulation. 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 and not 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. Analog/RF Simulation ParamSweep component cannot sweep temperature Do not use the Ptolemy ParamSweep component to sweep temperature (temp) when using cosimulation or fast cosimulation modes. It does not sweep temp correctly. 6 Data Display

7 Use analoglib s port component in place of ADS Term component The Term component in ADS is used for measuring S-parameters; it is not provided in RFDE because the Cadence analoglib port component has the same functionality. Please use the port component in RFDE with a blank source type. Revised information for S-parameter file devices in analoglib In the analoglib Components manual, in Sources > Using S-parameter File Devices from analoglib, change the following configuration variable names in the fourth paragraph: Change SIM_FILE_PATH= to SIM_FILE_PATH Change SIMILATION_DATA_PATH to SIM_FILE_PATH Using ppar with the transmission line substrate parameter When using RFDE with Cadence version 4.4.6, it is possible to pass certain string values into a subcircuit and use them on a component; however, Cadence version does not support this. This applies to the Subst parameter on adslib components such as in the microstrip and multilayer transmission line categories. For this, use the ppar function as described in the Cadence documentation. (Note that the ppar function works with numeric-valued parameters in both versions of Cadence. Also, note that the ppar function cannot be used to pass the model parameter of diodes and transistors.) Incorrect documentation about GlobalNode In Simulation > Circuit Simulation > Preparing a Circuit for Simulation > Naming Nodes, 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 maintain the same identity throughout the entire hierarchy of designs. In other words, the nodes with the same name as the global node name in other designs are all electrically connected. This facilitates the interconnection of boards, IC chips, and connectors. Analog/RF Simulation 7

8 Device pin currents for pins of a connected device redundantly saved in data set Device pin currents for the pins of a connected device device connected are saved redundantly in the data set. Disregard the redundant pin current that are saved this way. Saving device pin currents at NestLevel=0 also saves currents at other levels When saving device pin currents at the top hierarcical level (setting NestLevel=0 in the Save Options form), currents at other levels are also saved for some simulation types. Disregard the currents at other levels. Selected sub circuit currents at levels 1 and below not saved Selecting sub-circuit at levels other than the top level and saving device pin currents does not work. The workaround is: 1. Open the Save Options dialog-box (session window > Outputs > Save Options...) 2. Under Pin Currents turn on "Use NestLevel" Doing a simulation will now save the pin currents at the sub-circuit level. Nonlinear Devices Setting values for HICUM The default values for HICUM have changed from those in the current documentation, and the default parameter values reflect these changes. Setting Rbi0=0 produces the wrong results in small signal AC simulations. You need to set Rbi0>0 or leave it blank. Convergence problems may occur in Transient and Harmonic Balance when self heating is on and the device is dissipating large amounts of power. Either turn off 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. 8 Analog/RF Simulation

9 Convergence problems with VBIC Convergence problems may occur in Transient and Harmonic Balance when self heating is on and the device is dissipating large amounts of power. Either turn off self-heating (Rth=Cth=0) or try sweeping the source power levels. Transient results for BSIM4 Transient results may differ from UCB spice3 results. Examples Modifications required for the Corners Analysis example The Corners Analysis example found in examples_rfde/corner requires the following modifications: The scale factors for two design parameters, Cseries and Lshunt, are not set properly. There should be no space between the number and the scale factor. For example, 2 pf should be set to 2pF. On doing a corner analysis without this correction, an error will be printed to the CIW window. This error does not prevent the simulation from running corner analysis. To correct this error edit the design parameter from the RFDE simulation dialog-box and save the state. The initial path for the model file is incorrectly hard-coded to an internal path. This causes and error when doing a simulation from the RFDE simulation window. However, this error does not occur during a Corner Analysis, since the model paths are overwritten with information from the corner under simulation. To correct this condition, edit the model path and set it to the directory where the models are. For example, if the corner analysis example is installed in examples_rfde/corner, then set the model path to $HPEESOF_DIR/examples_rfde/corner/corner/CORNERS/bjtlib/npn34Mod Lib.net. After the setting the correct path for npn37modlib.net, save the state. Design Kits New environment variable for data file search path There is a new environment variable in hpeesofsim.cfg which is the search path for data files. To make use of this with design kits that contain simulation data files in Examples 9

10 the 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 is copied from $HPEESOF_DIR/config/hpeesofsim.cfg. It is not necessary to restart the software for this path to take effect. Resimulating the design will cause the file to be read. Model Translation: New functions for Spectre/Hspice compatibility There are a number of Spectre/Hspice compatibility functions that have been added into design kits so they can maintain their equations as is between different simulators. The simulator team at Agilent Technologies has now added some of those functions into the simulator itself. If you have made your own compatibility functions, you will need to remove those functions to work with ADS 2003A or RF Design 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 complex number. Synopsis y=asinh(x) Examples y=asinh(polar(1,0)) returns y=asinh(complex(1,-1)) returns 2.693/ atan(x) - similar to arctan Purpose Returns the inverse tan, or arc tan of a integer or real number. Synopsis y=atan(x) Examples y=atan(1) returns ceil(x) Purpose Returns the ceil of an integer or real number. 10 Design Kits

11 Synopsis y=ceil(x) Examples y=ceil(10.23) returns 11 y=ceil(-10.23) returns 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.13 fmod( , 34.6) returns fmod( , 20) returns floor(x) Purpose Returns the floor of an integer or real number. Synopsis y=floor(x) Examples floor(10.23) returns 10 floor(-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 hypot(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.0 log10(cmplx(2,1) returns 0.403/ 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.0 pow(cmplx(1,-1), cmplx(1,1)) returns 3.102/ Design Kits 11

12 Instrument Server Problem with datasets using.ds extension The instrument server does not overwrite existing dataset data blocks, thus a unique blockname is required for every read of an instrument or file. You will receive an error message reporting the need for a unique blockname; however, on Win2000, ADS may hang if you close the Instrument Server immediately after receiving this error message. Printing/Plotting Color images printed in black and white Xprinter cannot print color graphics saved as EPS, PCL4, or PCL5 files. Try printing directly 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 UNIX installations using Xprinter if the PCL Cartridge driver is selected. The colors in the hardcopy produced using this driver do not match those displayed on the monitor. Use the Color LaserJet PS driver when generating color hardcopy or print in monochrome. HPGL/2 output and TrueType fonts If your design contains any TrueType fonts and you print to file using the HPGL/2 format, your text will be lost. To preserve it, convert it to HersheyRomanNarrow as follows: Component Text Choose Select > Select All. Choose Edit > Component > Component Text Attributes. Select HersheyRomanNarrow from the Font type drop-down list and click OK. Other Text Choose Select > Select All. Choose Edit > Edit Text. Select HersheyRomanNarrow from the Font Type drop-down list and click OK. 12 Instrument Server

13 Installing printers on Solaris8 To install a printer you need read and write permission for your $HOME/.Xprinterdefaults file. (The Install documentation incorrectly identifies this as the.xpdefaults file.) For read and write permissions, type chmod 777 $HOME/.Xprinterdefaults Search Partial word queries Using a partial word for a query entry could prevent the search engine from finding any matches. For example, when you perform a query, use a complete term such as hpeesofsim because no matches will be found for eesofsim. Search 13

14 14 Search

15 Index A analoglib configuration variables 7 port component 7 S-parameter file devices 7 B BSIM3SOI values 8 BSIM4 values 9 C color differences 12 color printing 12 compatibility functions 10 convergence problems with HICUM 8 problems with VBIC 9 installing printers 13 string values in subcircuits 7 T Term component 7 Transient results for BSIM4 9 TrueType fonts 12 V VBIC values 9 D data lost 6 misread 6 design kit environment variable 9 E environment variable for design kits 9 extensions, writing to files 12 F files data misread 6 valid names 6 functions, simulator compatibility 10 H HICUM values 8 HPGl/2 fonts 12 P port component 7 ppar function 7 printers, installing on Solaris 13 S Snapshot mode 6 Solaris Index-1

16 Index-2