Main Support:       Knowledge Center
Documentation:   IC-CAP English Doc   >  Previous Supported Releases   >  PathWave Device Modeling (IC-CAP) 2022   >  ICCAP 2022 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

PathWave Device Modeling (IC-CAP) 2022 Release Notes

PathWave Device Modeling (IC-CAP) is the industry standard platform for DC and High Frequency measurement and modeling of semiconductor devices. For general information about PathWave Device Modeling (IC-CAP), refer to the Keysight EEsof product page.

This document describes new features, functionality, fixed issues and known issues in PathWave Device Modeling (IC-CAP) 2022. It also includes documentation changes and provides workarounds for defects wherever possible.

To download  PathWave Device Modeling (IC-CAP) 2022, visit the Keysight EEsof Knowledge Center website.

What's New

Enhancements

  • PathWave Device Modeling (IC-CAP) now supports Python 3. It provides an immersive Python 3 experience, with expanded package support, integrated plotting, and linkage to customized installations.  PathWave Device Modeling (IC-CAP) Python 3 standard configuration now includes additional packages like Pandas, SymPy, H5Py, OpenPyXL, and the most updated version of SciPy, NumPy, MatPlotLib (see the documentation for a complete list of packages).
    Here is a summary of the new Python 3 capabilities:
    • Python 3.8.5 support
    • Convenient Python 2 to 3 script to convert current Model files that contain Python 2 code to Python 3. For more information, refer Python 2 to 3 Converter.
    • New Python packages: Pandas, SymPy, H5Py, OpenPyXL, XLRD, XlsxWriter, and many others.
    • Python demos and examples now use Python 3. See examples/python and examples/demo_fetures/5x3_PYTHON_PROGRAMMING directories. 
    • Python 3 modeling application examples to showcase the power of MatPlotLib, NumPy, and Pandas. See file py_mos_app_ex.mdl in the examples/demo_fetures/5x3_PYTHON_PROGRAMMING directory.
    • Enhanced IC-CAP Python API and documentation. To view the documentation, refer Python API Documentation for PathWave Device Modeling.

      The existing Python 2.7 programs may not work well and may need to be converted to Python 3 using the provided converter. For more information, refer Python 2 to 3 Converter. Refer to https://docs.python.org/3.8/howto/pyporting.html for details.

  • The PathWave Device Modeling (IC-CAP) Python 3.8 Interpreter can be extended with a user's own C/C++ implemented extension module using the Python documented process of building a python shared library (.pyd or .so). For more information, refer https://docs.python.org/3.8/extending/extending.html. This library file should be placed in a directory where the Python Interpreter can find it, on the standard search path or by extending sys.path in a python script before attempting to import the module.

Changes

  • PathWave Device Modeling (IC-CAP) will automatically check on startup if a minimum set of required python modules is found in the python installation.  Any warnings or errors found during the check with regards to the minimum required python modules will be reported to the status window on startup.  To disable this automatic check on startup a new environment/configuration file variable named ICCAP_PYTHON_NO_MODULE_CHECK can be set. For more information, refer List of Configuration Variables.

Issues Fixed

  • Any warnings or errors found during the check with regards to the minimum required python modules will be reported to the status window on startup. To disable this automatic check on startup a new environment/configuration file variable named ICCAP_PYTHON_NO_MODULE_CHECK can be set. For more information, refer List of Configuration Variables.
  • Fixed the measure dialog hang in the Angelov_GaN_Modeling model (Toolkit) when changing to a high number of frequency points.
  • Fixed the issue of missing text in the Measurement Debugging Tools dialog (in the latest version of AdMOS packages).
  • Fixed the issue of overlapping text in the Status pane information (in the latest version of AdMOS packages).
  • Fixed the Canvas issues for the new dark and light color theme.
  • If the message "Simulator did not identify version" appears with failed simulations while simulating with the ADS simulator, use ADS 2021 Update 1.0 or later version.
  • Fixed the issue of 'get_var()' returning incorrect IP address value for variables.
  • Fixed the issue of Python showing an error when Input/Outputs use variable strings for their field values.
  • Fixed the issue of PNA driver for PNA-L 5230C with an option 425.
  • Fixed the issue of Tuner Min/Max field width.
  • Fixed the issue of Keithley 26xx missing 'Init Command' instrument option causing Angelov-GaN toolkit not recognizing it.
  • Fixed an issue in the iccap python API where passing an Output/Input or Transform dictionary that represents an IC-CAP dataset into some of the different iccap python functions would not read the dictionary data in properly.

    Now in PathWave Device Modeling (IC-CAP) 2022, the Output/Input/Transform dictionaries with measure data, or with measure and simulated data will be passed into the python iccap functions with all the data intact, where as, in prior releases, only the simulated data would be passed into the function intact and the measure data would be discarded or converted from measure data into common data. This change to fix this improper behavior with how the Input/Output/Transform dictionaries that represent IC-CAP datasets in IC-CAP 2022 may cause previous python code with dictionaries to now see the following error occur:

    "Error: dictionary format is not a valid IC-CAP dataset"

    This is because  DM_PRODUCT_SHORT_NAME 2022 will use stricter rules on determining if a python dictionary represents a valid IC-CAP dataset. The dictionary must have include a 2 item tuple key where the first element of the tuple is a character representing the type of dataset contained by the dictionary. The valid characters that can be used are the uppercase 'M' for measured data, and uppercase 'S' for simulated data, and uppercase 'C' for common data.

    Some examples of valid python dictionaries that represent valid IC-CAP datasets are the following:

    A. DM_PRODUCT_SHORT_NAME DC Voltage Output with first order sweep dataset with both Measure and Simulated data represented as a Python Dictionary:

    {
    ('M', '11'): [(0.0004+0j), 0j, 0j],
    ('S', '11'): [0j, (-0.000671183+0j), (-0.000657576+0j)]
    }

    B. IC-CAP S-Parameter Output with first order sweep dataset with both Measure and Simulated data represented as a Python Dictionary:

    {
    ('M', '11'): [(0.972565-0.127472j), (0.941986-0.275208j), (0.880493-0.408478j)],
    ('M', '21'): [(0.00528336+0.0520554j), (0.0241585+0.111626j), (0.0552139+0.163994j)],
    ('M', '12'): [(0.00507355+0.0525513j), (0.024025+0.112129j), (0.0548248+0.164459j)],
    ('M', '22'): [(1.01447-0.0617676j), (0.998291-0.133118j), (0.976257-0.198914j)],
    ('S', '11'): [(0.989891-0.129094j), (0.952238-0.277412j), (0.890485-0.412026j)],
    ('S', '21'): [(0.00513904+0.0523477j), (0.0242414+0.111634j), (0.0554282+0.163591j)],
    ('S', '12'): [(0.00513904+0.0523477j), (0.0242414+0.111634j), (0.0554282+0.163591j)],
    ('S', '22'): [(0.996573-0.063535j), (0.983758-0.137764j), (0.962565-0.207798j)]
    }


    C. DM_PRODUCT_SHORT_NAME transform with simulated dataset only represented as a Python Dictionary:

    {
    ('S', '11'): [1.53257, -0.000450023, -0.200657576, -2.2340211562]
    }

    D. DM_PRODUCT_SHORT_NAME transform with common dataset only represented as a Python Dictionary:

    {
    ('C', '11'): [(3.357125-0.065532j), (-0.09450023+0.116234j), (-0.6575762+0.0563221j), (-12.2340211562-0.2321146j)]
    }

    With DM_PRODUCT_SHORT_NAME 2022, if the first character element of the dictionary key's 2 item tuple is not a valid character such as 'S', 'M' or 'C', then when that dictionary is passed into some iccap functions that take a dataset argument, the function may return an error such as the following:
    "Error: dictionary format is not a valid IC-CAP dataset".

Installation

  • If Keysight IO Library is installed by super user/root on Linux and other users on that machine want to use the IO Library, the following steps should be done:

    • Change permission of files under /dev/pcigpib
    • Add user to kt-iols, usbtmc and dialout groups 

    For more details, refer Keysight IO library documentation.

  • During installation of any product, if you get a warning message related to previous version detected and that release is already uninstalled, go to the .com.zerog.registry.xml file in the C:\Program Files | (x86)\Zero G Registry\.com.zerog.registry.xml (hidden file folder) and remove the old entry manually.

  • On Linux platforms: If using National Instrument IO Libraries, Keysight IO Libraries, or TAMS IO Libraries that support VISA interface and instrument connections, these are the default locations that  PathWave Device Modeling (IC-CAP) will search on startup for the appropriate libvisa.so shared VISA IO shared library file with executable permission

    • The Linux  PathWave Device Modeling (IC-CAP) startup script will look for a VISA Shared IO library file named libvisa.so on the Linux system in the following methods in order
      • If the optional environment variable VISA_IO_LIBRARY_PATH is set in the current user's environment to have the full file path location to the libvisa.so file,  PathWave Device Modeling (IC-CAP) will try to use that libvisa.so specified file path and no other.
      • If the VISA_IO_LIBRARY_PATH environment variable is not set, then  PathWave Device Modeling (IC-CAP) will search for a compatible VISA IO Library shared library in the following locations:
        • (Red Hat Enterprise 7 Only)  PathWave Device Modeling (IC-CAP) will search for Keysight IO Libraries VISA IO shared library files with executable permissions 
          • Linux 64-bit OS (Red Hat Enterprise 7) only: /usr/local/lib64/libivivisa.so and /opt/keysight/iolibs/libktvisa32.so 
        • If not found, then  PathWave Device Modeling (IC-CAP) will search for a NI IO VISA Libraries libvisa.so shared library file with executable permissions at the following location:
          • Linux 64-bit OS: /usr/local/lib64/libvisa.so or /usr/lib/x86_64-linux-gnu/libvisa.so
        • If not found in the previous location, then  PathWave Device Modeling (IC-CAP) will search for a TAMS IO Libraries libvisa.so shared library file with executable permissions at the following location:
          • Linux 64-bit OS: /usr/lib64/libvisa.so
        • If not found in the previous location, then  PathWave Device Modeling (IC-CAP) will search for the IVI Foundation libivivisa.so shared library file with executable permissions at the following location:
          • Linux 64-bit OS only: /usr/lib64/libivivisa.so

            The IVI foundation's VISA IO libivivisa.so will only be able to communicate via VISA IO with instruments if there is a vendor IO Library installed (i,e. Keysight IO Libraries or another vendor) and registered with the IVI foundation's libivivisa.so as an available vendor VISA IO library installed on the system.

Licensing

  • PathWave Device Modeling (IC-CAP) requires: a) the version 2020.02 of the EEsof EDA licensing software, b) a minimum code-word version 2020.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 2020.02. IC-CAP  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 2020.02, licensing vendor daemon (agileesofd) is integrated with FlexNet FNP 11.16.5.1 version (Windows) and FlexNet FNP 11.16.5.1 version (Linux) of FlexNet license manager daemon (lmgrd). For the Windows platform, PathWave Device Modeling (IC-CAP) 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 Administrator).

Known Issues

ProblemSolution
Setups with LIST type sweep for frequency all other inputs CON sweep will not simulate properly with AFS.

Workaround:

Change any CON bias to a LIST sweep with a single value. 

 

The following Python syntax, used in PythonLocal Macros or Transforms, leads to an unexpected Python error.

For a list, such as,

l = [1,2,3] # list of three integers. 

then

error = [l[i] for i in range(3)] # list comprehension.

or

error = list(l[i] for i in range(3)) # list constructor.

results in the following error:

NameError: name 'l' is not defined


Workaround:

Use PythonGlobal

The following Python syntax, used in PythonLocal Macros or Transforms, leads to an unexpected Python error:

NameError: name 'get_par' is not defined
from iccap import get_par
# get the parameters
L, W, M = [ get_par(p) for p in ("L", "W", "_M") ]

The get_par appears to be out of scope in the list comprehension. This unexpected behavior was introduced by Python 3. We recommend using PythonGlobal until further investigation.

Workaround:

Use PythonGlobal. Use caution since by using PythonGlobal, a transform may modify a variable in the global namespace, which was created by another macro or function. It is recommended that Python scripts are developed in their own modules or .py files so the code resides in their own namespace. Use transforms and macros to import the modules and call functions, classes, and methods within the modules.

The following code causes an error during parsing.

SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 632-633: truncated \uXXXX escape

during parsing. To trigger the error simply make any edit in the script. Note that the function will execute without errors.

from iccap import Setup

from icutils import pivimport

# Note the use of r (raw string) in defining the Windows path to avoid 
# the directory separators being interpreted as escape characters

in_file = r'C:\Data\users\ic2020\test\mes\idvd.mes'

pivimport.mes_file_import_create_noprompt(Setup("."), in_file, use_iv_lsync=Tru, debug=False)

Workaround:

Use '\\' or forward slashes '/' (UNIX STYLE) in the path definitions. For example:

in_file = 'C:\\Data\\users\\ic2020\\test\\mes\\idvd.mes'



On LINUX, running several simulations using ADS via script may cause the following error:

Error: Error handling gemx message

Internal error: Attempt to access dead Gemx Connection

Workaround:

Using ADS 2021 Update 2 or later may mitigate the issue.

Also, the issue may be caused by network latency, make sure ICCAP_TEMP is local.

In some Extraction Packages, such as the CMOS Modeling Packages, the GaN CMC Modeling Package, etc. Plots may be displayed with a background that is not consistent with the current theme, i.e. white background in Light theme and black background in Dark theme would be consistent. This is due to Plot Options at Model, Plots or IC-CAP/Main level being set to White Background or default.

Workaround:

  • In the Model file and Plots, make sure the White Background option in the Plot Options dialog is set to Automatic. This means that the Plot and Model will look at the settings at the IC-CAP Main for plot background color.
  • In the IC-CAP/Main window/Tools/Plot Options dialog, select White Background or Automatic if the current theme is Light. Unselect both Automatic and White Background if the current theme is Dark. This selection will propagate down the hierarchy in all loaded Models and Plots as long as their White Background setting is Automatic.
Issues with Data Viewer while using the Dark or Light theme. 

Workaround:

Use Data Viewer in the Legacy mode.

UI issues in the CMOS Modeling Packages:

  • Some dialogs may have a legacy color style, including light blue or gray background.
  • In the Measurement Module, the 'Select Devices' dialog is not styled as per new themes.
  • In the Extraction Modules, some extraction steps may not be fully visible.
  • Selecting some Tabs may result in a very wide or tall window, which may be difficult to manage if the screen resolution is not FHD (1920x1080) or higher.
  • In the Extraction Module, the Project Directory name in the status panel may overlap with the Status label.

Workaround:

Use the CMOS Modeling Packages in the Legacy mode to avoid issues related to the new UI.

Custom Dialogs designed with PathWave Device Modeling (IC-CAP) GUI Studio may require color and layout adjustment due to the new color themes and the different dimensions of the widgets. A dialog will typically require a larger window size.

Workaround:

  • Use default colors for background and foreground texts to automatically adapt these to the current themes
  • Increase the window's default width and height
  • Insert horizontal and vertical scrollbars to allow the user to navigate within the window
  • Simplify your dialog to use fewer widgets, hide advanced options into a different dialog
  • Use Legacy mode as a temporary fallback. Note that Legacy mode will no longer be supported in  PathWave Device Modeling (IC-CAP) 2022.
It takes longer time for PathWave Device Modeling (IC-CAP) to launch.

Here is the list of possible causes and workarounds:

  • Network condition to the license server(s) can affect the launch time.
  • If a LAN-GPIB interface or a TCPIP instrument had been connected last time and if the connection is offline at the next start of PathWave Device Modeling (IC-CAP), it could be no response until it is timeout (default is 120s).
    Workaround: If this is the case, get the connection back online. Another workaround is before launching PathWave Device Modeling (IC-CAP), open <UserHOME>/.icconfig file in a text editor, search for 'LINK HDWR "Hardware"', and at the dev_file_list section change the interface/connection name to "dummy".
  • Cleaning up the temporary folder, which is normally '<UserHOME>\AppData\Local\Temp' on Windows, that PathWave Device Modeling (IC-CAP) uses could be a potential solution for the longer time to launch.
System variable WAFERPRO_HIDE_S2_STATUS does not work on Linux.NA
In the DEFINE_EXTR_BOX Utilities transform, if you press   OK, Done! , the window is reopened, but it takes the parameter.

Press OK, Done! and close the Window using the Close window button (in top-right corner).

Using Two-Port simulations with DC outputs in Eldo, some two-port points (often only the first curve) will show minor variance from the Two-Port Simulation alone. These variances have only been observed beyond 8 digits of precision. Keysight is working with Mentor to determine the root cause of this variance.Unless the precision beyond 8 digits is crucial, this can be ignored.

ASM_HEMT_MODELING or MVSG_MODELING if opened through right click 'Edit...' will not load automatically the required *_GaN_UTILITIES model files. As a result most transform execution will show a Error:

For ASM_HEMT_MODELING

[...] Function iccap_func could not locate 'ASM_HEMT_GaN_UTILITIES/ [...]

For MVSG_MODELING

[...] Function iccap_func could not locate 'MVSG_GaN_UTILITIES/ [...]

Go to the Main IC-CAP window and double click on the ASM_HEMT_MODELING or MVSG_MODELING file.
Angelov-GaN modeling package: Tune/Optimize does not work with the ADS built-in model in ADS2019/ADS2020.

Since the angelov_gan.va file is no more included in the new ADS versions, the compiled va library of the model for the ADS versions was added in this  PathWave Device Modeling (IC-CAP) installation, which resolved the tuner/optimizer issue as a workaround. Note that the model name used in the package was changed from 'angelov_gan_va' to 'angelov_gan' as the default.

Angelov-GaN modeling package / ADA-HBT modeling package gives error: ERROR: Could not set Cal/State File Name [.cst only] to ... The instrument option name of the PNA driver was changed to "Cal/State File Name [.csa|.cst only]". To update the internally-stored instrument options list, click Reset IO Table button in the Measure module window.
Angelov-GaN modeling package / ADA-HBT modeling package gives error: ERROR: Keysight PNA.xx.xx: While recalling calibration file : C:\134Users\134Public\134Network Analyzer\134Documents\134atxxx.csa

Use forward slash instead of backslash even on Windows, for example:

  • C:/Users/Public/Network Analyzer/Documents/atxxx.csa
  • C:/Program Files/Agilent/Network Analyzer/Documents/atxxx.csa

Note: If the file is in the PNA-default folder (see PNA manual), just file name without path will work.

B1500A: Invalid Pulse Width setting in the Instrument Options table results in Error-120: Incorrect parameter value.

Set valid Pulse Width:

HPSMU/MPSMU/HRSMU: >= 500us

MCSMU: >=50us / 2us resolution

Instrument option settings is not correctly handled in measurements if WPRO_INIT transform is added and it does not have the call to load instrument options.Insert a line to call WPro_LoadInstrOptions(RoutineName, SetupName) function in the WPRO_INIT transform of the user-defined Routine/Setups.
E4991B is not supported.NA 
In B1500, the measurement fails with NI IO Library in the old instrument mode.Close the Nucleus software and restart the computer. 
Timeout failure on non-VISA connection with B1500A in long-time measurement such as Sampling measurement.

Use VISA connection with the System Variable 'USE_STB_OPC_FOR_DATA' = Yes, which is introduced in  PathWave Device Modeling (IC-CAP) 2021.

This is valid for VISA INSTR (Instrument) connection only, not for SICL/IEEE-488.2 connections or VISA INTFC (Interface) connection. Currently this option is effective only for B1500A.

Unable to simulate few setups in BSIMSOI4 Modeling Package using ADS 2019 Update 1.0 and ADS 2019.

Use ADS 2017 Update 1.0 for simulation in the BSIMSOI4 Modeling Package.

Variable containing double quotes is not parsed accurately.

This issue exists in files that are saved in older versions of IC-CAP. If you save the file in earlier versions 2016.04 with a variable, for example,  xyz "test" and reload it in 2016.04/2018/2020 Update 1. This variable will show as xyz " or something similar. This issue is fixed in the latest  PathWave Device Modeling (IC-CAP) release.

Workaround:

  • Load the file into IC-CAP 2020 or later.
  • Fix the double-quoted string in the variables.
  • Save the file with the new IC-CAP 2020 or later.

PathWave Device Modeling (IC-CAP) cannot retrieve data from HSPICE result if the number of signals exceed 512.

Workaround:

Reduce the number of output nodes by adding #echo .option posttop=1 to the HSPICE simulations. This option defines the hierarchy depth saved in output file. For posttop=1, HSPICE only saves voltage and current information of top level nodes and branches.

When changing DIODE parameters in the Qg setup (time-domain simulation), at some point the parameter change makes the simulation not running without error, and it never recovers from the deadlock until turning on the Simulation Debugger.

Workaround:

The cause seems to be too high impedance at the Gate node of the model for the time-domain simulation. Add a 100 Tohm resistance between G-S of the transistor in the Test Circuit.

2x Model files with two Circuit (Models)

  • If model file #1 circuit is changed but you only simulate the circuit file #2, the update from one does not get parse correctly automatically

Workaround:

If you simulate, all the referenced models need to get parsed so include all other model files.

The built-in SPICE2 and HPspice simulators rely on g2c libraries on Linux platforms. These libraries are not officially available for Suse 12. 

Workaround:

The recommendation is to use SPICE3 for examples set to use SPICE2 or HPSpice on Suse 12.  These example files may be made to work by changing or adding the system variable SIMULATOR to spice3.

For PathWave Device Modeling (IC-CAP) 2022 on Linux, the Miniconda fontconfig installation is taking precedence over the system fonts installed in /etc/fonts. A wide array of fonts are still available in the font selector box for plot options, but those specially added to the OS do not appear.

Workaround:

No instructions for workaround are available, but adding the fonts to $ICCAP_ROOT/tools/etc/fonts in the same way one would install to the root system at /etc/fonts should provide a workaround. 

Segment Sweep with Noise analysis is not creating the correct netlist for the ADS simulator.


Documentation

ProblemSolution

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.

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

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. 


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.


Installation

ProblemSolution
On Windows systems, if you have installed a pre-release version of IC-CAP and then try to install the current version or a newer version of the IC-CAP release, you can get the warning stating 'Previous Version Detected' even though you have uninstalled the current version properly.To get past the 'Previous Version Detected' message while installing, you need to delete the .com.zerog.registry file.
  • On 64 bit systems the file is at C:\Program Files (x86)\Zero G Registry\ .com.zerog.registry.
IC-CAP ships with an installation of ImageMagick ‘convert’ for the Save Image feature in plots. Without a working ‘convert’ call, the Save Image option can only save JPG, BMP, PNG, PPM, XBM, and XPM formats. The version of convert shipped with IC-CAP does not work on Red Hat version 5, though most default installations of Red Hat version 5 will have a working ImageMagick tool in /usr/bin/convert folder. IC-CAP tests for a workable ‘convert’ program during launch. Initially at $MAGICK_HOME/bin/convert, then within IC-CAP installation, and finally within the path. A warning about the limited save options are issued at launch if no working version of ‘convert’ is found.To avoid this warning, you can install a current version of ImageMagick on your system or set the MAGICK_HOME environment variable to a working installation.
If McAfee antivirus is running, it may pause the installation.On disabling the Security firewall option in McAfee antivirus settings, the installation works fine. After the installation is complete, enable the Security firewall option in the McAfee antivirus settings.

On Linux, PathWave Device Modeling (IC-CAP) is only able to communicate with either Keysight IO Libraries Suite 2020 or later versions, or the TAMS IO Libraries installed on the same system, but cannot work with both TAMS and Keysight IO libraries installed at the same time. The libsicl.so installed by both Keysight IO Libraries Suite and TAMS IO Libraries will overwrite each other in the /usr/lib64/libsicl.so location.

Choose to only install either Keysight IO Libraries Suite 2020 or TAMS IO Libraries on the Linux Red Hat Enterprise 7 platform.

Licensing

ProblemSolution
New license server software packaged in the EEsof EDA License Tools version 2014.01 does not work on SuSE 10 platform.Use SuSE 11 or RHEL 5 or 6 instead as your Linux license server machine.
License server may stop recognizing Flex-10 dongle on some systems within a few hours after starting.If you experience this problem, it can be remedied by installing the latest WibuKey drivers from Wibu Systems.
Unable to install Flex-10 driver if Flex-9 dongle is already plugged into a machine.Before installing a Flex-10 driver for the first time, unplug the Flex-9 dongle.
There is a known Flexera FNP 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.
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.
Additionally, we also recommend you to 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.
On the Linux platform, PRODUCT_NAME_LICENSE_FILE needs to be correctly specified before starting SHORT_PRODUCT_NAME. Without that being set correctly, SHORT_PRODUCT_NAME would not start.
Set PRODUCT_NAME_LICENSE_FILE as instructed.
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 2014.01 and 11.9.0.0 or earlier when run at the same time.NA
The "Check-in failed" message occurs in the license activity log occasionally can be ignored; the license mentioned in this message is actually properly returned.NA
License Setup Wizard does not remove any previous user-configured FLEX Windows License Service installed using FlexNet's lmtools.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.
  • 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".
NA
On some Windows 7 machines, when more than one definition of an Ethernet adapter exists (duplicates), license checkouts may appear to hang up.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).
If a license server is configured with two license versions, that is, version 2.8 and 2.9 node-locked license files, the license server may crash.You should combine the two license files into one file, instead of using them separately.
For LSF style distributed simulations, in case of windows, ensure that the PATH 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.
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.Wait for a license on the server to become available as you normally would before launching the product.
If SHORT_PRODUCT_NAME does not start after you reboot your 64-bit Windows computer, and a license denial message is displayed, then it might be caused by a spurious registry entry.
Check to see if registry entry HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager\EEsof EDA License Server exists; if it does, remove it and restart SHORT_PRODUCT_NAME.
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.NA
The Product Selector tool will be unable to display the license server status properly when connected to older license server.Upgrade your license server to the latest version.

When the same user is running similar simulations from multiple sessions of IC-CAP on the same computer and display—that is, the same User-Display-Host— and if simulations are rerun an extra license may be pulled.

Click Stop from the Status window of all the IC-CAP sessions to release all the simulator licenses, then rerun the simulations.

Product selector opens every time we invoke IC-CAP 2014.04 even when we auto-start by selecting a particular product license.

Set the environment variables, IC-CAP_PRODSEL_PREVIOUS and IC-CAP_PRODSEL_AUTOSTART to the same values of what it is creating ICCAP_PRODSEL_PREVIOUS and ICCAP_PRODSEL_AUTOSTART resolves the problem.

Documentation

Starting with 2021, the online help gets a new user interface (UI) that brings new features and enhanced usability. Using the new features, you can do the following among many other things:

  • Browse and use the online help on all device sizes like mobiles, tablets, laptops, and desktops.
  • Refine search queries right from the documentation.
  • Filter pages in the navigation tree using keywords.
  • Apply dark theme.
  • Change hyperlinks color.
  • Copy code samples with a click.
  • Copy links to sections with a click.
  • Use keyboard shortcuts to perform different actions.
  • Use QR code to open any page on mobile and tablets.

For more details, see How to Use Online Help.

Additionally, the offline help now lets you create PDFs on-the-fly while you are connected to the internet using the PDF button on the top-right corner of pages. It works just like online help.

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