Page tree
Skip to end of metadata
Go to start of metadata

PathWave RF Synthesis (Genesys) 2022 Release Notes

(W5309B) PathWave RF Synthesis (Genesys) Core + System

  • This feature brings the ability for RF system designers to incorporate layout effects due to board parasitics into their system-level simulations. This can be done both during prototyping and later for verification of the final design, as long as a layout is available. It is recommended to use Keysight EMPro and RFPro for this workflow, but it can also work with third-party tools.
  • Added two new examples to demonstrate this feature: 
    • Layout Modeling 28GHz TX.wsv
    • Layout Modeling Two Stage Cascade.wsv
  • For more information, see Spectrasys Layout Modeling.

Spectrasys AM / AM and AM / PM Amplifier Modelling

  • AM to AM modeling is now supported in Spectrasys for the following models: 

    • RFAMP

    • RFAMP_HO

    • RFAMP_IP2

    • NonLin

    • NonLin_HO

    • VarAmp

  • The method of data entry can use data directly from Keysight Vector Network Analyzers, without reformatting the data.

  • S-Parameter based nonlinear models like SDATA_NL, SDATA_NL_HO, SDATA_NLI do not support the AM to AM feature.

  • The NonLinearModelingMode parameter is used to enable the AM to AM capability. 

    • The default nonlinear parameter mode supports user-entered nonlinear parameters like P1dB, PSat, and so on.

    • When the Compression Curve option is selected the following AM to AM parameters are enabled:

      • AM_AM_PinPwr - This is the corresponding vector of input power into the device in dBm.

      • AM_AM_Data - This is the AM to AM data vector.

      • AM_PM_Data - This is the AM to PM data vector. 

      • AM_AM_OverrideOddIPn - By default, the third-order intercept is being extracted from the data using equations derived by our Vector Network Analyzer (VNA) engineers. 
  • Added a new example for this feature:

    • AM to AM PM VNA XParams.wsv
  • For more information, see AM to AM and AM to PM.

Spectrasys Frequency Multipliers

  • Frequency multipliers are enhanced to support rich spurious response simulation even when spurious responses are very close in power level to the main signal being multiplied. See the Frequency Multiplier model for additional information.
  • A new parameter MixOrderMax is added to the frequency multiplier model to allow users the maximum mixing order of the spurious responses they want to simulate.

Spectrasys Frequency Dividers

  • Fixed some defects regarding the SSB decomposition into its AM and PM components for Frequency Dividers were addresses.

System Simulation/Models

  • Added new parameter to RFAMP model to specify the order of IM products and harmonics to be generated. This can be used to overwrite the System Analysis order setting on select parts as desired.

Non-Linear MaxOrder parameter 

  • The following nonlinear models now support the MaxOrder parameter that will limit the maximum intermod and harmonic order created by the model. As a default, the model will use whatever order is listed in the System Analysis. The maximum simulation order for a model can never exceed the Maximum Order specified on the System Analysis. For example, if you want to simulate 5th order intermods and harmonics you cannot do so just by changing the order of the single model. Rather you can change the Maximum Order on the System Analysis to 5 or greater. In the model, as a default, it will use the System Analysis maximum order. The model MaxOrder will restrict the order even more if desired. Here is a list of supported models: 
    • RFAmp
    • RFAmpHO
    • NonLin
    • NonLinHO
    • RFAmp_IP2
    • SData_NL
    • SData_NL_HO
    • SData_NLI
    • VarAmp
    • ATTN_NonLinear
    • Switch_NonLinear
    • SDSwitch1
    • SDSwitch2
    • SDSwitch3
    • SDSwitch4
    • SDSwitch6
    • SDSwitch8

Vendor Parts Library

  • Latest library from X-Microwave
    • New layout symbols showing the size and physical design of parts.
  • Latest SELECT+ library from Modelithics
    • New simulation-ready sample of the Modelithics COMPLETE library. Please contact Modelithics for instructions on how to use the full version with Genesys2022

Defect and Bug Fixes

  • Fixed an issue with EM Co-simulation used in conjunction with nonlinear devices whose operating points are a function of the DC solution of the EM Co-sim. The Momentum DC solution was incorrectly being modified.
  • Corrected phase noise for the RFAMP_IP2 model.
  • Fixed issue with phase noise at negative frequencies.
  • Fixed issue with equations in Text Balloons not working properly for older workspaces that were being automatically migrated.
  • Compression measurements (COMP, and CCOMP) now work for the Circuit Link and X-Parameter models.
  • The OIP3_OneTone and IIP3_OneTone measurements now provide an estimation of the IP3 for Circuit Link and X-Parameter models. The 2F1-F1 intermod products are not available in a Harmonic Balance simulation and therefore cannot be used to predict IP3 for a Circuit Link part. However, the 3rd harmonic can be used to provide a less accurate estimation which is better than providing no estimation.
  • The Volterra/Harmonic Balance selection logic for Circuit Link has been updated and has an improved user flow.
  • Fixed crash in System Analysis simulations when an S-Parameter model with one grounded port was used inside a subnetwork.

(W5300B) PathWave RF Synthesis (Genesys) Core

Python Script

  • Python is available as a scripting language in Script objects. It requires python 3.8 to be installed separately. The python library matplotlib is not supported by python script objects in Genesys.
  • External python scripts can now access datasets from Genesys workspaces using the svepythonapi module. 
  • The script processor was obsoleted. The scripting language can be selected from the right-click menu of the script object. Text output from a script is directed to the Output Window instead of the Script Processor.

Monte Carlo

  • The Monte Carlo dataset now reports each parameter settings in its own variable.
  • Added option to Run Single Round, which will reproduce the results of a certain round, e.g. round 73 out of 100 rounds, without running the first 72 rounds. The assumption is that the Seed value has not changed. This enables troubleshooting corner cases in a Monte Carlo analysis.
  • Added option to Capture all Dataset Variables, which will store all variables from the underlying analysis in the Monte Carlo dataset.


A new version of the getinterpdata function has been added, providing a much-simplified method to lookup a value in a variable from its independents. For example, if Power depends on frequency and time, the call getinterpdata( Power, [11e6, 7e-6] ) will look up the Power value at 1MHz and 7us. The values do not need to be present in the indeps; the function performs linear interpolation or extrapolation as needed (a second return value indicates the method used).

Known Issues 

  • The Modelithics SELECT library part: AMPXP_QOR_RF2878_001_S works correctly using Linear and Harmonic Balance. However, there are errors when using this part in a System Analysis.
  • In some cases, the installer fails to determine that a system reboot is required. If you run Genesys after such an installation, it will most likely crash during startup. Reboot the system and then run Genesys.
  • The Momentum Mesher returns warnings for vias. This message can be ignored as the accuracy of the simulation is not degraded. 
  • Genesys 2018 and later versions are not recognized by ADS 2016.01 or earlier versions of ADS when Using the ADS Link. You need to install ADS 2017 or later versions in order to use the ADS link.
  • If you encounter an error indicating "MATLAB Script engine failed to run" during Genesys startup, make sure the installed version of Microsoft Visual C++ 2005 Redistributable (x64) is 8.0.61000 or higher. You can download and install the latest Microsoft Visual C++ 2005 Redistributable (x64) from Microsoft Visual C++ 2005 Redistributable Package (x64). Note: Please contact Microsoft, if the link does not work.
  • Some issues with plot legends not always being created properly have been observed with MATLAB R2017b under some rare conditions so MATLAB R2018a is recommended when using MATLAB Script in Retail MATLAB mode.
  • MATLAB R2018a is unsupported in Genesys if the current Windows user name contains non-ASCII characters. Use an earlier version of MATLAB, or an ASCII-only user name. Contact support for other possible workarounds.
  • Issue: 3D visualization does not work properly when McAfee antivirus is installed.

    Workaround: You need to disable the McAfee antivirus to make the 3D visualization work.

  • Some dialogs may not render properly on Windows machines using 150% scaling.


Licensing and Installation


  • Genesys requires: a) the version 2021.02 of the EEsof EDA licensing software, b) a minimum code-word version 2021.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 2021.02  Genesys will not start if any of these requirements is not met. Refer to the License Codeword Version Compatibility Table.
  • In the EEsof EDA License Tools version 2021.02, licensing vendor daemon (agileesofd) is integrated with FlexNet FNP version (Windows) and FlexNet FNP version (Linux) of FlexNet license manager daemon (lmgrd). For the Windows platform, Genesys installer will automatically set up these two new license server daemons by default for the local node-locked license users; for the Linux platform, you need to follow the Setting Up Licenses on Linux instruction to complete the licensing configuration process. For more details, refer to Licensing (For Administrators).
  • Genesys does not automatically release licenses after checking out. From Genesys 2014.03 onwards, click Action > Release All Simulation Licenses option is available to manually release all checked out simulation licenses.

Known Issues

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

  • Unable to install Licensing Hardware Key Drivers on Windows.

  • Workarounds:

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

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

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

  • You may observe issue in recognizing more than one FLEXID on Linux platform with the 2020.02 license tools.
    Workaround: Consolidate your licenses to one FLEXID and configure the same.
  • Setting FLEXLM_DIAGNOSTICS to the highest level (FLEXLM_DIAGNOSTICS=3) on Windows client may cause a crash during license checkout. Flexera is investigating this issue.
    Workaround: It is recommended not to use the FLEXLM_DIAGNOSTICS on Windows clients or use it at lower level (FLEXLM_DIAGNOSTICS=1 or FLEXLM_DIAGNOSTICS=2).
  • WibuKey 6.5 software driver is not supported on SuSe 11.
    Workaround: Use the older WibuKey 6.30 software driver (WkRt-Lin-6.32.1504-500.x86_64.rpm).

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

    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 v6.10 or v6.11 is found and experience this problem then upgrade the WibuKey drivers to v6.30/6.30b from Wibu Systems.
  • Unable to install Flex-10 driver if Flex-9 dongle is already plugged into a machine
    Workaround: Before installing a Flex-10 driver for the first time, unplug the Flex-9 dongle.
  • There is a known FlexNet Publisher issue, whereby mixing node-locked codewords and floating codewords in one license file can result in: a) Remote simulations not working or b) A second local simulation not working in case the license is node-locked and also has incorrect version.
    Workaround: It is strongly recommended that you do not mix node-locked codewords and floating codewords in one license file nor in any configuration that ends up with node-locked codewords and floating codewords both available on the same server. In other words, put the node-locked license and the floating license on different servers, and point to the respective one based on what you need to run.
  • If a user simultaneously runs two instances of a product and has mixed different versions of the same codeword on one license server, extra licenses may be pulled and result in unexpected “Licensed number of users already reached for this feature” errors.
    Workaround: We recommend you remove expired codewords, to separate out the new and the old versions of codewords into different files and different servers, and to point to the respective one based on what you need to run.
  • Not specifying the TCP/IP port for the license server during license setup may lead to unexpected behavior and/or license checkout failure on the Windows platform. We strongly recommend you to always explicitly specify the TCP/IP port associated with each license server.
  • A node-locked and floating bundle operating on Linux cannot be shared between products using EDA License Tools version older than 2014.01 when run at the same time.
  • License Setup Wizard does not remove any previous user-configured FLEX Windows License Service manually set up by a user using FlexNet's lmtools.
    Workaround: You must remove the previous user-configured Windows License Service via lmtools.
    • Run the lmtools.exe from C:\Program Files\Agilent\EEsof_License_Tools\bin to invoke the lmtools utility. The lmtools utility window is displayed.

      If you have installed an EEsof product released before 1st August, 2014 on your system prior to installing an EEsof product released after 1st August, 2014 then the default EEsof Licensing tools path will remain C:\Program Files\Agilent\EEsof_License_Tools. On the systems that only have EEsof products released after 1st August, 2014 installed then the default EEsof Licensing tools path will be C:\Program Files\Keysight\EEsof_License_Tools.

    • In the Service/License File tab, check the Configuration using Services option. All user-configured FLEX Windows License Services will be listed.
    • Select the service you wish to remove.
    • Select the Config Services tab and click the Remove Service button to remove the service.
      To ensure that the license service or lmgrd is running, click View Log. A log window appears that confirms whether agileesofd and lmgrd are up and running.
  • While running multiple versions of prior Genesys releases together, set GENESYS_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 GENESYS_LICENSE_FILE.
    Workaround: You can use GENESYS_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.

Fixed Issues

  • The issue related to the vendor daemon agileesofd could sometimes crash while the License Manager and the Product Selector was running on a remote Windows 8 machine has now been fixed with the newer FlexNET publisher 2015 (also known as version 11.13.1) that is automatically installed by the Genesys installer. 

  • No labels