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

Skip to end of metadata
Go to start of metadata

Advanced Design System 2019 Release Notes

For general information about Advanced Design System (ADS), visit ADS webpage at

From ADS 2017 release, the Linux system requirements has been updated:

  • Support for Redhat 5.x has been discontinued.
  • Updated the system libraries and rpm files. Following is the list of minimum patch versions required:
    • Redhat 6.8
    • Redhat 7.2
    • Suse 12 SP2
    • Suse 11.3

Few ADS features will not work properly, in case you have installed lower patch versions than the above-recommended versions.  

For more information, refer to Supported Platforms.


Feature Updates

Design and Technology Management

  • Python Datalink
    Datalink allows users to post-process simulation data in Data Display using Python and supports the following:

    • Send ADS-generated data to Python script
    • Read Python generated data in ADS
    • Call a Python Script from ADS, with optional data send and data read

    For more information, see ADS and Python Integration Using Datalink.

  • General

    • Added Workspace Cleanup tool to remove unnecessary files from your workspace. For more information, refer to Clean Up Workspace.

    • Update references now supports library and data files.

    • Added support for archiving external data files.

    • Improved performance for finding references and dependents used by file rename and delete.
    • Added option to execute DDS equation manually. For more information, see Automatic Equation Calculation.
    • Added new commands to view and update design references and dependents. For more information, see References and Dependents.
    • Improvements in Workspace Archive performance and information.
    • Improvements in Layer docking window: Layer search/filter enables you to view used layer(s).
    • Support creating new display packets and improved editing display packets
    • On screen editing support for Interoperable labels
    • Support open/edit design having Interoperable OA paths.

Known Issues

  Back to Feature Updates

Design Editing

  • Enhancements

    • Added ability to specify the net when inserting a via.

    • Layout Avoidance Routing – ADS will avoid metal areas on a different net when inserting a trace. For more information, see Avoidance Routing.

    • Insert Net Connection  - Creates a connection between two pins by merging the nets they are on. Once assigned to the same net, avoidance routing can be used when inserting a trace from one pin to the other. Insert Net Connection can also be invoked while inserting a trace by pressing the ‘C’ hotkey.

    • Smart Mount – Smart mount is a new method for inserting nested technology in a design. Smart mount components can be placed on a module or a PCB design without the need for complicated nested technology setup. For more information, see Smart Mount for Multi-Technology.

    • For assemblies operating at high frequencies, Electromagnetic (EM) coupling effects between different components can be significant enough to warrant their inclusion in the design flow. For more information, see Smart Mount for Multi-Technology.

  • Issues Addressed

    • Fixed issue where ADS would crash when attempting to map a new layer to a substrate in a read-only library.
    • If the Options > Preferences... > Entry/Edit > Polygon self-intersection checking option is checked, ADS will display an error if a self-intersecting polygon would be created in an editing operation (stretch edge, move vertex, add vertex, or delete vertex). Previously self-intersection checking was only performed when inserting a polygon.
    • Right clicking on flight wire will not cause ADS to crash.
    • PCB Vias appear in Via Search.
    • A change in 2017 caused meander traces to be drawn with rounded ends when the trace end-type was set to rounded. This is probably not what was desired when a meander trace was included in a PDK. Meanders in a PDK macro will draw a square end unless the compatibility policy is set to use the new add path/trace.
    • Fixed issue with add vertex to trace sometimes adding the vertex in the wrong location.
    • Several improvements in moving of points and vertices.

Known Issues

  Back to Feature Updates

Circuit Simulation

  • Electrothermal

    • A new meshing algorithm targets a fully-converged solution without requiring the user to manually specify HeatWave parameters. HeatWave auto-computes the relevant parameters to increase resolution, based on the user's initial settings and on characteristics of the design. For more information, see Setting Electro-Thermal Simulator Options.

    • A single component that dissipates power, for example, a spiral inductor, can be represented as multiple power sources that may have different vertical extents within a chip. A component’s power is apportioned among its split power sources before thermal simulation. See Splitting Power Across Heat Sources for an explanation of power splitting for the case where all power-sources for a component are equally thick and at the same height.

    • The Electrothermal FloorPlanner can now run in background locally, allowing the continued use of ADS while it runs. For more information, see Solve for Temperature in Background.

    • The temperature at the boundary of a design (ambient temperature) can now be swept during an Electrothermal simulation in persistent mode. The temperature must be set as the outer sweep parameter of the testbench. This removes the need to manually perform multiple simulations with different temperatures.
  • New ADS to FlexDCA connected flow
    ADS supports the newly developed FlexDCA_Probe component that allows you to send ADS waveforms directly to FlexDCA. FlexDCA is a powerful user interface for sampling oscilloscopes that come with comprehensive built-in measurement capabilities for SerDes, for instance, TDECQ, OMA, SER, etc for PAM-4 applications.

  • NXP SiMKit Models
    The models have been updated to SiMKit Release 5.0 (April 2018), and these are now the default.

    For more information, including supported device versions, see Devices and Models, NXP SiMKit.

  • Support for new or updated models:
  • Verilog-A
    ADS 2019 release includes an updated version of the Verilog-A compiler module. Users having encrypted Verilog-A models or releasing compiled libraries in their designs need to take note of the following:

    • Models compiled with previous versions of ADS needs to be recompiled.

    • Models encrypted with previous versions of ADS are not supported and have to be encrypted again. Files encrypted using ADS 2019 are appended with the .vax extension, older encrypted files with .vap extension are not supported. For more information, refer to Verilog-A in ADS Design Kits.
    • All PDKs with encrypted models must be updated to work with ADS 2019.

    • The Devices-Verilog-A component palette and examples using these components are no longer available. You can create your own symbols and use them in your designs. For more information, see Getting Started with Verilog-A in the Advanced Design System.

    • The tiburon-da_veriloga and tiburonda_hsd_kit design kit and included models are no longer available.

    • The internal Verilog-A version number has changed from 2.91.100 to 2.91.101.  This only affects early testers/users of ADS 2019, as only early pre-release versions used "2.91.100".  Any Verilog-A PDKs developed using pre-releases versiond of ADS 2019 may need to have the Verilog-A models recompiled.  This affects the locations of the work.db files, as their locations have changed from .ams_work/2.91.100/work.db to .ams_work/2.91.101/work.db.
    Models with Verilog-A source code in workspaces or PDKs will be automatically recompiled when needed.
  • Envelope simulation improvements
    • Improved accuracy and performance on S-parameter fitting.
    • Variable timestep option for more accurate result.
    • Enable Fast Envelope with VTB.
  • DDR Design
    • Added ‘Display’ tab to Eye_probe and Eye_Diff_Probe so that parameters can be made available to be edited directly on the schematic.
    • Enhanced measurement functions for S-parameter data.
    • Minor issues found in IBIS, EBD, SnP component, SParamChecker, simulation manager and UI related issues are solved. 

Known Issues

  Back to Feature Updates


EM Simulation

  • General
    • The EM Setup based flow supports designs with smart mount components.
  • Momentum
    • The surface impedance model has been enhanced to improve its accuracy towards DC.
    • The RF scaling is more accurate for substrates with multiple or infinite silicon layers.
  • FEM
    • The ambient temperature and temperature dependency of conductors materials is now taken into account.
    • Mapping of port distribution lines to mesh elements in FEM is now more robust. 
  • RFPro
    • First release of the new companion EM tool for RF circuit and module designers. For more information, see RFPro.
      • Evaluate the RF performance of a design taking into account the combination of circuit simulated components and EM simulated parasitics introduced by the layout of a design.
      • Built-in preset EM simulator setups (Momentum RF, Momentum Microwave or FEM) and easy mechanism to create and distributed customized presets.
      • Layout preprocessing options to ignore (remove) small conductor shapes and ignore (fill) small conductor holes.
      • Automatic via model lets Momentum determine the most appropriate via model type.
      • Fixture de-embedding of a component lets Momentum eliminate the nearby mutual coupling between the conductors leading up to the component ports.
  • Coilsys
    • Load functionality to restore last set pcell param values. For more information, see CoilSys

Known Issues

  Back to Feature Updates

Signal Integrity/Power Integrity

  • PIPro 

    • DC Analysis setups now allows to model discrete VRM models: Discrete Buck, Discrete Boost and Discrete Inverting. 

  • SIPro and PIPro 
    • Automatically will pick up lib/cell models for component assignment.
    • Simulations from command-line supported using Python API.
    • Temperature specification for conductor materials.
    • Capability to add and use virtual pins for port definitions
  • For more information, see SIPro and PIPro.

Known Issues

  Back to Feature Updates

Power Electronics

  • Power Electronics Library
    • Added new components to two new palettes: Power Electronics-Logic LT Compatible and Power Electronics-Logic. The Power Electronics-Logic LT Compatible palette contains Analog Behavioral Logic Gates BUF_L, INV_L, AND_L, OR_L, XOR_L, and D- and SR-Flip-Flops. These mirror the idiosyncrasies of logic gates implemented in LTspice (for example, one symbol to represent both OR and NOR that has both inverting and non-inverting outputs) and are instantiated if you import an LTspice netlist that contains logic. The Power Electronics-Logic palette also contains a similar set of logic gates but these have a more industry-standard behavior (for example, separate symbol for OR and NOR with one output each)  These are instantiated if you import a PSPICE netlist with Analog Behavioral Logic. For more information, refer to Power Electronics Library.

    • Added the Variable Turns Ideal Transformer Component for use with the Circuit Averaging (also called Averaged Switch Model) technique. For more information, refer to Variable Turns Transformer component.

    • Added the OpAmp5 (Operational Amplifier 5 pins) component. For more information, refer to OpAmp5.

  • Power Electronics Examples

  • Work Flow Configuration for Power Electronics

    • Added a Work Flow Configuration for Power Electronics projects. For more information, select Option  Work Flow Configuration... , then select Power Electronics in the Work Flow Configuration dialog box. Also, refer to the text on the dialog box. 

Known Issues

  Back to Feature Updates

Layout Versus Schematic (LVS)

  • Physical Nets LVS
    • Designs that produce a clean report for Pin Nets LVS may produce errors when run with Physical Nets LVS, because device-level component pins are not configured properly. Physical Nets LVS requires the component pin to be a shape to form a physical connection. 
      • Physical Nets LVS now checks for improperly configured components pins and displays a warning message.
        • Device-level component pins need to be configured as area pins.
        • Term and the area pin need to be on a conductive layer.
      • The area-pin requirement only applies to device-level components.  It is not necessary to add area pins on sub-designs.
    • Improved support for the system gnd! net.
      • Physical Nets now displays a warning identifying shapes on gnd! that are not physical connected in layout, instead of treating the missing connection as a nodal error.
    • Performance
    • Improved performance for designs with many round vias
  • Control LVS Pin Connectivity for User-Created Components

    • Components like spiral inductors generate nodal errors when run with Physical Nets LVS, because the pins are on the same physical net in layout and different nets in schematic.
    • Designers can now control LVS pin connectivity behavior for components in their local design library.
    • In the LVS dialog box
      • Run LVS
      • Right-click on a component listed under “Component Count”
        • Connect Component Pins
        • Deactivate and Short Component
    • Component library must be writable to use this feature. 
    • Feature can be used for layout components with fixed artwork in layout, an EM model and a look-alike symbol in the schematic.
    • For more information, see “Layout Versus Schematic (LVS): Setting Component LVS Commands”.
  • LVS Options
    • The LVS options tab controls settings that are specific to the designer’s methodology.
      • Many designers want to run LVS with settings that generate the most information for finding and fixing LVS errors. These are the recommended settings and system defaults for new workspaces. See LVS Options Recommended.  
      • Other designers want to run LVS with the most generic settings, especially when running LVS for the first time on a finished design.  See LVS Options for All Designs.  
    • LVS dialog options tab provides a way to select one or more LVS analysis to run
      • Options tab now shows information on supported design flows for each type of LVS analysis.
      • Only the tabs for the enabled analyses are displayed.
  • Pin Nets LVS
    • Pin Nets LVS report is a browser format that can be used to inspect mapped components at each level of the design hierarchy. 
    • The report now also shows mapped nets in a browser format.  Expand the header to browse and inspect mapped nets at each level of the design hierarchy.
    • To see the browser format
      • Pin nets option “All levels – hierarchical view”
      • Component mapping with instance names 
  • PDK Configuration
  • LVS Documentation
    • LVS documentation has been updated with new content.

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

  Back to Feature Updates

Design Rule Check (DRC)

  • Performance
    • Performance improvements for large layouts.
  • Custom Rules
    • Fixed problem where custom rules had to be defined at the end of the rule file.
  • DRC Dialog
  • Fixed problem where DRC results could not be loaded for certain polygons.
  • The setrule.ael file is now only loaded for the current rule location.
  • PDK Configuration

For more information. see Design Rule Check (DRC).

  Back to Feature Updates


  • Rule Categories
    • Assura DRC supports rule categories (switches). The DRC dialog box detects the Assura DRC configuration in the PDK and populates the Rules tab with rule categories.
  • Batch Mode
  • Import Assura DRC Results
    • Assura DRC results can be imported into the DRC dialog. Click Import from the DRC dialog box and browse to the Assura DRC results directory.
  • PDK Configuration

For more information, see Using Assura DRC Link.

  Back to Feature Updates

Artwork Translators

  • ODB++ Importer

    • Creates component footprint pads on a non-conductive information layer, rather than as conductive metal on the front or back side of the board. The actual conductive pads are still imported into the top level design. If area pins are needed, they can be created from the informational pad shapes in the footprint designs.

    • Both more and less restrictive on the characters allowed in imported component footprint cell names. Any legal ADS Cell name is now allowed, including names with the “.” character.  The “*” character is now mapped to “_”, as it is not legal in an ADS cell name. Re-imports of older designs may result in slight component name changes.

For more information, see Artwork and Design Translation.

  Back to Feature Updates


Verification Test Bench (VTB)

  • The Single Port VTB (only Source) simulation is now supported. Now, you can create complex modulated sources in SystemVue and use with ADS Circuit Envelope.
  • From ADS 2017, to install files that are required for the VTB functionality you need to download a separate VTB installer (for Windows only). For Linux, the VTB installer is bundled with ADS installer.
    • It is recommended to download compatible ADS and VTB installers to the same directory. After the download, run the ADS installer. This process will automatically install the VTB functionality.
    • If you have already installed ADS and find VTB functionality is missing, then you need to download and install the VTB.

Known Issues

  Back to Feature Updates


  • All the newly added examples are searchable using the Example Search dialog box.

For more information, see Working with Example Workspaces.

Known Issues

  Back to Feature Updates

Design Kits

  • Added a new utility for setting-up Si RFIC PDK model sections for circuit simulation. This utility can be used as a replacement of process include component. For more information, see Si RFIC PDK Model Include Utility .
  • With new Lisp functions supported in ADS 2019, PDK authors may have to modify their PDKs to selectively load functions that may have been emulated earlier.

Known Issues

  Back to Feature Updates



  • ADS  requires: a) the version 2018.04 of the EEsof EDA licensing software, b) a minimum code-word version 2018.04 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 2018.04. ADS All-Versions 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 2018.04, licensing vendor daemon (agileesofd) is integrated with FlexNet FNP version (Windows) and FlexNet FNP 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 Linux Licensing Setup instruction to complete the licensing configuration process. For more details, refer to Licensing (For Administrators).

Known Issues

  Back to Feature Updates

Known Issues

Design and Technology Management

  • Python Datalink
    • Measurement Equations cannot use any Datalink function.
    • The Spyder application included with Python Datalink does not work on the Suse platforms because the older versions of system libraries are not compatible with the Spyder application.
    • Exceed on Demand: Note that in some cases, EoD settings may need to be configured to properly display Spyder.  Please contact your EoD support representative for additional guidance.
  • 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 Editing

  Back to Feature Updates

Design Guide

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

Circuit Simulation

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

    • 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 script. For more information,  see Checking Installed RPM Files and the Operating System Version.
  • DDR Design
    • SnP components cause an error in simulation after preparing for a differential simulation for a particular configuration. The workaround is to use the first pin selection option on the SnP.

  Back to Feature Updates

EM Simulation

  • RFPro
    • Does not yet support multi-technology designs (using nested technology or smart mount).
    • Project load will fail when a layout shape has a multi-bit net name (e.g. 'd<7:0>' or 'a,c,net1') with the error 'OccDesign::getNet: key not found'.
    • With McAfee Endpoint Security enabled, the Momentum surface current visualization hangs.
      Workaround: Disable the "Enable Adaptive Threat Protection" flag in McAfee ENS.
    • On Windows 10 with Intel HD graphics, Via Designer may show an error message ‘Failed to use 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 graphics driver to the previous recommended driver resolves this issue (e.g.,A05).
    • DirectX 9 as graphics driver is no longer supported. DirectX 11 will be used by default. Run "diagdx" to verify which DirectX version your system supports.
  • EM Setup
    • On a Virtual Windows 10 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, opens up blank. There is no workaround.

  Back to Feature Updates

Signal Integrity/Power Integrity

  • SIPro/PIPro, Via Designer
    • On Windows 10 with Intel HD graphics, Via Designer may show an error message ‘Failed to use 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 graphics driver to the previous recommended driver resolves this issue (e.g.,A05).
    • DirectX 9 as graphics driver is no longer supported. DirectX 11 will be used by default. Run "diagdx" to verify which DirectX version your system supports.
  • SIPro/PIPro
    • ADS 2019 is not compatible with the latest available Samsung component models released in June 2018. The support for the component models will be added in an upcoming update release.
  • PIPro-DC
    • 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

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.

  Back to Feature Updates


  • 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


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

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

      • Disable Firewall setting in Anti-Virus Software installed on the PC.
      • Download and unzip process explorer from the below link and then invoke procexp.exe.
        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 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 "" 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 you experience this problem, install the latest WibuKey drivers 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 ADS releases together, set ADS_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".
    • On some Windows 7 machines, when more than one definition of an Ethernet adapter exists (duplicates), license checkouts may appear to hang up.
      Workaround: Disable the duplicate network card definitions in your network settings: Control Panel > Network and Internet > Network Connections. This issue has been acknowledged by Flexera and they have created a bug report (SIOC-000103097).
    • 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 ADS_LICENSE_FILE.
      Workaround: You can use ADS_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.
    • On Windows 10 systems with  UEFI Secure Boot (BIOS) turned on, Wibu USB key or dongles are not recognized and licenses based on the Wibu key can not  used.
      Workaround:  Disable UEFI Secure Boot under the BIOS settings.

  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 Test Bench

  • When you install ADS and VTB from different directories, uninstalling ADS does not uninstall VTB automatically.
    Workaround: You need to manually uninstall VTB from Start > Control Panel > Add/Remove Program.
  • ADS only supports import of Custom VTB (SystemVue workspace) created using SystemVue 2018.
  •  To use VTB, ensure ADS is installed in a path that has only ASCII characters.
  • Backward compatibility
    In ADS, the customized VTB can have the backward compatibility issue.
    Workaround: To fix this issue, use one of the following method:
    1. Open and Save the custom VTB in SystemVue 2018. 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>"<ADS_Install_Dir>\SystemVue\2018\ win32_64\ bin\ WorkspaceConversionTool.exe" VTB_Examples.wsv VTB_examples_new.wsv

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

  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 Updates


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

  • From ADS 2016.01 onwards, in ADS 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 ADS 201x (or the installed version) Help, Click File > 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 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 Firefox window open and then try to open online help.
  • ADS online help is not supported on the Google Chrome browser.
    Workaround: Use Internet Explorer or Firefox version 39 or above to view ADS documentation.
  • While using the installed ADS 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
  • ADS installed help search does not support [] or {} or any other text using these combinations.

  Back to Feature Updates

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