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

 

  

Main Support:       Knowledge Center
Documentation:   ADS English Doc   >  ads2019update1   >  ADS 2019 Update 1.0 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

ADS 2019 Update 1.0 Release Notes

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

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.

Contents

Feature Updates

Memory Designer 

  • Introducing a Revolutionized Workflow for Memory System Design. This new feature reduces DDR setup time from hours to minutes, and provides a predictive design flow for DDR4 and beyond. 
    • New super-components for setup of memory controllers and memory devices - applying IBIS models as a group of signals.
    • 1-click connection of bus-wires between new super-components and PCB; connections are made automatically by matching Signal ID information.
    • One schematic for both Transient and DDR Bus sim, with no changes needed to be made to the schematic to swap between them.  (The change of signal stimulus is changed and netlisted automatically).
    • New universal Memory Probe - provides intelligent access to signals anywhere within the schematic, and apply measurements as a group.
    • Memory Probe can invoke automated DDR4 Compliance Testing - using Keysight's industry-proven measurement science (DDR4 Compliance test suite with the Infiniium, as used in hardware compliance test).
  • Updates to SIPro to support Memory Designer Workflow, including a new DDR Setup wizard, to help generate EM setups in a highly productive manner - and a DDR Attribute editor, to view/edit the Signal IDs parsed from the layout information.  
  • Huge speed up to SIPro Power-Aware SI EM extractions where power plane metallization and decaps are included in the extraction. 

Known Issues

  Back to Feature Updates

High-Speed Serial Channel Simulation 

  • New MIPI C-PHY 3-wire Tx and CphyEye_Probe added. These new models work in both ChannelSim and Transient simulations, and allow the user to look at triggered and non-triggered eyes. 
  • New 8B9B encoder for MIPI D-PHY added. The new encoder is supported with Tx_AMI, XtlkTx_AMI, Tx_Diff, Tx_SingleEnded, Xtlk2_Diff, and Xtlk2_SingleEnded models.
  • Channel Operating Margin (COM) is a channel compliance test used in IEEE 802.3bs and some JEDEC standards. This simulation similar to an SNR calulation, is now built-in as a new simulation option to the Channel Simulator. Therefore, now ADS Channel Simulator supports both IBIS-AMI and COM flows in a complete and smooth workflow by bit-by-bit, statistical, and COM mode selection under Channel Simulator Controller. This simulation option automatically invokes a Matlab Runtime (or optionally full version) in order to process the COM calculations as per the standard.  
  • FlexDCA probe supports both Waveform Memory and Slot configurations. By transferring waveforms directly to Keysight's FlexDCA, it enables customers' easy access to complex analyses like PAM-4 measurements including TDECQ, Jitter decomposition, and 802.3bs compliance tests as well as FlexDCA's built-in math, signal processing and transforms, and simulation capabilities, 
  • Back Channel Interface (BCI) - IBIS-AMI BIRD 147.6 can provide support for link training; Whereby the Tx and Rx IBIS-AMI components that support the same BCI protocol, can pass messages to each other in order to optimize the Equalization settings in both Tx and Rx.  For a user this is a huge usability and productivity improvement, and typically means that an optimum equalized eye can be achieved without the need to sweep every possible EQ setting in both models. 

  Back to Feature Updates

Design and Technology Management

  • The new technology wizard has been updated to support adding a library/pdk technology not currently in the workspace. 
  • Improved the performance of the reference DB and its impact on other operations. 
  • Fixed the reference DB to handle read-only user libraries. 
  • References and dependents window now prompts appropriate message if you delete something after listing its references or dependents.
  • Closing a modified design without saving now updates the reference db.  
  • Removing a library or library definition file will warn you about dependents that are in the set of libraries being removed. 
  • Check workspace now checks the problems in read-only user libraries when setting is enabled. 

For more information, see References and Dependents.

Known Issues

  Back to Feature Updates

Design Editing

  • New Pcb vias are different in ADS 2019 Update 1. Old Pcb Vias are now called as ‘Padstack Templates’. You can create new Pcb Vias by specifying which padstack template to use and additionally user can specify start/stop layer and stackable attribute. For more information on New Pcb Vias, see Define and Insert PCB Pads using Padstack Templates.
  • A new Smart Mount subtype Multi-Mount is added. These are intended for designs that can be either used as a bottom mount, flip chip or a custom mount. The decision is left up to the module designer, at the time of instantiation of the smart mount design. The mounting type of this instance can also be changed once placed. For more information, see Multi-Mount under What is Smart Mount help topic.

Known Issues

  Back to Feature Updates

Circuit Simulation

  • Virtual Test Benches
    • The Virtual Test Benches have been upgraded to support the latest 5GNR tests.

    • Circuit data are now saved by default when using VTB to enable circuit insights under modulated signals conditions.

  • Support for new or updated models:
    • Support for  the latest BSIM-IMG model (102.9.2)
  • Issues Addressed:
    • Performance improvement on the oscillation nodes selection on large designs.

    • Fixed a discontinuity in the BSIMSOI negative bias region

Known Issues

  Back to Feature Updates

  

EM Simulation

  • RFPro

    • New EM (FEM only) analysis capability for multi-technology designs (Nested Technology or Smart Mount):

      • Extracts physical interconnects crossing technology boundaries including bond wires.

      • Ports can be easily defined from (virtual) pins placed anywhere in the design hierarchy.

    • New User-Defined EM Extraction analysis type allows to EM-simulate selected nets of a large design.
    • The Dielectric Size Options context menu on a design provides control over the size of infinite dielectric layers for FEM simulations.
    • The Far Zone Sensor settings under the analysis Options → Frequency Plans → Fields Storage allows enabling or disabling far field computations. The angular resolution of the 3D far zone sensor can be specified as well.
    • Issues Addressed:
      • Material Editors in RFPro have been made read-only. Material properties must be modified at their source.
      • Small shape display culling has been improved.
      • Virtual pin editing has been improved.
      • Advanced Simulator Options per Net are properly passed to the Momentum simulator.
      • Dielectric vias are properly treated in RFPro.
      • The Far Field plot updates properly when the excitation is updated.
      • The Cell Role Recognition Rule can be customized.
  • EM Setup

    • A new 'SMPS' frequency plan type supports Switched Mode Power Supply simulations.
  • FEM

    • New control over the port calibration approach with the 'Direct', 'SMD' and 'Delta-Gap' Feed Type. For more information, see Ports in FEM.

    • Issues Addressed:

      • Simulation Resources: the shipping sitecluster.py has been renamed to sitecluster.example to more easily allow a custom sitecluster.py to be picked up.

  • Momentum 
    • The Momentum layout preprocessing for FEM simulations has been enhanced to preserve the Feed Type in support of the new FEM port calibration capabilities.

Known Issues

  Back to Feature Updates

Signal Integrity/Power Integrity

  • Typically 70% reduction in memory usage for PIPro DC Electro-Thermal, and 1.5x performance speedup. 
  • Performance improvements in DDR SIPro simulations, with huge speedups (5x or better) for simulations where Power-Aware simulation (power plane metallization and decaps) are included in the extraction.
  • New DDR analyses setup tool, including attribute editor allowing to view and modify DDR Signal IDs (attributes such as Reference Designator, Signal Type and Signal Index). An analysis for DDR generated using the DDR setup tool is optimized for speed.
  • For SIPro simulations, and PIPro-AC simulations, components models have a new option: ("Updating model does not require new simulation"). 
    • Enabling this option allows modifying the component value or model after the simulation. This is the default for new PIPro simulation setups.
    • Disabling this option no longer allows the component value to be changed except by performing a new simulation. This is the default for new SIPro simulation setups. Disabling this option typically improves the SIPro simulation time and memory requirements. 
  • Capability to define back drill vias in SIPro, per net edited in a table.
  • Control for resource control for all SIPro and PIPro analysis with the capability to specify the number of threads being used during the analysis simulation.
  • Capability to remote simulate on LSF/PBS/Subgrid cluster when SIPro or PIPro user interface is launched on a machine in the cluster.

For more information, see SIPro and PIPro.

Known Issues

  Back to Feature Updates

Power Electronics

  • Power Electronics Library
    • Power Electronics specific controllers for Transient simulation and Harmonic Balance simulation have been added to the Power Electronics library.
    • SMPS frequency plan type has been added to the EM simulation setup, which creates a composite frequency plan that can capture the most important EM features of a PCB in switched-mode power supply circuits.
    • Schmitt components compatible with LTspice have been added to the Power Electronics library.
    • Set Dominant and Reset Dominant flip-flops have been added to the Power Electronics library.
    • Spectre compatibility has been added for Advanced Spice Model for High Electron Mobility Transistors (ASM-HEMT). 

Known Issues

  Back to Feature Updates

  

Verification Test Bench (VTB)

  • Upgraded SystemVue 2018 Update 1 engine in ADS.
    • The following 5G NR VTBs updates include :

      • Support Test Models defined in 3GPP TS 38.141 V1.2.0(2018-11) for NR downlink examples.
      • Support Common Configuration defined by Table 6.1-1 in 3GPP 38.521-1/38.521-2 for NR uplink examples. 
      • Speed up the EVM measurement by reducing the measurement length to 1 subframe.
      • Add ACLR measurement.

  • Parameters to the above 5G NR VTBs added/modifiled/removed to support above new features. So, you may need to update the VTB parameters in the existing designs and respective Data Display tables/graphs due to changes in the Sink name. You may get different results compare to the ADS 2019 release.

  • SystemVue engine used by ADS 2019 Update 1 is evolved based on the updated SystemVue 2018 Update 1 VTB engine. Due to this the above VTB examples may provide different results for ADS 2019 Update 1 and SystemVue 2018 Update 1. If you need to make changes to these examples, it is recommended to open and modify them with SystemVue2018 Update 1, and then import them back into ADS, and observe the results by running ADS 2019 Update 1.

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

    With the default settings in SystemVue VTB, SystemVue manages the time scale of the simulation. In general, when the VTB has sinks, the sinks are set in such a way (inside the SystemVue workspace) that the stop time of the simulation is automatically set to retrieve the amount of data necessary to calculate the requested figure-of-merit. In the case where the VTB does not have sink (input-only VTB), the stop time may be not clearly set in the SystemVue workspace. In this case, this may result in a long simulation if the stop time is large.

    By default, no warning is issued because the simulator does not know the stop time of the SV workspace before running it.

    If the user sets a value different from 100n (excluding 0), the envelope controller becomes the master. In this case, the simulation will stop at the first stop time it reaches (either the stop time set in the Envelope controller or the stop time set in the SystemVue workspace). Setting a custom stop time may be useful to debug general VTBs (without having to run the full timeframe) and may be required for input-only VTBs to set a realistic stop time

    When you set 100ns, for back compatibility, the simulator ignores it. stop=100n was the value set in the controller when you put it on the schematic. To be back compatible, stop time = 100n means that we let the SV workspace control the timing.

  • 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.
  • ADS 2019 Update 1 only supports import of Custom VTB (SystemVue workspace) created using SystemVue 2018 Update 1.

Known Issues

  Back to Feature Updates

 

Licensing

  • ADS 2019 Update 1 requires: a) the version 2019.02 of the EEsof EDA licensing software, b) a minimum code-word version 2019.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 2019.02. 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 2019.02, licensing vendor daemon (agileesofd) is integrated with FlexNet FNP 11.13.1.4 version (Windows) and FlexNet FNP 11.13.1.3 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

Memory Designer

  • Memory Probe is unable to automatically get the speed grade from the Memory Controller.
    Workaround: Manually specify the Memory Controller speed grade correctly in the Memory Probe speed grade parameter.
  • On clicking Run, a “No named nodes were found” warning is displayed. 
    Workaround: Ignore the warning and click “Run anyway”.
  • DDR Termination component supports only one clock termination topology which is the series resistor.
  • Memory Probe’s Signal Selection tab list all pins connected by wires regardless of whether the signals in these pins are enabled for simulation in controller or DRAM.
  • Loading a large IBIS file (>100MB) takes a long time without any indication of the progress.
  • Infiniium overwrites the existing PDF report file with same file name without warning.

  Back to Feature Update 

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

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

  • 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
    • Project load fails 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 previously recommended driver resolves this issue (e.g., 22.20.16.4836,A05).
    • DirectX 9 as graphics driver is no longer supported. DirectX 11 driver is used by default. Run "diagdx" to verify the DirectX version that your system supports.
  • 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, opens up blank.
  • Momentum
    • In rare cases, when cumulating edge mesh and thick metals, the new conductor loss model introduced in ADS 2019 can lead to an overestimation of the resistance of the conductor when increasing frequency. The issue is scheduled to be addressed in ADS 2020. 

  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 previously recommended driver resolves this issue (e.g., 22.20.16.4836,A05).
    • DirectX 9 as graphics driver is no longer supported. DirectX 11 driver is used by default. Run "diagdx" to verify the DirectX version that 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.
    • DDR Attribute Editor shows RefDes, Signal Type, and Signal index as “Unknown” by default for newly created sipiSetups.
      Workaround: Click the Auto Assign option. The Auto Assign option automatically assigns correct values for all Unknown values.

    • In Power Aware SI analysis, the Multiple Components Model Groups Default Model Editor's Updatable Component option is incorrectly displayed as enabled by default.

  • 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.
  • PIPro-AC, DC, ET
    • When doing an AC, DC or ETH simulation on Sungrid, the simulation log is is not getting updated during the simulation. After the simulation is completed, the log file is displayed correctly.  

  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

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

  • Unable to install Licensing Hardware Key Drivers on Windows.
    Workaround: Turn off UEFI Secure Boot (BIOS) and use the default 6.3 version of the Wibu key driver delivered with the EEsof Licensing tools.

  • 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://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx
      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 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  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".
  • 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  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 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 followingmethod:
    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 

Documentation

  • On Windows, printing directly from installed help generates non-readable output.
    Workaround: Use the 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