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

 

  

Main Support:       Knowledge Center
Documentation:   SystemVue English Doc   >  sv2020update1   >  PathWave System Design (SystemVue) 2020 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

PathWave System Design (SystemVue) 2020 Update 1.0 Release Notes

Enhancements

Data Flow Analysis/Models

  • Added new parameter to ReadSignalStudioFile to allow the user to playback the normalized or unnormalized file (this only applies to files generated by SystemVue or ADS).
  • Added support for overlapped subarrays in models BeamformerWeightsSplitter_M, and Combiner_M, which allow one element to be used by multiple subarrays. It enables the generation of multiple beams in a single simulation.
  • AntennaArrayTx/AntennaArrayRx models can now specify polarization using Etheta/EphiLHC/LHC, or Ellipse Axial Ratio and Tilt Angle when Element Pattern Type is set to IsotropicThree Sector Antenna for Y-Z URA, or Cosine Antenna.
  • AntennaArrayTx model can now decompose far-field envelope signal (Output port) into any one of the polarization pattern component pairs Etheta/EphiEleft/ErightEco/EcrossLudwig 2 (Az/El)Ludwig 2 (Al/Ep)Ludwig 3 (H/V) (Polarization1Output/Polarization2Output ports).
  • AntennaArrayRx model now takes into account Element Pattern Polarization when computing output envelope matrix signal but still assumes each element is perfectly matched (in polarization sense) to the incoming signal.

Phased Array Analysis

  • Made complex polarization patterns available in the dataset of Phased Array Analysis (see variables ArrayMeas_Polarization1_ComplexPattern and ArrayMeas_Polarization2_ComplexPattern). Previously, only their magnitude was available in the dataset (see variables ArrayMeas_Polarization1_Pattern and ArrayMeas_Polarization2_Pattern).
  • Added support for easy creation of Beam Pattern UV Plot graphs and Beam Pattern Cut (Theta/Phi/U/V) graphs (see Easy Graph Plotting of Beam Patterns).

RF_Link Simulation

  • Delay introduced in each path (due to filter transients) is now available in the dataset with the extracted behavioral data (see variables PathDelay and PathDelayInSamples).
  • Added support for the VarAmp and ATTN_Ctrl models (see example Examples\RF Architecture Design\VarAmpAGC_RF_Link.wsv).

System Analysis/Models

  • The Frequency Comb source now supports phase noise.

Platform

  • Added support for setting axis' range and units for 3D Graph.
  • A new improved error window allows the filtering of messages based on type (Error/Warning/Message) as well as associated workspace item type (Analysis/Design/Equation/etc.) (see Error Log).
  • The Parameter Synchronization Tool enables easy comparison and synchronization of the matching model or design parameters. Both parts and design parameters can be synchronized.  Either (1) select one or more parts on a schematic, right-click, and select "Sync Part Parameters..." or (2) select one or more designs in the workspace tree, right-click, and select "Sync Design Parameters...".
  • New 3D graph visualization palettes, including standardized ones like: inferno, viridis, and cividis.
  • New graph color themes, including dark, light, and PathWave palettes, which are found in Tools > Options > Graph.

5G Advanced Modem Library

  • All features conform to V15.4.0

  • New functions

    • Downlink
      • Supported NR DownLink frame synchronization method using CP+DMRS.
      • Supported user-defined Bandwidth setup in NR Downlink source and receiver.
      • Supported VSA setup file generation for MIMO configuration.
    • Uplink
      • Supported user-defined Bandwidth setup in NR Uplink source and receiver.
  • EVM function update (NR_DL_EVM and NR_UL_EVM)
    • Supported user-defined Bandwidth setup.
    • Updated NR DownLink EVM model to support MIMO measurements. 

    • Updated NR EVM model to support composite Magnitude and Phase error measurements.

    • Updated NR EVM model to support EVM Window and Symbol Timing setup.

  • Test Models update
    • Updated NR DownLink Test Model example (NR_DL_TM.wsv) to support the latest Test Model defined in 38.141-1 / 38.141-2 of version V16.1.0 (2019-09).

WLAN 802.11ax Library

  • All features of 802.11ax library comply with 802.11ax PHY in the IEEE P802.11ax/D1.2, April 2017 specification.
  • Added new 802.11ax receiver subnet WLAN_11ax_Receiver. It can demodulate 802.11ax waveform to get the outputs of Constellation, Channel coded bits and MPDU bits.
  • Supported 80+80MHz bandwidth in 802.11ax source and EVM model.
  • Added the CombineEqualizerUsingLLTF,  CompensateSamplingClockErrorRemoveEqualizerPhaseRampActiveAntennaThresholdTrackingModeEqualizerSmoothing, and EqualizerSmoothingLength parameters for WLAN_11ax_EVM model to be consistent with VSA 89600.
  • Added two new examples for 802.11ax BER and FER simulation:
    • Examples\Baseband Verification\WLAN\WLAN_11ax\WLAN_11ax_Rx_AWGN.wsv
    • Examples\Baseband Verification\WLAN\WLAN_11ax\WLAN_11ax_Rx_Fading.wsv
  • Added three new examples for 802.11ax VTB simulation.
    • Examples\VTB\WLAN_11ax\Tx\WLAN_802.11ax_Source.wsv
    • Examples\VTB\WLAN_11ax\Tx\WLAN_802.11ax_Tx.wsv
    • Examples\VTB\WLAN_11ax\Rx\WLAN_802.11ax_ReferenceSensitivity.wsv

Radar Baseband Verification Library

Example and Folder reorganizations: 

  • <Electronic Warfare>
    • Proposed globally accepted EW classifications (ES, EA and EP) from reference textbooks.
    • Renamed existing EW examples with the newly proposed EW classifications.
    • ES_ChannelizedTx/Rx are combined as one example.
    • ES_DOA angle measurement examples are combined and updated for usability.
  • <Environment Modeling>
  • <Obsolete Examples>
    • Contains old examples that R&D will cease to support after 2020U1 release.
  • <PhasedArray Performance Modeling>
    • Radar_PhasedArray_DataFlow.wsv
      • Demonstrates phased array RF impairment modeling using DataFlow simplified amplitude and phase shifting.
    • Radar_PhasedArray_SpectraSysRFLink.wsv
      • Demonstrates phased array RF impairment modeling using Phased Array RF_Link and Spectrasys phased array RF models.
      • Customized RF impairment modeling using ADAR1000 frequency-dependent chipset model is available for user evaluation.
    • ADBF (Adaptive Rx Beam Forming) Example updated for improved usability.
  • <Radar System Design>
    • Updated AntennaTx/Rx based pattern plotting example and scanning example.
      • AntennaTRx_BasicTest.wsv
      • AntennaTRx_Scan_Modes.wsv
    • Established new Monopulse Phased Array Radar Tracking And Scan Example Workspace (PhaseArrayRadar_TAS.wsv):
      • Realized monopulse phased array radar scanning with predefined beam grids.
      • Realized simplified radar target tracking workflows for multiple moving targets.
      • Dynamic display of the workspace include
        • Antenna scan and target detection confirming with beam grids
        • Phased array antenna beam patterns
        • Target tracking trajectories plotting
  • <Signal and Data Processing>
  • <Signal Generation>
    • Moved the "AmbiguityFunction" example folder into this folder.
    • Established the "Phase_Coding_Signal.wsv" example which shows how to generate the phase coded signals, including Barker code, PRN code, ChirpLike code (Frank Code, P1 to P4 and Px Code) and PolyTime (T1(n), T2(n), T3(n), T4(n)) example folders. Also enhanced parameter setting and example note.
    • Modified the "CW_Signal.wsv" example with parameter setting and example note enhancements. Single-frequency CW signal generation case is added.
  • <TR Module Modeling>
    • Radar_RF_Modeling_SingleTRx.wsv
      • Presents a simplified single channel Tx and Rx RF impairment modeling.
  • The original examples and the new ones added for 2020U1 are all reorganized inside these folders. The help documentation is also updated for this change.

Multiple Ray Tracing for Automotive Radar Complex Scenario Analysis

  • Enabled "Phase Center" checkbox in antenna array pattern import tab to enable the user to include element spacing incurred phase shifts in antenna patterns.

Documentation

  • Reorganized and consolidated all Sys-Parameter related documentation section under the Using SystemVue > Sys-Parameters section.

Fixed Issues

Data Flow Analysis/Models

  • Fixed issue with AntennaArrayTx model, which ignored E-phi component when pattern files in HFFS, CST format were used.

RF_Link Simulation

  • Fixed issue with modeling accuracy of the RF system phase response when the magnitude response was almost flat. This issue was causing incorrect (better than expected) EVM results. This may result in longer delays being introduced in the RF path modeled compared to previous releases.

System Analysis/Models

  • Fixed issue with incorrect intermods after mixer and amplifier with a frequency comb as the input signal.
  • Fixed issue with IM2 term of f1-f2 not showing up in power spectrum with a frequency comb as the input signal.
  • Fixed issue with Multisource part dialog corrupting the descriptions of the individual source signals defined when more than one source signal was added.
  • Fixed issue where TIMCP3 measurement with frequency comb input signal did not match TIMCP3 measurement with equivalent multi-carrier input signal.
  • Fixed issue with mixer generating a higher than expected DC IM2 component.

Automotive Radar System Design Library

  • Fixed issue with gain and Uni/BiDirectional Raster scan output signal inconsistencies for AntennaRx model compared with AntennaTx model (same issue fixed prior to the System Design (SystemVue) 2020 release).
  • Fixed issue with Bi/UniRaster Scan false output issues of AntennaPolarizationTx and Rx model as compared with AntennaTx model (same issue fixed prior to System Design (SystemVue) 2020 release).

Radar Baseband Verification Library

  • Fixed issue with gain and Uni/BiDirectional Raster scan output signal inconsistencies for AntennaRx model compared with AntennaTx model (same issue fixed prior to System Design (SystemVue) 2020 release).
  • Fixed issue with Bi/UniRaster Scan false output issues of AntennaPolarizationTx and Rx model as compared with AntennaTx model (same issue fixed prior to System Design (SystemVue) 2020 release).

Multiple Ray Tracing for Automotive Radar Complex Scenario Analysis

Fixed issue with the amplitude error issue in MRT GUI:

  • The AutomotiveRadar_RayTracing_SignalVerification.wsv example is modified accordingly, with Ae_Term (Lamda^2/(4*pi))) additions in all Rx channels (Now both the returned power and standard PEC sphere RCS agrees well with theoretically calculated values). The RayTracing Channel code and .bin file are also updated for the missing sqrt(1/(4*pi)) for this fix.
  • The AutomotiveRadar_RayTracing_Demo.wsv example is modified accordingly, with Ae_Term (Lamda^2/(4*pi))) additions in all Rx channels. The .bin files both for the double-car scenario and complex scenario are also updated due to this fix. 

Known Issues

  • On windows machines with an integrated video card (Intel UHD Graphics) and dedicated video card (NVIDIA or Radeon), there is a known issue where 3D graphing in PathWave System Design (SystemVue) may crash the product. To see if you have more than one video card available, run Device Manager, and look under Display Adapters. The workaround is to disable the integrated video card and use the dedicated card by default. In the control panel for your video card, find the 3D application settings and set them to high performance.
  • After upgrading to PathWave System Design (SystemVue) 2020 Update 1, schematic path annotations that contain buses may not display all of the expected information until the analysis is re-run and saved, due to a change in workspace format. 
  • If you encounter an error indicating "MATLAB Script engine failed to run" during 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).
  • 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 PathWave System Design (SystemVue) if the current Windows username contains non-ASCII characters. Use an earlier version of MATLAB or an ASCII-only username. Contact support for other possible workarounds.
  • FlexDCA_Sink does not work with FlexDCA version A.05.71.24. You can use version A.05.63 or prior, or use the version newer than A.05.71.24.
  • Some dialogs may not render properly on Windows 7 machines using 150% scaling.
  • If you see an error like "Undefined function 'log2' for input arguments of type int32" when running a 5G NR workspace, you need to replace the error model with the model from part library selector.

  • The X-Microwave Parts Library has a known issue with their mixers used in the IF port in and RF port out configuration. Fixing this will require a library update from X-Microwave that could not fit in the SystemVue2020 Update1.0 release. Two workarounds to use their models:

    1. Always use the X-Microwave mixers with the RF port as the input and IF port as the output. Many of the X-Microwave mixers have identical IF/RF input characteristics.

    2. Place a MIXER_TBL component that is built-in to the Spectrasys library and use the Param-Sync tool to transfer the parameters from the X-Microwave part. In this case either the RF or IF port can then be used as the input port and verify that the 'Use Table for LO Harmonics Only' checkbox is on the correct tab. 

Licensing and Installation

Licensing


  • SystemVue 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  SystemVue 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, SystemVue 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).



  • PathWave System Design (SystemVue) does not automatically release licenses after checking out. From System Design (SystemVue) 2013.08 onwards, Action > Release All Simulation Licenses option is available to manually release all checked out simulation licenses.

Known Issues


  • 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 SystemVue releases together, set SYSTEMVUE_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 SYSTEMVUE_LICENSE_FILE.
    Workaround: You can use SYSTEMVUE_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 SystemVue installer. 




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