Main Support:       Knowledge Center
Documentation:   ADS Documentation   >  ADS 2023   >  ADS 2023 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

Advanced Design System 2023 Release Notes

For general information about Advanced Design System (ADS), visit ADS webpage at http://www.keysight.com/find/eesof-ads.

Starting ADS 2022 release, support for the following operating systems has been discontinued:

  • Windows 7 Enterprise
  • RedHat Linux RHEL 6.x
  • SuSe Linux SLES 11

For more information, refer to Supported Platforms.

Contents

Feature Updates

Design Editing and Layout

  • General Enhancements
    • The select-ability of PCB Via/Padstacks and Smart Mount is subject to layer visibility, similar to the select-ability of all other layout objects.
    • Group editing multiple PCB vias or pads can be done in the Properties window.  When multiple PCB vias or multiple PCB pads are selected, the property window show the padstack used.  If multiple values are used, the property window shows "(multiple values)".  The padstack name can be changed from a dropdown list and will apply to all selected PCB vias or PCB pads.  Note that the padstack value of PCB vias defined from a Via Constraint Rule cannot be edited.
    • A new rule is supported by the constraint manager for specifying stacked vias.  This rule is integrated into interactive routing. For more information, see Via Rule Functions - Stack Via.
    • The Insert Via command is enhanced to support both vias and stacked vias in the same dialog box.  For stacked vias, suitable selection is presented based on Stacked Via Rules as well as stackable combinations of PCB and OA Vias. For more information, see Insert or Edit PCB Vias.
    • GDSII layer map files can now contain end of line comments that start with the # character.
    • GDSII Import has been enhanced to retain the multi-patterning properties, defined in the Open Access Data Model Specification version 1.0, for shapes and vias. These properties can be seen in the Info window.
    • A new 'Resolve Overlap Conflicts' dialog is added to facilitate the transition away from WYSIWYG connectivity mode.  It provides a consolidated view of all the overlap zones in the layout, and allows a user to resolve any connectivity conflicts as desired.  Moreover, the following related areas have also been enhanced to allow holistic solution:
      • Design Differences dialog has been updated to support a one-click resolve overlap zone conflicts action.
      • Blue dot merge nets dialog was updated with consistent behavior and improved user experience.

For more information, see Net Overlap Zone.

    • (Beta Feature) A new Simple Evaluator is available for evaluating component parameter expressions significantly faster than the existing Full Evaluator. The Simple Evaluator does not support all features of the Full Evaluator. A preference for which evaluator to use can be set per library as a library configuration preference in the Library Configuration Editor. If no preference is set, the new Simple Evaluator will be used.
    • (Beta Feature) A new connectivity mode for layout is added.  It can be activated by setting the environment variable "USE_NEW_CONNECTIVITY" to TRUE.  Designs may have their nets changed upon being open in this new mode for now--it won't be this case when this mode is officially released as the only layout connectivity mode. This mode is intended to be the only connectivity mode in layout after WYSIWYG is fully deprecated.
    • (Beta Feature) In 3D layout view, 3D bounding cuboid, instead of just all edges, of an instance is drawn. It can be activated by setting the environment variable "USE_EXPERIMENTAL_3D_FEATURES" to TRUE.
  • AEL Interfaces

  Back to Feature Updates

Data Display

  • Data Viewing, Analysis and Manipulation

    • Native Python functions are available to read an ADS dataset and convert it to a DataFrame. For more information, see Using Datasets in Python.
    • In Datalink 2023,
      • the ads and sm3d python wheels require minimum python version 3.7.
      • pwdatatools has been upgraded to keysight-pwdatatools 0.3.1. For more information, see PathWave Data Tools API Reference.
      • Python library seaborn has been added to the ADS Python DataLink. Seaborn is a plotting library that is based on matplotlib. It provides a high-level interface for visualizing data. For more information, see https://seaborn.pydata.org/
    • A new environment variable, DATA_HOME, is used for dataset alias paths. A dataset alias referencing a dataset in the path specified in DATA_HOME is automatically shortened to use this new variable in its path.  This method provides a better support for referencing a common directory across different workspaces and improves cross platform usage.
    • In Expression Manager,
      • a new option is available for creating multiple plots from a drag and drop of multiple selected expressions. For more information see, Expression Manager.
      • the dataset organization and management are enhanced--datasets insides the subfolders of the "data" directory are presented; external dataset directories and files can be added and presented.
      • the performance for selecting multiple objects in Expression Manager or Variable Explorer is improved.
    • A new capability of grouping a plot's Limit Line and Mask objects in to a single Specification object
    • The expression API collapse() now supports irregular data.

For more information, see Data Display.


File and Workspace Management Tools

  • General Enhancements

    • Improved usability and discoverability of the VS Code AEL extension:
      • A new Debug option added to the Command Line dialog can automatically launch VS Code that in turn attaches to ADS without having to manually start the debugger in VS Code.
      • VS Code can now debug multiple ADS sessions. 
      • VS Code is automatically disconnected from hpeesofde process upon ADS exit.
      • VS Code performs breakpoint verification and auto-save before loading an AEL file.
    • Improved open workspace performance of the Library View by deferring loading of libraries outside the workspace directory.  ADS can be used without restriction while waiting for the libraries to finish loading.
    • The Technology roughness models are copied to the destination library when copying a substrate to a new library.

    • Archive workspace now also lists dataset files outside the workspace directory for data-display references.
    • ADS uses TclTk version 8.5.  If a user has a custom $TCLLIBPATH environment setting that is incompatible with ADS's oaTcl settings, a warning will be issued, and the user's custom $TCLLIBPATH will be ignored in favor of the TclTk settings shipped with ADS.

  Back to Feature Updates

Circuit Simulation

  • General

    • The Remote and Distributed options have been removed in ADS 2023. To use remote or distributed simulations with circuit simulation, one can use the either "Simulation Manager" or the "Design Cloud" options.

    • The latest 102.6 version of the L-UTSOI model is now supported.

    • For ease of use, the new Monte Carlo controller now boasts both Yield and Yield Optim options. Future improvements to the Monte Carlo will be ported in that controller moving forward.

  • ElectroThermal
    • A Reusable Dynamic Thermal Model for thermal simulation may now be generated and used in Transient or Circuit Envelope Electrothermal simulations.
    • The handling of complex polygons is improved by splitting them into simpler polygons before a thermal model is built. This feature is enabled by setting the environment variable ETH_CLIP_POLYGON_THRESHOLD to "250".
  • Obsolescence Announcement

    • The RF System Budget Analysis is obsoleted.

Known Issues

  Back to Feature Updates

HSD Design

  • Memory Designer
    • HBM3 memory Interface addition in Memory Designer
    • LPDDR5x memory Interface addition in Memory Designer
    • Supports IBIS - EMD models in Memory Designer
    • Supports IBIS 7.1 parser
    • Allows users to use a custom IBIS file viewer instead of notepad.exe.
    • Dynamic display of Reference Designators on Controller and Memory components' symbol view.
    • Allows multi-segments smart bus wire connection in Memory Designer.
    • Multiple plots, ex Eye Density, from a drag and drop expression in the Expression Manager
    • CA/Data Bus Pre-Layout Builder enhancements
      • Added a row for instances' name - custom entry
      • Ability to drag and drop the instance (lines and vias) column 
      • Copy (right click) and paste (before/after) the instance column
      • Fit view all
      • Read variable values when computing the impedance and delay
    • Supports Design Clouds
  • SerDes Design
    • New Ethernet AMI Modeler
    • USB AMI model generation for NZR modulation and Spread Spectrum Clocking (SSC)
    • New USB reference channel models.
    • PCIe AMI model generation for Gen 6 with PAM4 modulation and weighted sum of DFE taps
    • New PCIe Gen6 reference channel models including 6-lane models with crosstalk.
    • PAM6 modulation for Tx in Channel Sim
    • Smart_Eye_Probe supports PAM4 for Transient Simulations
    • Channel Operating Margin (COM) - two new versions, 3.4 and 3.7 are added in ADS 2023
    • Supports external channels and Rx package model for measured-data based Tx_Waveform_AMI component.
    • PowerSum Crosstalk Calculation in S-Parameter Toolkit
    • ICR/ICN Calculation in S-Parameter Toolkit
    • Supports IBIS 7.1 parser
    • Supports Design Clouds
  • EM-SIPro/PIPro

    • RapidScan
      • Support for trapezoidal conductor cross sections, the edge angle is picked up from the substrate Angle parameter.
      • Improved coplanar ground detection 
    •  General
    • PIPro

      • Radiated emission calculations are now available as an optional output in the Conducted EMI analysis. 
      • CEMI Analysis now works with remote, cloud, and cluster simulations when running Design Cloud 2.5 or later versions.​
      • ADS now ships with a Power Integrity Conducted EMI Example using the Picotest SIC531 PCB: PIPro_Conducted_EMI_Example.7zads.
      • The python API package empro.toolkit.sipi has been deleted, use empro.toolkit.analysis instead.

      • Parameter sweeps as beta feature, e.g. allowing to sweep ambient temperature in PIPro-DC solutions.
      • Improved resource dialog for remote, cloud and cluster simulations.
    • SIPro
      • Analysis name for SIPro changed from PA-SI analysis to SI Analysis. This is a name change, the SI Analysis has the same functionality as the earlier PA-SI Analysis.
      • Consistent lowest frequency point simulation in SIPro: independent on the lowest user specified frequency and independent on the frequency plan, 20 kHz is used as the lowest calculated frequency. The resulted S-parameter will however represent the user specified frequencies.

      • Parameter sweeps as beta feature, e.g. allowing to sweep edge bias.
      • Improved resource dialog for remote, cloud and cluster simulations.

Known Issues

  Back to Feature Updates

EM Simulation

  • RFPro Platform

    • OpenAccess component instance parameters can be swept.
    • Complex designs open faster and consume less memory. Likewise, the performance of switching component roles and re-extracting nets has been improved.
    • Inspect the simulation mesh and ports through the new Mesh/Ports result view.
    • The multi-port excitation setup in the field visualization editor can be exported to or imported from a .csv or .json file.
    • The markup for an encrypted 3D component, a dotted bounding box, is no longer hindering when picking positions.
    • The visibility of a net can be toggled through a context menu.
    • Snapping during 3D component positioning or measuring has been improved.
    • Improved resource dialog for remote, cloud and cluster simulations.
    • The schematic interoperability between ADS and Virtuoso can improved by toggling between the 'empro_basic' and a new 'empro_basic-skill' library.
    • The Python version of SIPro, PIPro, RFPro and PEPro has been upgraded from Python 3.8 to 3.10. Most existing Python scripts will continue to run without modification. For detailed differences between Python 3.8 and 3.10, see https://docs.python.org/3/whatsnew/3.9.html and https://docs.python.org/3/whatsnew/3.10.html.
  • Momentum
    • TSMC's advanced IC process node features are now supported. Features include: width, thickness and resistivity bias, colors for multi-patterning and damage K. To benefit from this new capability, a new .ltd file must be generated by importing the .ircx file.
    • Per instructions from the foundry, when a layout scale factor is defined, first the scaling is applied, then the bias. Pre 2023, it used to be the other way around.
    • The ground loss model correction is no longer applied in case the substrate stack contains at least one semi-conductive layer. 
    • The Power Distribution Network analysis example with Momentum has been obsoleted and replaced by the Tutorial: Performing a PI-DC and PI-AC Anlaysis using PIPro.
  • FEM
    • The robustness of the meshing process has been improved for multi-technology designs.
    • Improved accuracy for passive device modeling on Silicon substrates. The section of a port line that passes through semiconductor material is no longer calibrated.
    • The temperature dependency of a conductor with surface resistance material is now correctly handled in Generation 2.
  • LTD Substrate Editor
    • The .ircx import generates an .ltd file that supports TSMC's advanced IC process node features.
    • The .ircx import allows to define or override the Silicon substrate layer height, permittivity and resistivity.
  • EM Setup
    • An issue has been fixed in the EM Setup-FEM flow for a simulation with a 3D component that has a multi-mode waveguide port
  • HFSS Option
    • HFSS simulations can be submitted to a remote host or scheduler through a PathWave Design Cloud simulation service

Known Issues

  Back to Feature Updates

Verification

  • Design Rule Check

    • ADS DRC supports over 20 new rules for polygon and edge selection.
    • New rules poly_oversize() and poly_undersize() provide improved performance and optional acute angle cutoff.
    • Fixed a Rules Compiler error related to clearance rules with connectivity qualifiers.
    • DRC functions are easier to find from the ADS Help navigation window. For more information, see DRC Functions (by category) and DRC Rules (by category).
    • To get started writing ADS DRC rules, try the new Create Rules dialog.  The dialog supports rules like acute angle, area density, non-90 angle and off-grid. The dialog is accessed through the Rules tab of the DRC dialog.

For more information, see Design Rule Checker (DRC).

  • Layout Versus Schematic

    • The function dve_connect_component_pins() supports CDF based components.
    • LVS supports evaluating parameters passed from the top-level design into a sub-circuit design.
    • Fixed an issue when running LVS from schematic where the layout window is not open, and the layout contains Smart Mount components.
    • LVS dialog reports Device Recognition rule file compile errors as errors (not warnings).

For more information, see Layout Versus Schematic (LVS).

  • PDK Validator
    • Component default callbacks are called prior to applying test values.
    • Cell names specified at the job level take precedence over values set at the PDK level.
    • PDK Validator supports placing a default design cell that exists in a different library than the component library.
    • The PDK Validator dialog checks if the test case is already open when the test case is viewed using the “Open test case” menu pick.

For more information, see PDK Validator .

  • Assura DRC Link
    • Documentation has been updated with troubleshooting tips. 

For more information, see Using Assura DRC Link.

  • Calibre LVS Link
    • Fixed an issue with running in local mode.
    • Documentation has been updated with troubleshooting tips.

For more information, see Using Calibre LVS Link.

Known Issues

  Back to Feature Updates

Power Electronics

  • SMPS Performance Testbench
    • Added a new tool called SMPS Performance Testbench, which enables the designer to run a series of simulated tests, either in a schematic design environment for a schematic-only type simulation or in PEPro environment for a post-layout type simulation which includes the layout parasitics.
  • Power Electronics Library
    • Added an Ideal Diode component to the Power Electronics Library,
  • Examples
    • Added an example to demonstrate the design of a fly back converter using ADS Power Electronics tools.
  • Netlist Import
    • Enhanced the netlist import tool to retain pin names from the input netlist file during the symbol generation for the model.
  • Power Electronics Model Builder
    • Bug fixes to the Power Electronics Model Builder (PEMB) tool.

Known Issues

  Back to Feature Updates

Signal Processing

  • Obsolescence Announcement

    • The DSPSource related features (e.g. DSP_To_ARF, 3GPPFDD_Dn/UpLink_src, TDSCDMA_Dn/UpLink_Src, WLAN_802_11a/b_Src) is obsoleted.

  Back to Feature Updates

Virtual Test Bench (VTB)

For general information about Virtual Test Bench (VTB), visit the VTB webpage at http://www.keysight.com/find/virtual-test-bench.

  • From ADS 2022:
    • Verification Test Bench (VTB) is now called Virtual Test Bench (VTB).
    • To install files that are required for the VTB functionality along with the ADS installer, you need to download a separate VTB installer for both Windows and Linux and manually install the VTB.
    • If you have already installed ADS and find VTB functionality is missing, then you need to download and manually install the VTB.
    • If you want to uninstall, then you need to manually uninstall VTB separately for both Windows and Linux.

For more information, refer VTB documentation.

Known Issues

  Back to Feature Updates

Licensing

  • ADS 2023 requires: a) the version 2022.02 of the EEsof EDA licensing software, b) a minimum code-word version 2022.02 or above, and c) the licensing server software, lmgrd and agileesofd, to be upgraded to at least the same versions as what are included in EEsof EDA Licensing software 2022.02 ADS 2023 will not start if any of these requirements is not met. Refer to the License Codeword Version Compatibility Table.
  • In the EEsof EDA License Tools version 2021.02, licensing vendor daemon (agileesofd) is integrated with FlexNet FNP 11.18.1 version (Windows) and FlexNet FNP 11.18.1 version (Linux) of FlexNet license manager daemon (lmgrd). For the Windows platform, ADS installer will automatically set up these two new license server daemons by default for the local node-locked license users; for the Linux platform, you need to follow the Setting Up Licenses on Linux instruction to complete the licensing configuration process. For more details, refer to Licensing (For Administrators).

Known Issues

  Back to Feature Updates

Known Issues

  Back to Feature Updates

Known Issues

Design and Technology Management

  • ADS dynamic link is compatible with Virtuoso releases up to IC6.1.8-64b.500.22 / ICADVM20.1-64.500.22;  it is not compatible, and hence not fully functional, with Virtuoso release number IC6.1.8-64b.500.24 / ICADVM20.1-64.500.24.
  • AEL constants are protected and should not be modified in any DDS expressions.  An AEL error will be issued in case an attempt to modify an AEL constant occurs.

  Back to Feature Updates

Design Guide

  • Unable to unarchive HDMI design guide from the Schematic view (DesignGuide > HDMI).
    Workarounds:
    • Unarchvie using the old ADS version.
    • HDMI design guide will open in case it is already unarchived.
  • Simulating the "1_Sim_CA" design in the DDR4 CTB design guide prompts the netlist error.
    Workaround: Open the schematic design "PatternGen_CA_Continuous" and arrange the pin numbers in order.
  • Simulating of schematics in the HDMI_Link_Simulation design guide prompt the netlist error.
    Workaround: Open the schematic design “HDMI_Diff_RX” and arrange the pin numbers order in order.

Design Kits

  • A design created using ADS2020 Non-Linear Demo Kit (NLD) and using NLD discontinuities like demo_bendP, demo_stepP, demo_teeP, etc. will not work as expected in ADS 2021.
    Workaround – In ADS 2021, either update the design with the latest NLD i.e. NLD shipped along with ADS 2021; or continue to use the NLD that was shipped with ADS 2020.

  Back to Feature Updates

Circuit Simulation

  • General

    • When using GoldenGate in ADS 2020 Update 2.0, some of the library files of RFIC cockpit options are not getting loaded due to license incompatibility. It is recommended to use ADS 2020 Update 1 when using GoldenGate in ADS.
      For details on license compatibility, see License Codeword Version Compatibility.

    • Simulation Manager may not work on Windows and throw exceptions for some designs.

    • ADS 2019 will not be compatible with Verilog-A files, which have been encrypted before ADS 2019. There is no change for non-encrypted Verilog-A files.

    • TMI models are supported for pure Hspice syntax only. The support of hybrid syntax (mixing Hspice and Spectre) is planned for a future release. 
    • BSIMSOI models using TMI modeling is not supported yet. Classical BSIMSOI models are supported as before.
    • TMI Aging simulations are not supported 
  • ElectroThermal

    • In ADS, electro thermal simulation is assisted to automatically turn off the HBAHB and TAHB options for single tone HB. However, the electro thermal simulation for multi-tone HB needs a manual intervention to turn off the HBAHB and TAHB options for reporting voltage data.

    • You may not be able to start a Transient/Envelope Electro-Thermal (ETH) simulation only when the same testbench is open in the viewer of Transient/Envelope thermal results. You need to close the viewer before launching a Transient/Envelope ETH simulation.

    • The electrothermal simulation will not run on designs created using Smart Mount for Multi-Technology feature.

    • Paths set while configuring the ETH controller may need to be updated when the workspace is moved across operating systems.

    • On a fresh Linux machine, electrothermal simulation fails with the following error message:

      Heatwave returned an unknown error code 127.

      Workaround: The error could be due to missing packages, for example, libpng12. Verify your system meets the requirements using the linux_sys_check.sh script. For more information,  see Checking Installed RPM Files and the Operating System Version.

    • If you get licensing errors while running thermal simulation, you may need the following workaround.
      Workaround: Rename the file  $HOME/.eesofrc. For example,  $HOME/.eesofrc-orig.

    • Electrothermal does not support remote simulation, batch simulation, Monte Carlo, tuning, Optimization, and Measurement Equations. Also, you cannot sweep directly on the DC controller.

    • All libraries referenced in a layout should use the same layout resolution, namely the OA database units (DBU) per user unit (UU).

    • You cannot run both a transient and envelope simulation on the same design from one testbench.

    • The calculation of power dissipation from passive components other than resistors may not be correct in harmonic balance simulations.

    • Electrothermal does not support the transient or envelope simulation that is controlled by a ParamSweep.  

    • If you get "Maximum timestep reduced to half of shortest transmission line delay " warning, it can lead to transient simulation to not converge   
      Workaround: Unselect "Limit timestep for Transmission Line" option on Time Setup tab of Tran component to get it work.

    • On Linux, if you specify the THERMAL_DIRECTORY variable in eesof_lib.cfg file using backward slash (..\thermal), the thermal simulation does not run properly.
      Workaround: Specify the THERMAL_DIRECTORY variable using forward slash (../thermal) instead of backward slash.

    • The ETH viewer does not support 4K displays. A few instances of text and icons may appear distorted. 

    • You receive an error message in substrate editor that you cannot use the same layer number more than once. You can safely ignore this error during thermal technology export.

    • On a fresh Windows 10 system, Electrothermal simulation terminates with an error. 
      Workaround: Install the following Microsoft Visual C++ runtime components: 

      http://www.microsoft.com/en-in/download/details.aspx?id=30679 

  • DDR Design 

    • You receive an error message to check port numbering when performing simulation with SnP component for differential configuration.
      Workaround: Select the first option in Pin Configuration for the SnP component.

  Back to Feature Updates 

HSD Design

  • SerDes
    • You receive an error message when runtime libraries for some of the ADS example ibs files (for old AMI models) are unable to get installed automatically during the ADS install.  The error appears eventhough the ibs file is supported on specific platform. 
      Workaround: Microsoft Visual C++ 2010 runtime library is required to run the dll files. Download the following library if it is not installed:

    • https://www.microsoft.com/en-in/download/details.aspx?id=26999

  • EM-SI/EM-PI
    • SIPro/PIPro, Via Designer 
      • On Windows 10 with Intel HD graphics, Via Designer may show an error message ‘Failed to use the connection between ADS and Via Designer.’  This has been isolated to the latest release of Intel HD Graphics drivers (23.xx.xx.xxxx).
        Workaround: Downgrading the graphics driver to the previously recommended driver resolves this issue (e.g., 22.20.16.4836, A05).
      • DirectX 9 as a graphics driver is no longer supported. DirectX 11 is thus be used by default. Run "diagdx" to verify which DirectX version is supported on your system.
    • SIPro/PIPro
      • ADS 2020 is not compatible with the latest available Samsung component models released in June 2018. The support for the component models is planned to be added in an upcoming update release.
      • Simulation failure when using components with S-parameter models or for which the model is defined using a lib/cel/view in case the Updating model does not require new simulation is not set. As a workaround, turn on the option. For PI-AC simulations, the options are turned on by default, for SIPro, this needs to be turned on explicitly.
      • If you run SIPro/PIPro on a fresh machine with Suse 11 or Redhat 6 installed, you may encounter the critical error "EMPro exited unexpectedly during execution." This is related to the graphics driver software.
        Workaround: Upgrade to the latest vendor-specific drivers and OpenGL libraries for the graphics card.
        Alternative workaround: 
        Run the following commands:

        cd $HPEESOF_DIR/fem/2020.20/linux_x86_64/bin
        ./startempro --personality=sipi--driver=x11

        Ignore any license-related error messages that may show up on executing these commands. The driver setting is saved per personality for future sessions.

      • With split domains on, there are no results available until simulation results are available from the last simulation, or even after the simulation.

      • Cadence® Allegro®(SPB 17.2 and SPB 17.4) is not supported on RHEL 8. As a result, the BRD Import and ADFI Export does not work on RHEL 8.

    • PIPro
      • The power graph is not correct when VRM's or Sinks are defined, starting from pin definitions. All the other result data is correct. This issue does not occur when VRMs and sinks are defined from component instances.

  Back to Feature Updates

EM Simulation

  • General
    • In a vncserver session running on an RHEL8.4 platform, you may encounter the critical error "EMPro exited unexpectedly during execution." This is related to the graphics driver software contained in the mesa-*.x86_64.20.3.3-2.el8 packages.
      Workaround: downgrade the packages to the previous version using the following command:

       sudo yum downgrade mesa-*

      The packages mesa-*-20.1.4-1.el8.x86_64, and the dependent llvm package work.

  • RFPro
    • The FEM and Momentum Generation 2 flows are state-of-the-art solvers but still evolving. In case it does not handle your design, switch back to Generation 1.

    • Multi-technology designs cannot be analyzed with Momentum.
      Workaround: Use the FEM simulator
    • Project load fails with the error 'OccDesign::getNet: key not found' when a layout shape has a multi-bit net name (e.g. 'd<7:0>' or 'a,c,net1').
      There is no workaround.
    • With McAfee Endpoint Security (ENS) enabled, the Momentum surface current visualization hangs.
      Workaround: Disable the "Enable Adaptive Threat Protection" flag in McAfee ENS.
  • RFPro and 3D Viewer

    • If the Geometry view is empty when opening the design, this may point to an issue with the graphics card driver.
      Recommended workaround: Upgrade to the latest vendor-specific drivers and OpenGL libraries for the graphics card.
      Alternative workaround 1: On Linux, launch the tool and force it to use the X11 driver. On Windows, set the driver to 'msw'. This preference is saved for the current user and per personality. You can do that by executing the following commands, e.g. in a shell on Linux:

      cd $HPEESOF_DIR/fem/2022.20/linux_x86_64/bin
      ./startempro --personality=rfpro --driver=x11
      ./startempro --personality=3dview --driver=x11

      Ignore any license-related error messages that may show up on executing these commands. The driver setting is saved per personality for future sessions.

      cd $HPEESOF_DIR/fem/2022.20/linux_x86_64/bin
      ./startempro --personality=rfpro --clear-preferences
      ./startempro --personality=3dview --clear-preferences

      For further troubleshooting with 3D libraries, refer to the following topics:

      Alternative workaround 2: Set the following environment variable EMPRO_SET_SOFTWARE_DRIVER_AS_DEFAULT=1. This variable controls the default driver when no preference was set. On Linux, X11 is used. On Windows, MSW is used.
      You can clear all preferences as follows:

  • EM Setup
    • On a Virtual Windows 10 system with Microsoft Hyper-V Video display driver, the 3D EM Preview with EM Setup Preprocessing may bring up a dialog with a Hoops error, and, after suppressing the dialog, it opens up blank.
      There is no workaround.
    • EM Setup faces issues submitting jobs to a cluster when the "sitecluster behavior" is not implemented in sitecluster implementation.

      Workaround: Add a behavior function to sitecluster that returns {} as output on stdout.

    • FEM based parallel jobs on sitecluster with behavior configuration (qbehave) may show incomplete simulation logs.
      Workaround: You can view the complete log available in the following location: <wrk_space>/simulation/<lib>/<cell>/layout/emSetup_FEM/proj.ep/Simulation/<simulation_num>/emds_dsn/design/emprfem*.log
  • Distributed simulations
    • The example implementation of the sitecluster command for LSF clusters may lead to failing simulations if the path or number of threads is too large.
      Workaround: See the workaround details in the sitecluster documentation.

Import/Export

    • Exporting with MentorDA link does not work with the latest Mentor Graphics software Version VX2.6. 

  Back to Feature Updates

Power Electronics

  • PowerMOS_SiC power devices operate under a very wide range of voltage and current slew rates and it is a challenge to create a model that converges under all conditions – especially conditions that depend upon what components are connected externally to the power device in the circuit schematic. Please contact technical support if you encounter such an issue when attempting to use this model.

  • If you run PEPro on a new machine with Suse 11 or Redhat 6 installed, you may encounter the critical error "EMPro exited unexpectedly during execution." This is related to the graphics driver software.
    Workaround: Upgrade to the latest vendor specific drivers and opengl libraries for the graphics card.
    Or
    Run the following commands:

    cd $HPEESOF_DIR/fem/2020.20/linux_x86_64/bin
    ./startempro --personality=sipi--driver=x11

    You can ignore any license related error messages. The driver setting is saved per personality for future sessions.

  Back to Feature Updates

Installation

  • While installing a new version of ADS, if you see “Previous version detected” error even after you have already run the uninstaller for that version of ADS, you may need to manually uninstall ADS before installation of the new ADS. To manually uninstall ADS, perform the following steps.
    1. Exit the current ADS installation session if it is running
    2. Remove or rename the file .com.zerog.registry.xml  under the folder  C:\Program Files\Zero G Registry . Both the folder and the file are by default hidden, so you may need to change the folder viewing setting to show hidden files and folders, do so via the Advanced settings of the View tab in the Windows Folder Options dialog box.
    3. Remove the ADS installation directory through the Windows Explorer.
  • After performing the above steps, you can re-start the ADS installer.

  Back to Feature Updates

Licensing

  • You may observe additional License Usage when Client Machine reconnects to network after intermittent disruption.
    Workaround: In case of network interruption on the client machine, to reclaim the inactive licenses, a TIMEOUT can be set using the TIMEOUTALL feature in options file (minimum time period of 15 minutes). The inactive license may stay checked out for this period of time

  • Unable to install Licensing Hardware Key Drivers on Windows.

  • Workarounds:

    • Turn off UEFI Secure Boot (BIOS) and use the default 6.3 version of the Wibu key driver delivered with the EEsof Licensing tools.

    • Turn on UEFI Secure Boot (BIOS), upgrade to ADS 2020 Update 2.0 and use the 6.51 WibuKey driver version available in the 2020.02 License tools installation directory.

    You will not be able to run older ADS releases with the 6.51 WibuKey dongle drivers

  • Setting FLEXLM_DIAGNOSTICS to the highest level (FLEXLM_DIAGNOSTICS=3) on Windows client may cause a crash during license checkout. Flexera is investigating this issue.
    Workaround: It is recommended not to use the FLEXLM_DIAGNOSTICS on Windows clients or use it at lower level (FLEXLM_DIAGNOSTICS=1 or FLEXLM_DIAGNOSTICS=2).
  • Licensing may not support a license file path that is too long. This will likely occur when you have too many license files.
    Workaround: Remove some license files, move the license files to a shorter directory path or to combine license files into a single file.

  • License Setup wizard may not be able to start license server with many license files. During setup, it may lead to a situation where a command prompt window appears/disappears incessantly. This is due to the fact that License Setup wizard is not able to start lmgrd with a long command line and may get stuck in a loop.
    Workaround: 

    1. It is recommended to combine all license code words tied to same MAC ID into single license file to avoid setting large number of license files.
    2. Try to use a shorter path to place license files.
    3. If #1 and/or #2 does not help, start the license server (lmgrd.exe) from the command line (e.g. lmgrd.exe -c <lic-file-path> -l <license_server_log.txt>) and then set <PRODUCT>_LICENSE_FILE=<PORT-NUMBER>@localhost for product you want to use on same PC.
  • Dongle drivers for Flex-10 dongles on Linux are release specific. Installing the latest dongle drivers on Linux will function properly only for the most recent EEsof releases.
    Workaround
    : Install and use dongle drivers as needed.  If you need to run the most recent EEsof releases, use the latest  Flex-10 dongle driver. If you need to use older releases, uninstall the latest dongle driver and re-install the older dongle driver

  • FLO and EEsof License setup are writing server logs at different locations. However, the EEsof server log file location is updated in the License Manager > Environment tab.
  • When multiple same-named INCREMENT lines of different version exist on the license server, few advanced FlexNet options to reserve/limit licenses may not work properly. 
  • Product Selector “Check Availability“ generates incorrect results (which leads to license failure) for older releases when multiple date base versions of like-named bundles exist in the license pool.
  • In Linux, Product Selector OK and Cancel Buttons locations are reserved.
  • Starting from FlexNet Publisher 2015 (also known as version 11.13.1), the adoption of the best practice of the least-privilege security therein results in the License Server related Windows Service to run with the LocalService Account privilege (instead of the LocalSystem privilege as before.)  Running with the LocalService Account privilege, an executable can no longer access any files located in the per-user specific type of folders.  As a result, any license file placed in those folders can no longer be accessed by the License Server when the License Server is automatically started via the Windows Service upon each PC reboot. For the local node-locked license, this would not result in any disruption to the usage of EEsof applications; however, for the license installed on a network PC that is accessed by multiple client PCs, this may cause EEsof applications not to start after the network PC reboots
    Workaround: Store your license files in the Windows folders that are accessible by the LocalService Account privilege.  For example, C:\ProgramData or C:\users\public are both qualified choices.  In general, any folder that has the "Users" group listed in its Properties > Security page and this "Users" group has the read permission enabled should work. 
  • Using the default port to connect to a license server may cause a delay when checking out licenses. If no port is given in the license file, Flexera scans ports 27000 to 27009 to find the port. Starting from FlexNet Publisher 2015 (aka version 11.13.1), the default timeout for the response from each port increased from .1 seconds to 3 seconds.

    To avoid the delay, KSM now issues licenses with port 27009 instead of leaving this blank. The EEsof License Setup Wizard (from Licensing 2017.01 onwards) handles some common situations such as: where it detects license file(s) without port, when users get a new license file with port 27009, or when all license files for a vendor daemon does not have same port.

    You will not be able to start the license server if all license files for a vendor daemon on a server does not have same port.
    Users who manually setup a license server or using EEsof License Setup Wizard with older licensing bits may need to manually edit license files to comply with the following rules:

    1. All license files for a vendor daemon on a server must use the same port (or all be blank). 

    2. Using the default port (blank) is allowed but may result in longer checkout times. 

    3. If setting up a network server, select an unused port that is not blocked by a firewall.

    Workaround: If the user cannot change the port, or wants to use the default Flexera ports, the environment variable FLEXLM_TIMEOUT can be set to .2 seconds (200000), to minimize the performance degradation. However, if the network latency is an issue in your environment, you may need to fine-tune this setting to minimize the general performance degradation while still accommodating the network latency.

  • Installation of EESof EDA tools (such as, SystemVue 2016.08, Genesys 2017.XX, or ADS 2017.XX) may hang at 4% (percentage vary based on the products) for few hours or even more on some specific machines.
    Workarounds:
    • Disable Firewall setting in Anti-Virus Software installed on the PC.
      or
    • Download and unzip process explorer from the below link and then invoke procexp.exe.
      https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
      Right click on the wusa.exe process under <Product installer exe> and select KillProcess. Now it will continue the product installation.
  • After installing EESof EDA tools (such as, SystemVue 2016.08, Genesys 2017.XX, or ADS 2017.XX) successfully and try to invoke the software or License wizard, you may encounter “api-ms-win-crt-runtime-l1-1-0.dll” missing error.
    Workaround: Install the Update for Universal C Runtime in Windows .  On Windows 64-bit system systems, the file to install is x64 version of the Microsoft hotfix KB2999226. A copy of the Windows6.1-KB2999226-x64.msu Microsoft 64-bit hotfix installer can be found under the C:\Program Files\Keysight\EEsof_License_Tools\bin directory.  The Microsoft hotfix KB2999226 can be found under the Update for Universal C Runtime in Windows  page at  https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows as well.
  • On a newly formatted RHEL system, the EEsof Licensing tools may fail to boot. This is because the FlexNet Publisher 2015 requires a certain rpm
    Workaround: Under the EEsof product installation directory, there exists a utility script named "Linux_sys_check.sh" under the bin directory. Run this script to find out whether any rpm is missing; run this script with a "-y" command-line option to also have all the missing rpms automatically installed if you have the sudo or root privilege.
  • License server may stop recognizing Flex-10 dongle on some systems within a few hours after starting
    Workaround: If v6.10 or v6.11 is found and experience this problem then upgrade the WibuKey drivers to v6.30/6.30b from Wibu Systems.
  • Unable to install Flex-10 driver if Flex-9 dongle is already plugged into a machine
    Workaround: Before installing a Flex-10 driver for the first time, unplug the Flex-9 dongle.
  • There is a known FlexNet Publisher issue, whereby mixing node-locked codewords and floating codewords in one license file can result in: a) Remote simulations not working or b) A second local simulation not working in case the license is node-locked and also has incorrect version.
    Workaround: It is strongly recommended that you do not mix node-locked codewords and floating codewords in one license file nor in any configuration that ends up with node-locked codewords and floating codewords both available on the same server. In other words, put the node-locked license and the floating license on different servers, and point to the respective one based on what you need to run.
  • If a user simultaneously runs two instances of a product and has mixed different versions of the same codeword on one license server, extra licenses may be pulled and result in unexpected “Licensed number of users already reached for this feature” errors.
    Workaround: We recommend you remove expired codewords, to separate out the new and the old versions of codewords into different files and different servers, and to point to the respective one based on what you need to run.
  • Not specifying the TCP/IP port for the license server during license setup may lead to unexpected behavior and/or license checkout failure on the Windows platform. We strongly recommend you to always explicitly specify the TCP/IP port associated with each license server.
  • A node-locked and floating bundle operating on Linux cannot be shared between products using EDA License Tools version older than 2014.01 when run at the same time.
  • License Setup Wizard does not remove any previous user-configured FLEX Windows License Service manually set up by a user using FlexNet's lmtools.
    Workaround: You must remove the previous user-configured Windows License Service via lmtools.
    • Run the lmtools.exe from C:\Program Files\Agilent\EEsof_License_Tools\bin to invoke the lmtools utility. The lmtools utility window is displayed.

      If you have installed an EEsof product released before 1st August, 2014 on your system prior to installing an EEsof product released after 1st August, 2014 then the default EEsof Licensing tools path will remain C:\Program Files\Agilent\EEsof_License_Tools. On the systems that only have EEsof products released after 1st August, 2014 installed then the default EEsof Licensing tools path will be C:\Program Files\Keysight\EEsof_License_Tools.
    • In the Service/License File tab, check the Configuration using Services option. All user-configured FLEX Windows License Services will be listed.
    • Select the service you wish to remove.
    • Select the Config Services tab and click the Remove Service button to remove the service.
      To ensure that the license service or lmgrd is running, click View Log. A log window appears that confirms whether agileesofd and lmgrd are up and running.
  • While running multiple versions of prior SHORT_PRODUCT_NAME releases together, set PRODUCT_NAME_MAXIMUM_BUNDLE_USAGE=ON in your environment so that all of them will use the same method to check out licenses. Otherwise, you might receive an error message, "Licensed number of users already reached".
  • For LSF style distributed simulations, ensure that the PATH on the client computer points to the $HPEESOF_DIR/EEsof_License_Tools/${architecture} directory that corresponds to the EEsof release being used. This needs to be done in order to ensure that the proper version of the Flexera utilities (like lmutil ) gets picked up in the path before any older in-compatible versions (that may also be installed on a users’ system.)
  • License Setup Wizard ( aglmwizard.exe ), which is used to set up and record the license path would not work if you already have an environment variable set for PRODUCT_NAME_LICENSE_FILE.
    Workaround: You can use PRODUCT_NAME_LICENSE_FILE variable to point to license file or refer to Licensing (For Administrators).
  • The License Setup Wizard will exit or not properly configure a license server, if the server has all of its licenses currently in use.
    Workaround: Wait for a license on the server to become available as you normally would before launching the product.
  • Unable to set license in case unicode characters are used either in path or license file name because the Flex License Service does not support these characters.
  • The Product Selector tool will be unable to display the license server status properly when connected to older license server.
    Workaround: Upgrade your license server to the latest version.

  • EEsof Licensing Tools installer can hang on systems with McAfee LiveSafe installed and running the default firewall settings.
    Workaround:  Prior to installing EEsof Licensing Tools, temporarily turn off the McAfee LiveSafe firewall.

  • Licensing setup steps on systems with McAfee LiveSafe installed can fail.
    Workaround:  Under the McAfee LiveSafe firewall settings, under Port and Settings, allow the use of port 27001 for lmgrd.exe under the EEsof Licensing Tools installation bin directory.  Under Internet Connections for Programs , enable lmgrd.exe, aglmmgr.exe and aglmwizard.exe for all devices and turn off monitoring.

  • On Windows, EEsof product releases prior to 2014 can have boot time issues with licensing if an newer EEsof product is installed prior to installing the older product. For example, if a users installs Advanced Design System 2017 and then installs Advanced Design systems 2014.01, the user can have boot time errors with ADS 2014.01.
    Workaround:  For Advanced Design System users,  set a system environmental variable named ADS_LICENSE_FILE under the Control Panel/ System, and Security / System / Advanced system settings and under the "environmental variables".  Add an System variable named ADS_LICENESE_FILE and the value will be the path to your local license file or the port@host setting for your site.

  Back to Feature Updates

Third Party Applications

  • Spyder application menu bar becomes inactive when the window is maximized using View > Full Screen or by pressing F11 (shortcut key to maximize the screen).
    Workaround: Press F11 again to make it the default screen. The menu bar is now active and works fine.

  Back to Feature Updates

Verification

  • Cadence applications (Assura) is not supported in RHEL 8 Linux Distribution. 

  Back to Feature Updates

Virtual Test Bench

  • From VTB 2022, SystemVue VTB's QT help file is integrated into SystemVue VTB installer. However, help does not open, when you press F1 for a VTB component.
    Workaround: Perform the following steps:
    1. Open a command window.

    2. Set the path to ADS help directory. Execute the following command:

      On Windows

      set path="<ADS_Install_DIR>\bin\Help";%PATH%

      On Linux

      export PATH=<ADS_Install_DIR>/bin/Help:$PATH

      On RHEL 7 (due to library related issue)

      export HPEESOF_DIR=<ADS_Install_DIR>
      export LD_LIBRARY_PATH=$HPEESOF_DIR/lib/linux_x86_64:$HPEESOF_DIR/lib/linux_x86:$LD_LIBRARY_PATH
      export PATH=$HPEESOF_DIR/bin:$PATH
      export PATH=$HPEESOF_DIR/bin/HELP:$PATH

      Where,

      <ADS_Install_DIR> is the ADS installation directory.

      On Windows: The default ADS location is "C:\Program Files\Keysight\ADS<version>"

      On Linux: The default ADS location is "/usr/local/ADS<version>".

      For example, <version> is 2022

    3. Invoke VTB help. Execute the following command:

      On Windows

      assistant -collectionfile "<VTB_Install_DIR>\Help\vtb.qhc"

      On Linux

      export SYSTEMVUE_INSTALLATION_DIRS=xxx/SystemVueVTB/2022
      assistant -collectionfile $SYSTEMVUE_INSTALLATION_DIRS/Help/vtb.qhc

      Where,

      <VTB_Install_DIR> is the SystemVueVTB installation directory on Windows.
      xxx is the directory where unzip or untar of VTB package is done on Linux
      On Windows: The default VTB location is "C:\Program Files\Keysight\SystemVueVTB2022"

      You can also refer to the online version of the SystemVueVTB documentation.

  • When using VTB on Virtual Machine (VM), if SystemVue crashes then ensure to restart your system.

  • To use VTB, ensure ADS is installed in a path that has only ASCII characters.

  • Backward compatibility
    In ADS, the customized VTB can have a backward compatibility issue.
    Workaround: To fix this issue, use one of the following methods:
    1. Open and Save the custom VTB in SystemVue2022Update0.1. Now, you can use the custom VTB in ADS.
    2. A built-in workspace conversion tool is provided in the installer. You can convert the custom workspace (.wsv) to the newer SystemVue version. Use the following steps to convert the workspaces:
      • Open Command Prompt in the Administrator mode.
      • Browse the location of the old workspace. For example, C:\ADS_VTB.
      • Run the following command parameter.

        C:\ADS_VTB><SystemVueVTB_Installation_Dir>\bin\WorkspaceConversionToolManaged.exe" VTB_Examples.wsv VTB_examples_new.wsv

        Where,

        1. <SystemVueVTB_Installation_Dir> is the location where SystemVue VTB package is installed. For example, C:\Program Files\Keysight\SystemVueVTB2022.

         2. VTB_Examples.wsv is old SystemVue file and VTB_examples_new.wsv is converted file.

    3. The following successful message is displayed.
      Created: VTB_example_new.wsv

    4. You can now use the VTB_examples_new.wsv workspace in ADS.

  • When multiple VTB versions are installed, the VTB package in the Library Configuration Editor remain fixed to a particular VTB version. However, symbol view uses the correct VTB version.

  Back to Feature Updates

Examples - Known Issues

  • Examples under <ADS Install Directory>\examples \Instrument_links folder are not getting opened on Linux where as they are opening fine on Windows.
    Workaround: Rename the ‘Instrument_links’ folder to ‘Instrument_Links’, if you have write permission to the <ADS Install Location>\examples folder. In case you do not have the write permission then proceed with manual unarchive process (File > Unarchive from the ADS Main window) pointing to the Example workspace. 

  • Example search might not work and prompt you the "Database is locked" error when ADS installation is on NAS.
    Workaround: Restart the nfslock service on client. In case the problem still persists, reboot the client to unlock the database.

  • Unable to compile Pin Diode Model using Visual Studio 2012 on Windows 7 64-bit platform.
    Workaround: Delete the contents of the directory examples\RF_Microwave\UserCompiledModel_wrk\ UserCompiledModel\lib.win32_64 before using UCMs.
  • An error occurs while running a custom VTB.
    Workaround: Download and run a custom VTB from the following location: <ADS Install Location>\SystemVue\2016.08\win32_64\VTB. 

   Back to Feature


Documentation

  • On Windows, Printing directly from installed help generates non-readable output.
    Workaround: Use the PDF version of the document for printing purposes.

  • From 2017 onwards, in the installed help when you open a page using the "Open a link in new tab" option the help does not open a page in a different tab by default. You need to set the preferences to open any link in a new tab.
    To set the preferences:

    1. From the 201x version of the installed help, Click Edit > Preferences.
      The Preferences Dialog box is displayed.

    2. Select the Options tab.

    3. Under Appearance, select the Show tabs for each individual page option.

    This is a one-time setting for a particular release of a product.
  • Unable to open online help, any external link, or Embedded Survey link in Linux on Mozilla Firefox browser.
    Workaround: Use Mozilla Firefox version 39 or above or keep the Mozilla Firefox window open and then try to open online help.
  • While using the installed help, you may encounter issues like help not showing any content, it throws an error, it displays unexpected hierarchy in the Content tab, or it does not display any search results.
    Workaround: Close the help, delete the contents of the following directory, and open the help again.
    • On Windows:  C:\Users\<Windows_Login_ID>\AppData\Local\Keysight\Help
    • On Linux: 
      • $HOME/.local/share/Keysight/Help
      • $HOME/.cache/Keysight
      • $HOME/.cache/rfdeqthelp
  • The installed help search does not support [] or {} or any other text using these combinations.
  • On Linux, Konqueror web-browser does not display the online help properly. It may not display help pages at all or may display them broken and with errors.
    Workaround: Use Mozilla Firefox to view the online help.

  Back to Feature Updates

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