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

 

  

Main Support:       Knowledge Center
Documentation:   SystemVue English Doc   >  sv2020   >  SystemVue 2020 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

SystemVue 2020 Release Notes


Enhancements

5G Advanced Modem Library

  • All features are updated to conform to v15.4.0
  • New functions
    • Downlink
      • System bandwidth configuration by Resource Grid parameters
      • Soft MLD algorithm is provided to PDSCH demodulation for better performance
      • HARQ support when Numerology=15kHz or 30kHz
      • Manual setup for frame synchronization in terms of time delay and frequency offset
      • Resource Allocation Type 0 in TX
      • PDCCH information bits decoding
      • CSI-RS generation in TX
      • VRB-PRB mapping
      • VSA setup file generation is updated to include new necessary parameters
    • Uplink
      • System bandwidth configuration by Resource Grid parameters
      • Soft MLD algorithm is provided to PUSCH demodulation for better performance
      • Resource Allocation Type 0 in TX
      • PUSCH frequency hopping
      • SRS generation in TX
      • PUCCH format 1/3/4 in TX
      • UCI transmission on PUSCH in TX
      • PRACH generation in TX which supports intermediate data output
      • Support assigning only 1 OFDM symbol for PUSCH in TX.
      • VSA setup file generation is updated to include new necessary parameters
  • EVM function update (NR_DL_EVM and NR_UL_EVM)
    • Consistent demodulation performance with VSA 2019 Update 1
    • Resource Allocation Type0 is supported
    • CSI-RS is supported
    • PUCCH format 1/3/4 is supported by the NR_UL_EVM model. The DCPunctured parameter has been added. When DCPunctured is enabled, the DC subcarrier is excluded from measurement results. This is often helpful to avoid obscuring measurement results with artifacts of LO feedthrough
    • Advanced EqualizerTrainingTimeAverage and EqualizerTrainingFreqMovingAvgSize parameters are added. They are a per-carrier setting for specifying how to perform a time-averaging and a moving average (frequency smoothing) on the reference signal subcarriers during equalization.
  • New OTA measurement workspaces
    • NR_UE_OTA_EIS.wsv illustrates Reference Sensitivity and EIS Coverage measurements
    • NR_UE_OTA_ACS_Blocking.wsv demos ACS and In-band Blocking measurements
  • Test Models Support
    • NR_DL_TM.wsv and NR_UL_TM.wsv are added to support test models
  • Other workspaces/designs added
    • NR_UL_PRACH.wsv is created to illustrate generating PRACH waveform
    • NR_PolarCode_BLER_Measurement is created to help to analyze Polar code performance
    • Two HARQ relevant designs for SISO and MIMO performance simulation are added for reference: “07 SISO AWGN HARQ Case” and “08 MIMO 2x2 HARQ Case” are added to NR_DL_Throughput workspace
  • Usability enhancement
    • 5G NR GUIs for downlink and uplink parameters configuration are added to make simulation setup more intuitive and thus easier to learn and use
    • RBG bitmap information is posted into the log when the Resource Allocation Type is Type0 to help inspect the resource allocation

 Back to Enhancements

DPD Baseband Verification Library

  • ET PA is supported in DPD_Cosim.wsv, where an Envelop Tracking PA is applied to generated waveform and PAE, ACPR, EVM can be measured.
  • Updated DPD workspaces to support NR DL and UL signals as the source and to support NR DL EVM and NR UL EVM as well.
  • DPD GUI is updated accordingly

Back to Enhancements

VTB Update

  • Three VTB workspaces are provided to apply DPD+ET to help analyze power amplifier's performance: DPD_VTB.wsv, DPD_ET_VTB.wsv and GetShapingTable_VTB.wsv, which are allocated in ..\Examples\VTB\DPD_ET folder
  • Updated VTB of LTE / LTE-Advanced to show more parameters such as payload configuration, resource blocks etc.
  • Added VTB examples of LTE-Advanced Uplink Carrier Aggregation.
  • Added constellation diagrams for VTB of WLAN 11ac and LTE-A NB-IoT. 
  • Improved error message reporting of the existing 5G NR / LTE / LTE-Advanced / WLAN VTB

Back to Enhancements

EVM Kernel Update

New EVM kernel package (1.148) consistent with VSA 2019 Update 1 is supported.

The new kernel mainly has updates for 5G NR library including:

    • Speed Optimization. Optimize PSS initial detection part. Currently, it can calculate correlation just for SSB parts
    • Speed optimization. 1. Apply freqOffset() to SSB blocks instead of whole frames. 2. use conjFlip of PSS instead of PSS which missed the first point to do correlation calculation
    • Fixed PDCCH resource mapping when CORESET RB start is not integer multiple of 6
    • Make sure PDSCH is located within the BWP when PDSCH RB start is relative to CORESET RB start in non-interleaved VRB-to-PRB mapping
    • Support non-interleaved VRB-to-PRB mapping for PDSCH transmissions scheduled with DCI format 1_0 in a common search space. A CORESET based PRB offset (N_start_CORESET) should be applied during the mapping
    • For DCI decoding, set UL/SUL bit to the lase bit of DCI Format 0_0
    • Fixed CORESET RB start relative to CRB0
    • Fixed peak EVM output when all PHY channels are excluded from EVM calc
    • Update UL spectrum flatness FR2 test limit to match with June version of the standard (38.521-2 ver15.3)
    • Speed up PDCCH Auto Detection
    • Update and fix an issue on processing DCI info
    • Update payload size calculation in PDCCH Auto Detection
    • Fixed a calculation of power adjustment for in-band emissions
    • Support power adjustment for an inband emission test
    • Fixed in-band emission issue
    • Fixed the defect that each pxsch config should use its own activeDMRSFlag
    • Fixed the constellation scaling issue when no eqbuild and tracking is applied for MIMO case
    • Update PDCCH Auto-Detection. 1) Fix a mistake on DCI Format type. 2) Skip DCI search if there is no power
    • Fixed a defect on PDCCH auto-detection with multiple PDCCHs
    • Fixed PDCCH Auto Detect crash
    • Fixed uninitialized variable issue which may cause NaN SSB EVM results
    • Update PDCCH auto-detect.
    • Fixed the defect of condition number when multiple PXSCH configuration
    • Fixed a memory access violation occurred in PUCCH DMRS generation
    • Output auto-detected PDCCH parameters in "nrPdcchDecodeInfoV"
    • Support mag and phase error calculations
    • Fixed the crash when the filter synthesis fails, the filter length is 0, we should not do the FIR filtering.
    • Fixed frame sync for PUSCH RA type 0
    • Fixed no reference point location on constellation for CSI-RS
    • Fixed Modulation type of PSUCH DMRS with transform precoding is incorrectly labeled as QPSK

There are also some updates for common functions that are used for all the EVM models as below. Hence, it is expected to see some minor difference in EVM result for other EVM models compare to previous SystemVue releases.

    • Fixed the output length calculation of arbitrary resampler
    • Modified the declaration of initializing function in ArbitraryResamplerBlock.
    • Add parameter in resampler to set the skip manually&add frequency estimation before data demodulation&&add channel response means every Gi length symbol in each data segment.

Back to Enhancements

System Analysis/Models

  • Nonlinear parameters such as P1dB, Psat, and intercept points for non-linear models (amplifiers, nonlinear block, and mixers) now support input impedance corrections. 
    What this means is that you can now enter the measured impedance of their device along with the mentioned nonlinear parameters from the datasheet and internally in the simulator, the non-linear parameters will be corrected for the mismatch to provide the expected results for the given non-linear parameters. 
    This addresses an issue when the PortParamType parameter was changed on non-linear devices to use an impedance other than the reference impedance, which resulted in the actual compression, saturation, and intercepts points to be incorrect.
  • Added four new intercept point measurements (OIP3_OneToneOIP2_OneToneIIP3_OneTone, and IIP2_OneTone) which simulate the 2nd and 3rd order intercept points based on a single tone.
    Intermod measurements for Quick Sweeps are improved to use the single tone intercept points that support both 2nd and 3rd orders. Using these measurements also increased measurement accuracy and speed. It is also simpler to use because a 2nd tone does not need to be configured. See examples RF Amp One Tone Intercept Points.wsv and RF Amp Intercept Quick Sweep.wsv.

    The OIP3_OneTone and IIP3_OneTone measurements do not work with X parameters because harmonic balance simulations, needed for X parameters, do not support signals underneath signals and would be considered a colliding tone.



  • The RF_AMP model can now generate higher-order (>3) harmonics and intermods up to 11th order (see examples RF Amp 11th Order Intermods.wsv and RF Amp Intercept Quick Sweep.wsv). The same algorithm used to generate data flow coefficients for 5th, 7th, 9th, and 11th order from PSat, IP3, and P1dB is used in the Spectrasys RF amplifier. Even order intercept points are estimated using measured data of several typical RF amplifiers.

Back to Enhancements

RF_Link Simulation

  • Improved simulation result agreement between Spectrasys and RF_Link.
    • The Spectrasys RF_AMP model is now using the same non-linear polynomial coefficients (for 3rd. 5th, 7th, 9th, and 11th order terms) used by the Data Flow Amplifier model given values for PSat, IP3 (TOIout), and P1dB (dBc1out). 
    • One tone IP3 measurements are added to provide the capability of extracting those parameters needed in the Data Flow model by using only a single tone.
    • There are still some differences in the intermod amplitude levels when the input power is within 10 dB or so of the compression point due to the differences in the way coherency is handled between Spectrasys and Data Flow. See Cosimulation Signal Coherency for additional information.
  • The RF_Link model is now supported in SVE (SystemVue Engine). Since Spectrasys is not part of SVE, SVE cannot characterize the behavior of the RF system and must use characterization data generated by SystemVue. There are new settings in RF_Link to control when the behavioral (characterization) data is generated.  This data should be recalculated whenever there's a change in the RF system or the sampling rate and/or characterization frequency of the RF_Link input signal changes.  By default, the data is always recalculated and will always be up-to-date.
  • Improvements were made to modeling mismatches.
  • RF_Link now supports the MIXER_TBL model and can generate IM products from higher LO and input harmonics that end up falling in the simulation bandwidth.

Back to Enhancements

Linear Analysis

  • The Linear Simulator is now included with the RF Toolkit (Spectrasys and related tools) so that S-parameters can be calculated.


RF design features like stability circles, gain circles, noise circles are not supported. Also, the transmission line or microstrip related features are not available.


Back to Enhancements


  • MATLAB SystemVue Toolbox and associated models (MATLAB_LinkMATLAB_LinkCx, and MATLAB_LinkEnv) allow MATLAB users seamlessly stream data to/from a SystemVue design while in the MATLAB environment (see examples under Examples\Tutorials\Algorithm_Design\MATLAB_Toolbox).
  • Link models can be used to only stream data to SystemVue, only stream data from SystemVue, or both.
  • The SystemVue design is simulated using SystemVue Engine (SVE).
  • MATLAB SystemVue Toolbox provides a function to read variables directly from a SystemVue Engine simulation dataset (adx format).
  • The MATLAB SystemVue Toolbox is only supported on Windows.

Back to Enhancements

Platform

  • Improved the sweep simulation output log to capture information from all simulations run during the sweep. Both distributed and non-distributed simulation logs have been improved.
  • The Parameter Synchronization Tool enables easy comparison and synchronization of matching model or design parameters.  Both part 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...".
  • The Smith Chart graphs are now available to facilitate plotting S-Parameters. This is available for all versions of SystemVue (the RF Toolkit is not required).

Back to Enhancements

Data Flow Analysis/Models

  • The FastCircuitEnvelope and FastCircuitEnvelope_M models now support parameterized FCE files. The FCE file parameters can be set using variables so that they can be swept or tuned.
  • The FastCircuitEnvelope and FastCircuitEnvelope_M models now support setting the Filename parameter using a variable and sweeping it.
  • The ReadFileCx model can now read pairs of real numbers from a ascii file and interpret them as complex numbers.
  • Added reset port to the Modulator and Modulator_M models to allow resetting internal phase accumulator when InputType parameter is set to Amp/Freq.

Back to Enhancements

Link to AGI STK

  • Link to AGI STK (STK_Interface) allows for retrieving data from an STK scenario and bringing it into SystemVue for use in setting up time-varying channel models. This feature used to be provided as a separate add-on. It is now part of the SystemVue installation with much-improved usability (custom GUI) and other features.

Back to Enhancements

Phased Array Analysis

  • Phased Array analysis can now export the directivity pattern to a file that can be read by AGI STK.

Back to Enhancements

Modelbuilder

  • A new example under the Examples\Model Building\C Modeling\Link Third-Party Library folder illustrates how to build a custom model linking to a 3rd party library.

Back to Enhancements

  • A new example under Examples\Instruments\M9410\SignalDownloaderM9410.wsv the illustrates how to download an I/Q waveform into Keysight M9410A VXT PXI Vector Transceiver.

Back to Enhancements

Automotive Radar Library

  • New functions
    • PMCW (Phase Modulated Continuous Wave) system-level analysis example
      • PMCW waveform-based MIMO architecture
      • Hadamard-Matrix-based orthogonal waveform generation
      • Enhance Rx aperture size with the virtual aperture to enhance angle measurement accuracy
    • AntennaTx
      • Retrace Time feature enabled for antenna scan modes
        • Bidirectional Raster
        • Unidirectional Raster
  • Example reorganizations
    • Complex Environment Modeling Examples
      • FMCW_Interference Analysis Example
      • GroundClutter_Guardrail Modeling Example
      • GroundClutter_ManholeCover Modeling Example
      • MicroDoppler Effect Analysis Example
      • PropagationLoss Analysis Example
      • Vehicle Scenario Modeling Example
      • VRU (Vulnerable Road User) Modeling Example
    • Radar Signal Processing Examples
      • Compressed Sensing Example
      • FFT-Averaging Analysis Example
      • MUSIC AoA (Angle Of Arrival) Analysis Example
      • Phase Difference AoA (Angle Of Arrival) Analysis Example
    • Radar System Design Examples
      • Basic FMCW Radar Example
      • FMCW Radar SISO (Single-In-Single-Out) Analysis Example
      • FMCW TDM-MIMO (Time Division Multiplexing Multiple-In-Multiple-Out) Analysis Example
    • Radar RF Impairment Modeling Examples
      • Phase Noise Modeling Examples
        • Phase Noise Basic Modeling Example
        • Phase Noise Target Masking Analysis Example
      • RF Impairment AoA (Angle Of Arrival) Impact Analysis Examples
        • Transceiver + Signal Processing System-Level (Transmitter with 2-Level Up-Conversion Architecture) Analysis Example
        • Transceiver + Signal Processing System-Level (Transmitter with VCO based Architecture) Analysis Example
    • Other Examples
      • Automotive Radar 3D Scan Example
      • Multi-Target Detection Analysis Example
      • Phased Array Transmitter Modeling Example
      • Flexible Waveform Generation Example

Back to Enhancements

Radar Baseband Verification Library

  • New functions
    • AntennaTx
      • Retrace Time feature enabled for antenna scan modes
        • Bidirectional Raster
        • Unidirectional Raster

Back to Enhancements

Multiple Ray Tracing (MRT) Complex Scenario Modeling Library

  • To address the complex environment modeling headache
    • 3D Scenario Display with built-in 3D CAD target library
    • Multiple-Ray-Tracing (MRT) algorithm(s) based radar echo generation
    • Signal processing capability integrated with dataflow examples
  • Multiple Ray Tracing GUI highlights
    • OpenGL based 3D-display of complex scenario with built-in target library
      • Vehicles: sedan, trucks, bus
      • Pedestrians: male adult, female adult, children
      • Other targets: road, guard-rails, buildings, lamppost, road-sign, manhole cover
    • Easy-to-Use complex scenario configuration panel (position, velocity, dynamic preview)
    • Radar parametric design (FOV, Polarization, Freq, Boresight Direction) and PRI/CPI compatible timing configurations
    • Raytracing parametric design (Ray Density, Bouncing Number, Ray Amplitude Threshold) for simulation complexity configurations 
    • Built-in Ray Output simplification algorithm, 100% integrated with Raytracing based Scenario Modeling Signal Processing Examples
    • Hands-on help documentation giving instructions from scratch
  • MRT based Scenario Modeling Signal Processing Examples
    • MRT algorithm verification example
      • Radar echo signal verification with standard PEC sphere-based scenario
    • MRT complex scenario analysis example(s)           
      • Double-Sedan Simple Scenario Analysis Example
      • Busy-Intersection Complex Scenario Analysis Example
    • Key Differentiators demonstrated by MRT examples
      • Complex scenario target range/doppler mapping
      • Scatter mapping enhancement from Point-Scatter (W1908) to Scatter Point Cloud (W1725)
      • MIMO architecture based system-level signal flow design with an antenna array and element radiation pattern importing capability

Back to Enhancements

Documentation


Starting with the 2020 release, the online help gets a new user interface. The new UI improves overall online help usability by providing the following key benefits in addition to several other minor benefits:

  • Table of Contents Sidebar: Displays collapsible Table of Contents for the entire documentation. The left-double-arrow icon collapses the sidebar, and the right-double-arrow icon displays the sidebar back again.
  • PDF Button: Allows you to instantly generate PDFs of the latest documentation anytime, including current page’s children pages. Currently, the PDF generation option is available only for SystemVue 2020 release. For the previous releases, you can switch to their Printing Manuals page and download the existing PDFs like earlier. Note that with the introduction of PDF generation feature, the Printing Manuals page will not be available from next release onward.
  • Product Release Switcher: Allows you to view the current page in other supported releases listed in the drop-down menu. Once you select a release from the drop-down menu, the current page is updated to show the content applicable to the selected release. The Table of Contents is updated as well. With this, you bookmark URL of only one release and then switch to other releases from this drop-down menu.
  • Latest Documentation: The documentation available in the new UI is always kept updated for all supported releases. These updates are available to you as soon as they happen at our end. This provides you 24x7 access to the most recent and technically accurate documentation.

For more details, see How to Use Online Help.


Back to Enhancements

RF Libraries

  • The Analog Devices RF parts library has been updated
  • The Custom MMIC RF parts library has been updated
  • The X-Microwave library has been updated. The old X-Microwave library is now obsolete but has has been left in the product to allow workspaces created with prior versions to be loaded and simulated. Several changes have been made to the X-Microwave library. They are listed as follows:
    • All parts are now in a single library. There are no longer individual libraries for each X-Microwave component vendor.
    • The default symbol is now the system behavioral symbol.
    • Each part now has a SymbolMode parameter which defaults to the system behavioral symbol. The user can change this to Hybrid where a physical representation that corresponds to the purchasable X-Microwave block. This can be extremely valuable as the final schematic will very closely represent the X-Microwave hardware. NOTE: The schematic connectivity may break and the respective symbol pins may be in different locations that may also require schematic rewiring. The most effective way to use these parts is to change the symbol, if so desired, before wiring the part.

Back to Enhancements


Fixed Issues

Data Flow Analysis/Models

  • Fixed issue with AddNDensity model producing higher noise level in "Noise density vs freq" mode when a rectangular noise density profile is given.
  • Fixed issue with FastCircuitEnvelope and FastCircuitEnvelope_M models producing an error although the input signal characterization frequency matched the characterization frequency for which the FCE model was extracted.
  • Fixed issue with ReadSignalStudioFile model not being able to check out a valid floating license for a waveform generated by N7631C 5G NR Signal Studio (Version 3.0.0.0).

System Analysis/Models

  • Fixed issue where an undesired signal at the same frequency as the desired signal would disappear when the signals passed through a mixer and the undesired signal would not be included in the UDCP measurement.
  • Fixed issue with interpolation of S-parameter data resulting in incorrect results.
  • Fixed issue where for a wideband input signal placing a filter before or after a linear amplifier resulted in 3 dB difference in output signal level.
  • Fixed issue with NonLin model using RevIM parameter incorrectly.
  • Fixed some phase noise coherency issues associated with split paths, mixers, then combined back together when the phase noise was only on the input signals.

RF_Link Simulation

  • Fixed issue where in some RF_Link simulations of RF systems with more than one mixers in cascade the simulation would error out with a message complaining about the mixer having a real baseband signal at its input.

Platform

  • Fixed issue with workspace variables set using VB scripts not retaining their values after workspace is saved and reloaded.

Changes to existing behavior

System Analysis

  • Removed Volterra option from System Analysis (Calculate tab). 
  • The default stage value for intercept, compression, and saturation points was increased from +100 dBm to +200 dBm to support Passive Intermod (PIM) simulation and analysis.

HDL Cosimulation/Code Generation

  • Support for Aldec RivieraPro is DISCONTINUED.

Data Flow Models

ReadSignalStudioFile

Signal Studio files (wfm extension) can be generated using:

  1. Signal Studio
    a) for the older formats, these files do NOT include the carrier frequency information
    b) for the newer formats like 5G NR, these files include the carrier frequency information in the file header but the file header structure is different compared to the one used for older formats.
  2. ADS or SystemVue; these files ALWAYS include the carrier frequency information in the file header.

Signal Studio files can be read in SystemVue using the ReadSignalStudioFile model.

In prior SystemVue releases, when the ReadSignalStudioFile model was used to read a file generated from Signal Studio (case 1), it would either not find any carrier frequency information (case 1a) or it would fail to read the carrier frequency (case 1b). Then the model would silently use the value of the RFCarrier parameter to set the characterization frequency of its output envelope signal. The RFCarrier parameter is by default hidden and can be made visible if the SetCarrierFrequency parameter is set to YES.

In the current SystemVue release, the above scenario will result in a simulation error of the form "ReadSignalStudioFile 'Design1.R1': Could not read carrier frequency information from the file. Please change SetCarrierFrequency parameter to YES and specify RFCarrier." You must change the SetCarrierFrequency parameter to YES and explicitly set the RFCarrier parameter to the desired value.

There is NO change in behavior for files generated from ADS or SystemVue (case 2).

Known Issues

  • On Dell laptops with an integrated video card (Intel UHD Graphics) and dedicated video card (NVIDIA or Radeon), there is a known issue where 3D graphing in 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 SystemVue 2020, 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) from Microsoft Visual C++ 2005 Redistributable Package (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 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.

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



  • SystemVue does not automatically release licenses after checking out. From 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