Here’s the page we think you wanted. See search results instead:

 

  

Main Support:       Knowledge Center
Documentation:   Genesys English Doc   >  genesys201403   >  Genesys 2014_03 Release Notes

This document contains references to Agilent Technologies. Agilent's former Test and Measurement business has become Keysight Technologies. For more information, go to www.keysight.com.


Skip to end of metadata
Go to start of metadata

You should be logged in the space to access Genesys 2014.03 documents and links to more detailed information. Please login using your Knowledge Center login credentials.

Genesys Release Notes

Release Highlights: Spectrasys Modulated RF

Spectrasys has now the ability to call and use the SystemVue dataflow time domain simulation engine. An RF behavioral model is extracted from the Spectrasys design that gets passed to the SystemVue Engine along with modulation parameters specified in the Multisource and system analysis path. The modulated RF simulation runs behind the scenes and simulation results are imported back into the Spectrasys workspace where the user can plot time domain results. Some of these measurements are the actual modulation spectrum, modulation constellation, ACPR, and EVM. Spectrasys has the ability to estimate EVM, BER, and ACPR in the frequency domain.

The supported modulation formats are:

  • BPSK, QPSK, 8PSK, 16PSK, 16-QAM, 32-QAM, 64-QAM, 128-QAM, 256-QAM, 512-QAM, 1024-QAM
  • WLAN-11ac 1
  • LTE-Uplink 1
  • LTE-Downlink 1

1 - These modulation formats have some restrictions on the types of parameters that a user can control.

See  Modulated RF for additional information.

New Modulated RF Examples

  • ACPR Estimation.wsg
  • BER Estimation Validation.wsg
  • EVM Basic Estimation.wsg
  • LTE Uplink Receiver.wsg
  • Receiver CoSimulation BER.wsg
  • TX Hybrid Amp Initial.wsg
  • WLAN 11ac Simulation.wsg

Tutorial Videos

The following new digital modulation tutorial videos have been created:

  • ACPR_Estimation
  • BER_Estimation
  • EVM_Estimation
  • Modulated_RF_Basics
  • WLAN_Modulation
  • MultiCarrier_Modulated_RF

Release Highlights: S/Filter

S/Filter has now been integrated into the workspace. This means that each workspace can contain multiple S/Filter designs (S/Filter synthesis objects). Furthermore, the S/Filter design is loaded and saved with the workspace. The S/Filter behavior is now very similar to existing synthesis tools. Several transforms are corrected, especially those that are related to distributed filters. Several improvements have been made in usability and stability.

The operations performed in the S/Filter synthesis will modify the associated schematic. If you want to manually modify the synthesized schematic, copy it to a different schematic first before performing any additional S/Filter synthesis operations.

Issues Resolved

  • Fixed several crashes in S/Filter.
  • Fixed some issues in dialog boxes.
  • Fixed stuck error messages.
  • Fixed potential negative index in an array.
  • Fixed recommended and calculated values in some transforms.
  • Fixed quarter wavelength error when using lumped element designs.
  • Changed functionality so that max solutions are shown when “Specify Permutations” is unchecked.
  • Fixed inaccurate transforms with multiple components.
  • Improved graying at various locations on the dialog box.
  • Added information in the Inverter Parts documentation.

New S/Filter Examples

  • Allpole BP.wsg
  • Customized BP.wsg
  • Diplexer.wsg
  • Distributed Edge Coupled.wsg
  • Inexact Extractions.wsg
  • LP with FTZ.wsg
  • Norton Transforms.wsg
  • Realizing Distributed LP.wsg
  • Resonator with FTZs.wsg

Tutorial Videos

The following new S/Filter tutorial video has been created:

  • SFilter_Diplexer
  • SFilter_Edge_Coupled_Filter

Release Highlights: Avago X-Parameter Models

Avago components have been provided with required X-Parameter data files in the form of Avago X parameter library. Using the provided X-Parameter files, you can perform non-linear simulations in Genesys. To learn more about using these parameters, watch the X Parameter Library video available in your Genesys installation. Here is the list of Avago components:

Part Number

Category

MGA-633P8

Amplifiers

MGA-634P8

Amplifiers

MGA-635P8

Amplifiers

MGA-636P8

Amplifiers

MGA-637P8

Amplifiers

MGA-638P8

Amplifiers

MGA-53543

Amplifiers

MGA-545P8

Amplifiers

MGA-565P8

Amplifiers

MGA-61563

Amplifiers

MGA-62563

Amplifiers

MGA-665P8

Amplifiers

MGA-425P8

Amplifiers

MGA-52543

Amplifiers

ADA-4789

Amplifiers

ABA-54563

Amplifiers

MGA-81563

Amplifiers

MGA-82563

Amplifiers

ATF-50189

Transistors

ATF-52189

Transistors

ATF-53189

Transistors

ATF-501P8

Transistors

ATF-511P8

Transistors

ATF-521P8

Transistors

ATF-531P8

Transistors

ATF-54143

Transistors

ATF-55143

Transistors

ATF-58143

Transistors

ATF-541M4

Transistors

ATF-551M4

Transistors

VMMK-1218

Transistors

VMMK-1225

Transistors

These components are available in the Avago XP Parts library. They are extracted with 1-Tone X-Parameter files. Note that you must download the X-parameter files and install them at the standard location. These files are provided as self-extracting zip files. Refer to Using X-Parameter Libraries for detailed instructions on how to download and install the X parameter library.

Release Highlights: MATLAB® Script

Math Language is obsoleted and replaced by MATLAB® Script (see MATLAB® Script ).

The following list documents the features inMATLAB®ScriptTMthat are not supported in this Genesys release or behave differently compared to Math Language in the previous releases:

  • MATLAB®ScriptTMequation debugger is not supported

  • MATLAB®ScriptTMauto-completion is not supported

  • getunits and setunits have been renamed to getdisplayunit and setdisplayunit
  • Tuning variable syntax =? has been changed to tune
  • dbg_print and dbg_showvar functions are not supported

  • isstring is obsoleted inMATLAB®ScriptTM

  • Structures and classes can be created and used within aMATLAB®ScriptTMequation, but cannot be transferred to Workspace Variables or Design Variables as output variables

  • The using function performs relatively slow
  • The exist function has different arguments comparing to previous versions.
  • When using runanalysisin aMATLAB®ScriptTMworkspace tree equation, the design equation of the corresponding schematic needs to use Engineering Langauge.

  • Expressions inMATLAB®ScriptTMequation block without output suppression (semicolon ;) do not generate output in the command prompt. However, it is still recommended to use semicolon at the end of expression lines for performance reason.

  • Unsigned 16-bit integer arrays were interpreted as strings by Math Language, which is not compatible withMATLAB®ScriptTM. For example, the script below works for Math Language but will error out inMATLAB®ScriptTM, with the error message "Error using str2num, requires string or character array input."
    aBytecnt = fread( t, 1, 'uchar=>ushort'); %t is a TCPIP object
    tTotal = str2num( aBytecnt ); %aBytecnt is an unsigned 16bit integer
    To make this work inMATLAB®ScriptTM, change the second line as shown below:
    aBytecnt = fread( t, 1, 'uchar=>ushort');
    tTotal = str2num( char(aBytecnt’) );

Release Highlights: Use Model Update to Equations and Variable Viewers

The use model of equations has been updated to more closely align with the MATLAB® use model.  

Workspace tree equations now behave like scripts. The variables defined in them have workspace-wide scope (no matter where in the workspace hierarchy the equation is located) and so they can be used anywhere in the workspace (other tree equations, schematics, design equations, graphs, tables). Workspace tree equation variables are shown in the Workspace Variables viewer.

A global Command Prompt is now available for equation scripting. The Command Prompt can access all Workspace Variables. The results of command prompt expressions execution are shown immediately in the Command Prompt as well as in the Workspace Variables viewer.

In previous Genesys releases, a workspace tree equation window contained an equation script editor, a variable viewer showing the variables defined in the equations, and a command prompt. Now a workspace tree equation window is just an equation script editor. Variables created from a workspace tree equation are now shown in the Workspace Variables viewer. The global Command Prompt replaces the local equation window ones compared to the previous Genesys releases.

Similarly, a design equation window is now just an equation editor for the design. Design parameters (defined in the Parameters tab of a design) and variables created in a design equation are now shown in the Design Variables viewer. The Design Variables viewer displays the variables of the design that is currently in focus (active window) or the design that was last in focus (if the current active window is not a design).

A design has its own Design Variables scope; the Design Variables (including design parameters and the variables defined in the design equation) are only accessible within the design. The design variables are automatically cleared before the design equation is evaluated.

Specifically for for the MATLAB® Script language, a function object is provided to define a MATLAB® Script function. A workspace tree equation or a design equation that uses MATLAB® Script can only define a script, but no functions. Note that the use model of defining and using a function in Engineering Language remains the same as in the previous Genesys releases. For more details, refer to Using Equations and Functions in a Workspace.

If multiple workspaces are opened at the same time using the same instance of Genesys and these workspaces contain different definitions of the sameMATLAB®ScriptTMfunction, the behavior is undefined due to function name conflict. In this case, do not allow multiple open workspaces (Tools > Options > General) and reopen the workspace that you are interested in.

Workspace Variables resolve an ambiguous situation where multiple workspace tree equations can define the same variable with different values. In previous release, the variable that is going to be used during an evaluation is undefined (assuming the equations that define the same variable are in scope). Now, the variable value is uniquely defined by the last equation that evaluates it and the value is displayed in the Workspace Variables viewer. The tooltip and "Go to definition" context menu can also be used to identify which equation defined the workspace variable.

Here are the tips specifically related to the equation use model update. Refer to Tips for Effective Equation Writing for more details.

  1. Ensure that the input and output equations are in separate blocks to prevent circular dependencies.
  2. Because workspace tree equations share the same Workspace Variables scope, be aware of variable redefinition, especially when it is redefined unintentionally. If it is desirable to define the same workspace variable in different workspace tree equations, consider turning off Auto-calculate for these workspace tree equations and control their execution manually. If the intent is to define different variable values for different designs, it is recommended to use design equations instead of using multiple workspace tree equations. If the intent is to use multiple workspace tree equations for post processing, make sure the result variables use different names so they can be compared and plotted together.
  3. It is no longer recommended to put "clear" at the top of a MATLAB® Script equation. Workspace tree equations share the same Workspace Variables scope. Putting "clear" at the top of a workspace tree equation is going to clear ALL workspace variables, including the ones defined in other workspace tree equations. Since design variables are always cleared before a design equation is evaluated, there is no need to put "clear" at the top of a MATLAB® Script design equation.

A new tutorial video, Equations_EngLang_and_MATLAB_Script, is created for introducing the new equation use model.

Release Highlights: Use Model Update to Parameter Evaluation and Units

The use model of how a part parameter is evaluated has been updated in order to resolve the confusion between "Use MKS" and "Use Display" in previous releases. "Use MKS" and "Use Display" options (provided at the top of the variable viewer frame of an equation window) have been removed from the product. In this release, when a part parameter has units and a variable (or an expression) is used to set its value, the following rules are used for parameter evaluation:

  • If the variable (or the result of the expression) does not have an associated unit, the unit of the part parameter is applied to the value. For example, suppose a variable "var" is 100, and suppose the parameter Value is set to "var" and the parameter Units is set to MHz, the resulting parameter value is 100 MHz (100e6).
  • If the variable (or the result of the expression) has an associated unit, the parameter value is simply the MKS value of the variable and the parameter Units is not used to interpret the parameter value (in this case, the parameter unit selected is used ONLY for display purposes, e.g. to show the parameter value on the schematic). For example, suppose a variable "var" is 100 Hz (MKS value 100 with display unit Hz), and suppose the parameter Value is set to "var" and the parameter Units is set to MHz, the resulting parameter value is 100 Hz (MKS value 100) and is displayed as 100e-6 MHz.

Refer to Using Variables or Design Parameters to Set Part Parameters for more details.

Release Highlights: Workspace Extension Change to .wsg

The workspace file format has been changed to improve file integrity due to all backward incompatible use model changes made in this release. The new file format is incompatible with prior versions. To distinguish the workspace file versions the workspace extension has been changed to wsg. When loading *.wsx files, they are automatically converted to the new file format and when saved they are saved with the new wsg extension. The original workspace is not modified unless you explicitly overwrite it.

Hint

When an old format workspace is loaded and converted you will see an Information message in the Errors window notifying you that a conversion has happened.

If there are any errors encountered during the conversion, a Conversion_Errors note object is created on the workspace tree; this note contains details about the conversion errors encountered.

Converting from a new *.wsg workspace to an old *.wsx workspace is NOT supported.

When loading old XML libraries, such as Design, Part, Equation libraries, a dialog box is automatically prompted to convert the old XML library to the new format. You will need to provide a name for the new library and the converted library will be automatically loaded. The old libraries remain unchanged so you can still load them in previous versions. You can also run the conversion tool (see below) outside the product to convert your XML libraries to the new format.

A command line utility program, WorkspaceConversionTool.exe, is provided to convert multiple workspaces and XML libraries in a directory. The workspace conversion tool can be found in: <Genesys_Install_Directory>\bin directory.

Usage: WorkspaceConversionTool.exe "SourcePath" "DestinationPath".

For example:

WorkspaceConversionTool.exe C:\tmp\source_directory C:\tmp\destination_directory
WorkspaceConversionTool.exe C:\tmp\source_directory\workspace1.wsx C:\tmp\destination_directory\workspace1.wsg

When converting a directory, all workspaces and XML library files in the source directory and any of its sub-directories are converted to the destination directory. Non-workspace files in the source directory are copied to the destination directory.

The workspace conversion tool converts the following items to match the new use model in the current product:

  1. Convert part parameter units and equations, if necessary, to preserve the same results with the new use model of parameter evaluation. See Use Model Update to Parameter Evaluation and Units.
    1. If a part parameter value is set to a variable (or an expression using a variable) and the variable is defined in a "Use MKS" equation and the variable does not have an associated unit in the original workspace, the part parameter unit will be set to the MKS version of that unit category (for example, from MHz to Hz).
      • If it is not desirable to change part parameter unit, there is a command line option, -ScaleEquationText, in the workspace conversion tool to associate MKS display unit with the variable at the end of the equation that defines the variable. For example,
        WorkspaceConversionTool.exe C:\tmp\source_directory\workspace1.wsx C:\tmp\destination_directory\workspace1.wsg -ScaleEquationText
    2. If a design equation is set to "Use Display" and there are design parameters that have associated units, additional lines will be inserted at the top of the design equation to strip out design parameter units and adjust design parameter values such that the design behaves the same as before.
  2. Convert workspace tree Equation object that defines a Math Language function to a workspace tree Function object that defines a MATLAB® Script function. The workspace conversion tool only handles the case where the first valid line in the original equation defines a function. If an equation block defines multiple functions, then only the first function will be converted to a function object. The other function(s) will exist only in the local scope of the converted function.

  3. Convert setunits and getunits in Math Language to setdisplayunit and getdisplayunit in MATLAB® Script. It also converts the old unit specification in setunits to the new unit specification in setdisplayunit.

  4. Convert tuning syntax =? in Math Language to tune in MATLAB® Script.
  5. If there is a "clear" function call at the top of a MATLAB® Script equation, the line will be commented out because it is no longer recommended to do so in the current version. Workspace tree equations share the same Workspace Variables. Putting "clear" at the top of a workspace tree equation is going to clear all workspace variables, including the ones defined in other workspace tree equations. Since design variables are always cleared before a design equation is evaluated, there is no need to put "clear" at the top of a MATLAB® Script design equation.

The workspace conversion cannot preserve the behavior for the following cases and will report conversion errors after loading the converted workspace.

  1. If there are duplicated variables defined in multiple tree equations in the original workspace, only one of them will be displayed in the Workspace Variables viewer. See Use Model Update to Equations and Variable Viewers.
  2. If there is a variable defined in a workspace tree equation that "Use Display" and the variable is associated with a unit (for example, through setunits or coming from a dataset) and the variable is used to set a part parameter, the behavior could be different than the previous release.
  3. If an equation should be converted to a MATLAB® Script™ function object, but the function name is already in use by another workspace tree object then the function object will not be created. The equation object cannot be renamed to another workspace tree object with the same name.

 

Release Highlights: Licensing

  • Genesys 2014.03 requires: a) version 2014.01 of the EEsof EDA licensing software and b) version 3.1 codewords to run.
  • A real-time and systematic license setup troubleshooting utility is added to the License Manager tool’s Diagnose tab. This utility also produces a detailed health report of the configuration.
  • Genesys does not automatically release licenses after checking out. In Genesys 2014.03, there is a new menu button Action > Release All Simulation Licenses for users to manually release all checked out simulation licenses.

Product Improvements and Updates

General

  • When dragging a schematic from the workspace tree to the another schematic the default schematic symbol is an automatically generated symbol that labels the sub-circuit port names on the schematic symbol. This will replace the generic N-Port symbol where all ports are located on the bottom of the symbol.
  • Annotation Text now supports equation expression macros, using %=statement=% syntax
  • Annotation Picture now allows .png files and uses relative paths to the image (so you can share the images associated with your workspaces).
  • Steps discos have improved performance

3D Viewer

  • Upgraded to newest 3D viewer code. Several defects have been addressed.

Momentum

  • Upgraded to the latest ADS2013.08 Momentum code. Several defects have been addressed.
  • Supports conductor permeability (ferrite conductors)
  • Far fields for multiple frequencies
  • Improved overlap extraction and mesh reduction around vias provides more accurate results when mesh reduction is on. Lower mesh densities can be used versus previous releases.
  • The direct compressed matrix solver computes matrix elements more accurately to minimize the differences with the solution of a direct dense solve.
  • Memory reports are now based on usage of physical rather than virtual memory.
  • Microwave mode simulations no longer produce 3 sets of duplicated S-parameter data (S+PortZ, S_50 and S_Z0+Z0) when the reference impedances are all equal. This reduces the result file sizes
  • Added Strip Model settings to Momentum analysis properties Simulation Options tab, defining "default" value of the Metal Layer strip model in Layout options Layer tab.

     

      New Strip Model settings added to Momentum Analysis changed Layout "default" Strip Model setting. Starting from Genesys 2014.03 the value is defined in Momentum Analysis properties Simulation Options tab, when in earlier Genesys versions the value related to Momentum Engine default for the strip model = 2D (planar model).

EECAD

  • Upgraded to latest ADS EECAD code. Several defects have been addressed.

Sweep, Monte Carlo, Optimization and Yield

  • When running sweep, Monte Carlo, optimization, and yield analyses, the tune variable values will be updated internally during simulation but will not be updated on the GUI (including tune window, equations, and schematics) until the evaluation finishes. The results of each iteration will be reflected on the GUI if they are displayed in graphs, tables or datasets.

Optimization

  • After optimization is completed or stopped, the best tune variable values found during the optimization will be updated to the tune window, equations, and schematics. During the optimization, the tune window, equations, and schematics will NOT redraw; only graphs and tables are updated during the optimization.
  • Disabled adaptive stepping for Momentum and Empower Optimization which caused false optimizations stops (with optimization error=0). This occurred when the goal function at some adaptive optimization steps does not have data points needed for optimization.
  • Added warning, if the optimization ended because of the goal data doesn't have points for optimization (for example, in case of narrow-band filter optimization, if simulation data points missed the narrow-band area).

Layout / Footprints

  • Library files used for layout (footprints, board layer, and component footprint mapping table files) can now be loaded and saved from a user specified location. This is set in the global options (Tools > Options > Directories) User Library Files. When a new directory is selected all library files in the current location are copied to the new directory location. After installation this directory default to C:\Program Files\Genesysxxxx.xx\Lib. If the location of these files was changed to C:\My Documents\My Genesys Libs\ then all the files in C:\Program Files\Genesysxxxx.xx\Lib would be copied to C:\My Documents\My Genesys Libs\ with next restrictions:
    • Only newer files will be copied from previous defined to the new library folder
    • No files will be copied to Genesys installation library folder after changing the library path from user defined to Genesys installation folder C:\Program Files\Genesysxxxx.xx\Lib : the installation folder always keeps original versions of the Genesys libraries

Spectrasys

Frequency Comb Source and Intermods from a Large Number of Carriers

You can now simulate nonlinear responses to hundreds of RF carriers with an innovative patent pending simulation technique. Traditionally, industries using many RF carriers, like TV, use simplified equations to predict nonlinear performance limited to in-band interference only. This new technique is fast and covers both in-band and out-of-band distortion simulation. You can now simulate hundreds of carriers and derived intermods.

For more information, see Frequency Comb Carrier and Intermods

Residual Phase Noise

Several active devices now support residual phase noise. This noise is additive phase noise that is added non-coherently with any input phase noise. The models that support residual phase noise are:

RF Non Linear Models Accuracy Enhanced

Non-linear models (Amplifiers, Mixers, and Non Linear Blocks) in Spectrasys have been enhanced to provide better overall accuracy. The compression curve is now modeled using a 9th order Volterra polynomial, extracted from 1st and 2nd order compression curves. Higher order intermod products are generated due to the higher order polynomial. The maximum order displayed to the user is controlled by the Maximum Order parameter on the Calculate Tab of the System Analysis. If the simulation of an existing workspace takes a significantly longer time to simulate it may be because the Maximum Order parameter is set to an order higher than 3 and so simulation time will increase due to the new accuracy implementation.

You can turn on/off Volterra Model by checking/unchecking the "Use Volterra Model" check box in the Calculate tab in System Analysis.

Convergence and Part Calculation Order Enhanced

Larger schematics now converge faster due to a part calculation sequencer that orders the calculations of parts in a way to optimize speed and improves convergence issues. The order of parts being calculated is specified in the simulation log.

RF Amplifier Model Changes

Obsoleted parameters: The corner frequency and frequency rolloff slope parameters have been eliminated from the RF amplifiers. The implementation of these parameters was ideal and did not relate very well to the real-world simulation problems. A recommended implementation is to create a user model with the amplifier followed by an appropriate filter response, such as a low pass filter. A new example called ‘Amplifier with Rolloff.wsg’ has been included to show how to implement filtering functions with user models.

Antenna Noise Temperature, Phase Noise and other Noise-related Enhancements

  • Antenna noise temperature can now be simulated for temperatures other than 290K. The MultiSource model is used to generate the antenna noise at a value specified by the user.
  • Cascaded Noise Figure calculation equations have been reformulated to support antenna noise and properly accounts for phase noise at the path input. The associated documentation has also been improved.
  • Output ports no longer generate noise. This removes dual noise spectrums that appear on spectrum plots at the output.
  • Mixer input and LO phase noise are now added coherently if the input and LO phase noise are locked to the same reference clock. Previously, the coherency was determined solely by the parent spectrum. As the parent input and LO spectrum are generally not at the same frequency, these spectrums were rarely coherent.
  • Phase noise accuracy has been improved when using a master reference clock
  • Coherent phase noise addition and subtraction is now support for all intermod combinations at the mixer output

New Power Dependent Attenuator Model

This model adjusts its gain based on the total input power into the model. User entered parameters control the dynamic range of the part, threshold, reverse isolation, and step resolution. The device can be configured to model continuously variable attenuators (analog) and digitally stepped attenuators. A new example called, 'AGC Using Power Dependent Atten.wsg' shows how to use this model.

Multisource Model Updates

The Multisource now supports a Frequency Comb source as well as Digital Modulation sources if the RF Modulation Analysis feature has been purchased. The Multisource will now allow users the ability to mark a signal as an undesired signal. This gives users the ability to create interfering signals from the same Multisource where desired signals are created.

Nonlinear Switch Updates

The nonlinear switch models now support more parameters so that signals appearing at other switch pins can be used to generate intermods.

Other RF Architecture Enhancements

  • Level diagrams can now display schematic symbols in subcircuits. The number of display levels is set in the system analysis.
  • The usability of the Envelope Source used in the MultiSource has been improved. The Envelope Source dialog box has been updated to be more friendly and intuitive. The documentation has also been improved. See Envelope Source Definition for additional information.
  • Three new measurements have been created for image noise. They are image noise frequency and power measurements for signal and noise for every image frequency in the system (IMGF_ALL, IMGCP_ALL, and INGNP_ALL). Existing measurements only consider 1 image frequency even for multiple mixers. Now all image frequencies can be analyzed.
  • Monte Carlo Spectrum Enhancements: Plotting the spectrum from a Monte Carlo run has been enhanced to show spectrum identification for each Monte Carlo setting during the run.

Status Display / Simulation Log Enhancements

The status display and simulation log have been enhanced to better identify which simulation step is being performed.

New Measurements

  • ACPR - Adjacent Channel Power Relative
  • IMGF_ALL - Frequencies for All Images in the System
  • IMGNP_ALL - Noise Channel Power for All Image Frequencies
  • IMGP_ALL - Image Power for All Image Frequencies
  • UDCP - Undesired Channel Power

New RF Architecture Examples

  • AGC Using Power Dependent Atten
  • Amp Mixer Cascaded IP3.wsg
  • Amplifier with Rolloff.wsg
  • Antenna Noise Temperature.wsg
  • Envelope Source Extraction.wsg
  • Phase Noise and Ref Clock.wsg
  • Phase Noise and Noise Figure.wsg
  • RF Amp Residual Phase Noise.wsg
  • Simple CATV Amplifier.wsg
  • Switch Intermods.wsg
  • Two Tone Correlation.wsg
  • Transfer Switch.wsg

Documentation Improvements

  • Spectrasys Cascaded Noise Figure
  • Spectrasys Filter Models
  • Spectrasys Mixer Models

Obsolete Features

Voltage Based Behavioral Models

Voltage based behavioral models have been obsoleted.

Old .wsp and .sch Workspace File Formats

The .wsp and .sch workspace file formats (which are over 10 years old) are not supported anymore. To load an old workspace, you must first load it in Genesys 2012.01 and save it as a .wsx file and load that into Genesys 2014.03. If you don't have a copy of Genesys 2012.01 and need to install it, download it from our website.

Tabbed Windows

Tabbed windows have stability issues and have been removed.

Obsolete Genesys Examples

  • Large Signal S Param Linear Test (2tones) .wsx

Resolved Issues

  • Export S data from Momentum simulation dataset will no longer cause the subsequent simulation to fail.
  • Fixed an issue where multiple runanalysis functions are used under different equation settings in a MATLAB Script equation.
  • Report proper error messages when thick metal touches the box wall under Momentum simulation with "Use Box" option.
  • Fixed TFR S parameter asymmetry issue.
  • Saving layout no longer requires a license, which prevents correupted layout in a workspace due to licensing issue.
  • Inserting a new layer in layout no longer creates a duplicate name.
  • Fixed an issue of placement of differential offset ports on layout.
  • Fixed ADS MOSFET model stability issues.
  • Fixed DIODE model singularity issues.
  • Fixed various issues related to platform stability, equations, sweeps, optimizations, MonteCarlo, graphs, simulations and syntheses.

Known Issues

  • Antivirus on your system may remove one or more files installed during the Genesys installation leading to a corrupt Genesys installation.
    Workaround: Disable antivirus and other related programs on your system before installing Genesys. You can enable them once the Genesys installation is complete.
  • For S/Filter synthesis, if the S/Filter synthesis dialog is the last window to be closed in the Genesys environment, the close button in the dialog does not work. Use "Window > Close All" menu instead.
  • If opening an S/Filter synthesis object pops up an error message box (e.g., due to incorrect S/Filter synthesis operations), it is not recommended to open such synthesis object during optimization. The popup message box could block the UI focus of the application so you cannot stop optimization until it is finished.
  • Quick Sweep in Spectrasys don't work correctly when the Circuit Link design contains a frequency translation device.
  • The Example\Spectrasys\Scripting\Excel_to_RF_Sys.exe spreadsheet to Spectrasys converter tool does not work on Windows 8.
  • Harmonics order is not correct for ATF-52543 component at the 5GHz and 5.5 GHz frequency. To see the correct harmonics, change the Min Amplitude Factor = 1e-8 in the Advanced tab of HB1 options and simulate it again.

Licensing Known Issues

  • Genesys 2012.01 and Genesys 2012.01 SP1 may not work after installing the new Modulated RF bundle.
    Workaround:
    1. Select Start > Genesys 2012.01 > Genesys Tools> Genesys Preference Tool option.
    2. Select & Add Available License Bundles to Selected License Bundles and click OK.
      Now you can invoke and use the features that are available in Selected License Bundles.

Operating System Roadmap

Genesys future releases post 2014.03 will not support Windows XP. For more details, refer to Supported Platforms.

 

 

 

Please help us improve
Please help us improve
Was this topic helpful? Yes No