Main Support:       Knowledge Center
Documentation:   SystemVue English Doc   >  Previous Supported Releases   >  PathWave System Design (SystemVue) 2021   >  PathWave System Design (SystemVue) 2021 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

Skip to end of metadata
Go to start of metadata

PathWave System Design (SystemVue) 2021 Release Notes


(W4501E) PathWave Comms/DSP Analysis

Multiple Envelope Data Flow Simulation

Data Flow Simulations now support Multiple Envelope signals (similar to Circuit Envelope simulations). The Multiple Envelope signal is an extended data type from the Single Envelope one. It contains a vector of Single Envelope signals [v1(t), v2(t), …, vN(t)]. Each Single Envelope element has its own complex envelope signal ( xi(t) OR xIi(t) + j xQi(t) ) and characterization frequency ( fci ), but all of them have the same sample rate. N is the number of the envelopes for the Multiple Envelope signal. For more information, see Multiple Envelope Signal.

The benefit of using Multiple Envelope signals is that for an RF signal with harmonics and inter-modulation products (usually these frequency components are far away from each other), the sample rate needed to fully represent all complex envelope signals can be in the order of the information bandwidth, which in general is orders of magnitude smaller than the sample rate required for a Single Envelope signal representation.

The following Data Flow models support multiple envelope signals:

  • RF_Link@Data Flow Models
  • Amplifier@Data Flow Models
  • Mixer@Data Flow Models
  • AddNDensity@Data Flow Models
  • SData@Data Flow Models
  • AddEnv@Data Flow Models
  • EnvSelector@Data Flow Models
  • CustomFIR@Data Flow Models
  • All IIR filters with the Envelope data type, including these filter models:
  • BPF_Bessel@Data Flow Models
  • BPF_Butterworth@Data Flow Models   
  • BPF_ChebyshevI@Data Flow Models   
  • BPF_ChebyshevII@Data Flow Models   
  • BPF_Elliptic@Data Flow Models   
  • BPF_SynchronouslyTuned@Data Flow Models   
  • BSF_Bessel@Data Flow Models   
  • BSF_Butterworth@Data Flow Models   
  • BSF_ChebyshevI@Data Flow Models   
  • BSF_ChebyshevII@Data Flow Models   
  • BSF_Elliptic@Data Flow Models   
  • BSF_SynchronouslyTuned@Data Flow Models    
  • HPF_Bessel@Data Flow Models   
  • HPF_Butterworth@Data Flow Models   
  • HPF_ChebyshevI@Data Flow Models   
  • HPF_ChebyshevII@Data Flow Models   
  • HPF_Elliptic@Data Flow Models   
  • HPF_SynchronouslyTuned@Data Flow Models   
  • LPF_Bessel@Data Flow Models   
  • LPF_Butterworth@Data Flow Models   
  • LPF_ChebyshevI@Data Flow Models   
  • LPF_ChebyshevII@Data Flow Models   
  • LPF_Elliptic@Data Flow Models   
  • LPF_SynchronouslyTuned@Data Flow Models   
  • SData@Data Flow Models
  • Sink@Data Flow Models
  • SpectrumAnalyzerEnv@Data Flow Models
  • CCDF_Env@Data Flow Models

    Models with anytype ports: 
    • Repeat@Data Flow Models

    • InterleaveDeinterleave@Data Flow Models

    • Reverse@Data Flow Models

    • Trainer@Data Flow Models

    • Transpose@Data Flow Models

    • DownSampleVarPhase@Data Flow Models

    • DownSample@Data Flow Models

New multiple envelope simulation examples

  • Basic examples (see examples in Examples\RF Architecture Design\Multiple Envelope)
  • 5G NR intermodulation (see example in Examples\Baseband Verification\5GAdvancedModem\Multiple Envelope)
  • WLAN and LTE intermodulation (see example in Examples\Baseband Verification\WLAN\Multiple Envelope)
  • Radar intermodulation (see example in Examples\Radar\Multiple Envelope)

Known issues

  • For the RF_Link model, the Manual Frequency Sweep Setup displayed in the RF_Link GUI is not supported.

  • When RF_Link is simulated with Multiple Envelope Signal, the MIXER_TBL model and MIXER_DBAL model are not supported. If the design has the two models, RF_Link will post an error during multiple envelope simulation.
  • Multiple Envelope signals are not supported in RF_Link_M and RF_Link_PhasedArray models.
  • In the Multiple Envelope simulation, the power levels are less accurate when the amplifier and mixer models work in the compression and saturation area. The power levels may have some differences compared to the ones of a SpectraSys simulation.
  • High orders (larger than 3rd order) components of Amplifier and Mixer have power level difference between a SpectraSys simulation and multiple envelope Data Flow simulation.

(W4503E) PathWave Phased Array Analysis

Phased Array Antenna Enhancements

Sum of Powers

  • Support dual resolution for Phased Array Analysis and BeamPattern by setting Pattern Computation to 1:Entire Space - Dual Resolution. Instead of using a single angular resolution over the entire sphere, it allows users to use a finer resolution in a specified subset of the sphere. Using this option, users can see finer details of beam patterns in a certain range without compromising measurement speed. A new example demonstrating this feature is available in Examples\RF Architecture Design\Phased Array Analysis\PhasedArrayAnlysis_Basics.wsv.
  • Support computation of directivity pattern with a subset of theta/phi angles by setting Pattern Computation to 2:Theta/Phi Range for Phased Array Analysis and BeamPattern. It aims to capture details of narrow beams without sacrificing simulation performance or increasing simulation dataset size. A new example demonstrating this feature is available in Examples\RF Architecture Design\Phased Array Analysis\PhasedArrayAnlysis_Basics.wsv.

  • Support new pattern normalization method, Sum of Input Powers, for Phased Array Analysis and BeamPattern by setting Pattern Computation to 2:Sum of Input Powers. This method is the only normalization option possible when the Pattern Computation is set to Theta/Phi Range around Measurement Direction since in this case we are not computing the pattern for the entire space and therefore we cannot compute its integral. This method of normalization is an approximation and provides good results (close to the ones you would get with the Pattern Integral method) only when there is a low coupling between the antenna elements.

Support Keysight Far-Field IO format

  • Supports FFIO as the element pattern file for Phased Array Analysis and BeamPattern/AntennaArrayTx/AntennaArrayRx/OTA_TestTx/OTA_TestRx models. FFIO is a pattern file generated by RFPro and EMPro. Within a single file, it incorporates the patterns of multiple antenna elements, and for each element, it includes the patterns for multiple frequencies. New examples are available in Examples\Beamforming\BeamPattern.wsv and Examples\RF Architecture Design\Phased Array Analysis\PhasedArrayAnlysis_Basics.wsv.

New Simulation Features and Enhancements

  • Removed the ArrayRadiation parameter in the ArrayAnt model in Phased Array Analysis and the ArrayRadiation and ThetaRange parameters in the BeamPattern model. When computing beam patterns, Upper Hemisphere is obsolete. If you want a beam pattern of the hemisphere, set PatternComputation to '2: Theta/Phi Range (around Measurement Direction)' and configure the Theta Range and Phi Range to hemisphere.

  • Added new result into the data set of Phased Array Analysis, 'Expanded_S_ParameterMatrix'. It is available when both 'EnableScalingSparameter' and 'SaveExpandedSParameters' are set to YES in the ArrayAnt model.

Antenna array and element pattern files

  • Support removal of the array factor included in the imported element pattern files for Phased Array Analysis and BeamPattern/AntennaArrayTx/AntennaArrayRx models. With pattern files for an antenna array, this feature allows you to change this antenna array’s geometry when simulating with SystemVue. New examples are available in Examples\Beamforming\BeamPattern.wsv and Examples\RF Architecture Design\Phased Array Analysis\PhasedArrayAnlysis_Basics.wsv.

  • Enhanced Pattern Data when it is used as the Element Pattern Type for Phased Array Analysis and BeamPattern/AntennaArrayTx/AntennaArrayRx models. New designs are available in Examples\Beamforming\BeamPattern.wsv and Examples\RF Architecture Design\Phased Array Analysis\PhasedArrayAnlysis_Basics.wsv.
    • Allow you to input PatternDataEtheta and PatternDataEphi for a subset of the sphere but not the full sphere as the previous version.
    • Allow you to input PatternDataEtheta and PatternDataEphi for more than one element.
    • Allows the phi grid of Pattern Data to be negative, in the range of -360~360. 

  • Support reading in CST element pattern file with multiple frequencies for Phased Array Analysis and BeamPattern/AntennaArrayTx/AntennaArrayRx models. The simulation is using the patterns specific to the simulating frequency. If the pattern file does not contain the pattern for the simulating frequency, the pattern will be interpolated by the patterns of the two most adjacent frequencies.

  • Support a new option '3:Individual for Each Element with Reorderring', for ElementPatternFileMapOption in ArrayAnt model of Phased Array Analysis; BeamPattern, AntennaArrayTx, AntennaArrayRx, OTA_TestTx and OTA_TestRx model of DataFlow. It allows you to rearrange the file indices of element pattern files. For the detail, please refer to Antenna Element Pattern Parameters.

  • Normalize Polarization patterns output by BeamPattern model and Phased Array Analysis by their own total power instead of the combined total power of two polarization patterns. 

  • Added new options for OutputPolarizationPatterns to allow the BeamPattern model to output two polarization components in complex values.

  • Enhancements for AntennaArrayTx/AntennaArrayRx model
    • Allow AntennaArrayTx/AntennaArrayRx model to convert imported element pattern files from their radiation pattern to its directivity pattern by setting EnableNormalizationElementPattern to YES.
    • Allows you to specify the polarization for input envelope signals in the AntennaArrayRx model. Polarization mismatch is considered when calculating its output.

  • Removed the Polarization Mismatch parameter from OTA_TestTX/OTA_TestRX models. Polarization mismatch naturally exists in OTA test; it is not something that can be disabled.

Datasets and Visualization

  • Added new result into the data set of Phased Array Analysis, 'ArrayMeas_ArrayFactorGainAtThetaPhi', which is the array factor gain in dB for the given direction.

  • Support multiple phi cuts measurement in Phased Array Analysis. Previously, only one phi cut angle is allowed to measure. It's enhanced to support more than one phi cut angle. When setting up Phased Array Analysis, users are allowed to enter a vector in the Phi Cut Angles, for example [30 270]. After the simulation, there will be two traces available in BeamMeas_PhiCutDirectivity. The first column of data represents the phi cut of 30 degrees, and the second column is the one for 270 degrees. The measurements, 'BeamMeas_NullPhi', 'BeamMeas_NullTheta' and 'BeamMeas_NullRatioToMaxLobe' are also performed on each phi cut trace.

Phased Array Data Flow Simulation

Supports Diversity of Channel Noise and Distortion, including Tapering (Channel Specific Amplifiers)

Added support to Amplifier_M for setting nonlinear parameter and noise figure per channel as well as defining channel groups, where channels in the same group share the same nonlinear parameters and noise figure.

Support for Sub-Array Architectures with Overlapping Array Elements

Added support to Splitter_M and Combiner_M models for defining custom sub-arrays with overlapping elements. An example is added to demonstrate this capability, Examples\Beamforming\CustomMapping.wsv.

Fixed Issues

Fixed defect with reading HFSS's pattern file, where precision could be lost when reading very small values. For example, a value of 0.002mV, could end up being read as 0.

  • Fixed error message when both IncidentWaveETheta and IncidentWaveEPhi are set to 0 in the AntennaArrayRx model.
  • Fixed issue in Phased Array Analysis, when "Calculate Intermod and Harmonic Spectrum" is enabled, the change of ZIN of RFAMP would impact the output power of this model. This is not expected. The output power should remain unchanged.
  • Fixed antenna element rotation issue. When all the elements are using the same pattern but their rotation was set individually by a vector, all of them were rotated by the first value in the vector rather than their individual rotations.
  • Fixed issue with beam pattern when Isotropic/Cosine/ThreeSector are used as antenna array's element pattern. When they have both Etheta and Ephi components specified, the composed beam pattern for the antenna array was wrong.
  • Fixed issue with wrong beam pattern in Phased Array Analysis Rx mode with S-parameter applied.

(W48502E) PathWave RF Analysis

  • 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 can also work with third-party tools.

  • Two new examples added to demonstrate this new 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 and VarAmp 

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

  • S Parameter based non linear models like SDATA_NL, SDATA_NL_HO, SDATA_NLI do not support the AM to AM feature

  • There is a NonLinearModelingMode parameter used to enable the AM to AM capability. 

    • The default nonlinear parameter mode supports user-entered non linear parameters like P1dB, PSat, etc

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

Spectrasys Frequency Multipliers

  • Frequency multipliers were 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 called MixOrderMax was 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 a MaxOrder parameter that will limit the maximum intermod and harmonic order created by the model. As a default, the model will use whatever order 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

RF_Link Simulation

  • Added RF_Link model settings during extraction in the behavioral dataset. In "Extract if not found" mode these settings are compared to the RF_Link model settings to determine whether the behavioral data can be used or whether it needs to be regenerated.
  • The input signal with Fc = 0Hz is supported for RF_Link. This feature brings the ability for customers to analyze the entire link performance (both IF and RF) in RF_Link. In other words, the Zero-IF Tx transceiver is supported in RF_Link.
    • With this feature, a lot of applications are enabled. For example, to analyze the link budget of the entire link including both the baseband and RF components, it's expected to support baseband IQ data as input of RF_Link.
      Then, with the IQ input, noise contribution and other impairments along the link can be accounted for in the RF_Link as a whole, which is promising for accurate performance prediction.

Vendor Parts Library

Latest library from X-Microwave

(W4521E) PathWave Radar and EW Library

Electronic Warfare Enhancements:

  • New Example Folder: <EW_EPM> under Radar_System_Design folder:

    • New Example: <EP_Radar_Template_ADBF.wsv>:
      • Re-established from the original Framework_AA example (originally in Three_Layer_Architecture folder) with major modifications.
      • This example is designed as the FIRST TEMPLATE EXAMPLE (for radar simulation) for new user to understand the 3-layer radar simulation architecture;
      • Azimuth-ONLY adaptive beamforming for side-lobe jamming cancellation is demonstrated;
      • The new feature of the <TargetScatterLocation> model with multi-target trajectory and RCS generations by bus output ports is enabled.

    • New Example: <EP_Radar_Template_3DAdapBF.wsv>:
      • This workspace demonstrates the generic radar simulation architecture together with statistical clutter and side-lobe jamming signal modeling.
      • Radar signal processing is presented with Pulse-Doppler MTI + MTD;
      • Side-lobe jamming suppression demonstrations are proposed with 3D (2 dimensions, Azimuth + Elevation) MMSE ADBF adaptive beamforming.  
      • The new feature of the <TargetScatterLocation> model with multi-target trajectory and RCS generations by bus output ports is enabled.

  • New Example: <ES_RWR_Modeling.wsv> under Electronic_Warfare folder:
    • This example demonstrates Radar Warning Receiver (RWR) simulation, as the SECOND TEMPLATE EXAMPLE (for EW simulation) for new user to understand the 3-layer radar simulation architecture;
    • One hostile radar is modeled as an emitter, which is measured by the RWR and the corresponding PDW (Pulse Descriptor Word, including Time Of Arrival (TOA), Pulse Width (PW), frequency, pulse power, etc.) list is generated.

  • New Example: <EA_RGPO_Modeling.wsv> under Electronic_Warfare folder:
    • This example demonstrates EA (Electronic Attack) false-target deception jamming simulation
    • Hostile radar range tracking is realized by range wave-gate tracking, and the design of support/self-protection jamming generation (effect on hostile radar known as Range Gate Pulling Off (RGPO)) is enabled on one fighter plane to protect the friendly-force targets.

  • New Example: <EW_RadarEWRx_Intermod.wsv> under Multiple_Envelop folder:
    • This example demonstrates radar and interference impacts on a specific simplified radar EW receiver;
    • Multiple envelope feature is enabled for Rx RF components, and intermodulated signals realized by the new MULTIPLE ENVELOP feature is presented with impacts on typical pulse parameter measurements of Pulse Descriptor Word (PDW).

RF Impairment Modeling Enhancements:

  • New Example Folder: <ADAR1000_Modeling_Examples> under PhasedArray_Performance_Modeling folder, enables system-level RF impairment modeling capability using commercial wideband chipset ADI ADAR1000:

    • New Example: <ADI_ADAR1000_PhasedArray_RFSim.wsv>:
      • Chipset RF structures precisely modeled using SystemVue Spectrasys RF models;
      • Channel-by-channel complex gain, NF, nonlinearities, and frequency sweeping impairment variations are demonstrated.

    • New Example: <ADI_ADAR1000_PhasedArray_WfmSim.wsv>:
      • Channel-by-channel complex gain, NF, nonlinearities, and frequency sweeping impairment changes demonstrated;
      • The antenna array manifold structure and beam pattern graphs are demonstrated;
      • The system-level waveform distortion evaluation using PhasedArray_RFLink is applied to incorporate chipset RF modeling into dataflow radar simulations.

    • New Example: <ADI_ADAR1000_PhasedArray_EWSysSim.wsv>
      • RF impairment of the ADAR1000 chipset based radar system design presented for both phased array Tx and Rx modes, together with 2-targets and 1-moving EW jammer.
      • For signal processing, PC (Pulse Compression) and PD (Pulse Doppler) results with jamming impacts are proposed to evaluate the system-level echo signal results.
      • Two specific simulation schematics have been designed for user evaluation:
        • ADAR1000 based phased array Tx + Idealized phased array Rx;
        • Idealized phased array Tx + ADAR1000 based phased array Rx.

Generic Radar Simulation Enhancements:

  • New Example: <IFF_Transponder_Modeling.wsv> under Three_Layer_Architecture folder:
    • The Identification for Friend or Foe (IFF) transponder (secondary radar) simulation example is established, in which two transponders are designed to receive the radar signal and send their response signals back to the radar.
    • MATLAB script-based models have been proposed as flexible response generators.

  • New Example: <DDS_SigGen_Examples.wsv> under Signal_Generation folder:
    • DDS LFM generation sub-examples are demonstrated with: 
      • Simplified radar target signal processing (wavegate + pulse compression) designs;
      • The signal generation performance is compared with the CW and LFM models for typical configurations and output time-sampled results.
    • DDS Sine wave generation sub-example is proposed with basic DDS + DAC architectures, with FFT at both DDS and DAC output ports.

Generic Usability Example Enhancements:

  • Major usability enhancements are done to:
    • <PhasedArrayRadar_MultiTargetSearch.wsv> example
    • <ES_DOA.wsv> example
    • <ES_TOA.wsv> example
    • <EW_Noise_CoverJamming.wsv> example
    • <FMCW_DSP.wsv> example

  • Minor usability enhanced examples:
    • <ES_DRFM_SingleChannel.wsv> example
    • <Radar_MPRI.wsv> example
    • <EW_Sequence.wsv> example
    • <Radar_PDW.wsv> example
    • <EW_PulseHopping_Generation.wsv> example
    • <RadarSigProc_Matrix.wsv> (and is renamed from <PulseCompressionMatrix> example)
    • <EP_ADBF.wsv> example.

Model Enhancements:

  • <TargetScatterLocation> and <Platform> models enabled for multi-platform/target trajectory and RCS generations by bus output ports.

  • <CFAR_M> model enables the “OS-CFAR” type for both range and doppler dimension CFAR.

  • <AntennaTx2> model:
    • Documentation improved and is consistent with the <AntennaTx> model.
    • The application differences between these two models are highlighted.

Model Defect improvements:

  • <PhasedArray Tx & Rx> models:
    • Both models fixed for extremely large output signal defect for ULA (element number > 8);
    • <PhasedArrayRx> model is updated to enable the bus size inconsistency error report if ArrayInput port size is NOT consistent with the desired target number.

  • <Platform> and <TargetScatterLoc> models are updated to enable error report if Velocity/Acceleration/Jerk under Simple XYZ Frame is set to vector size other than 3.

  • <CFAR/CFAR_M> models are fixed for inconsistent output data defect if CFAR type == ClutterMap.

  • Parameter range checking fixings have been done to: <CFAR/CFAR_M>, <Ground_Clutter> <RCS>, <Clutter_H>, <TargetScatterLocation>, <TargetTrajectory> models.

  • <DDS> model output timing defect fixed with properly timed output samples.

Example improvements:

  • <AdaptiveArrayCapOn.wsv> example: fixed excessive warning for example.
  • <FMCW_Radar.wsv> example: fixed incorrect doppler frequency shift results.

New radar modeling example with the capability of SVE working in MATLAB. 

The example is accessible under the Examples\Tutorials\Algorithm_Design\Baseband_Link\Radar folder, and three radar examples can be simulated in MATLAB software using the script files in the same location:

1) One simple 1Tx1Rx simulation: <RF_Radar.wsv>;

2) Phased Array modeling simulation: <PhaseArray_Radar.wsv>;

3) Deception jamming simulation: <DeceptionJamming_Radar.wsv>.

Added custom STK Sweep to allow easy sweeping of STK scenario time. All top-level STK parts are swept simultaneously without the need to define a variable to configure each one of them. Note that STK parts in the subcircuits will not be included in this sweep, they have to be at the top level.

Animation time settings have been moved under Advanced Options; leave them blank to load from the scenario.

(W4522E) PathWave 5G and Cellular Library

All supported features are updated conforming to v16.1.0

New functions

  • Downlink
    • PDSCH DMRS update of release 16 in Tx and Rx
    • VSA setup file generation updated supporting PDSCH DMRS update of release 16
  • Uplink
    • PUSCH DMRS update of release 16 in Tx and Rx
    • PUCCH format 3 and 4 DMRS update of release 16 in Tx
    • PUSCH scrambling for msgA in Tx and Rx
    • PRACH generation
      • Supporting IAB-MT (integrated access and backhaul mobile termination)
      • Supporting new random access configurations added in FR1 and unpaired spectrum table
    • VSA setup file updated supporting PUSCH DMRS and PUCCH format 3 and 4 DMRS update of release 16 and PUSCH scrambling setup for msgA
  • Channel model
    • MIMO_FastFadingEngine Model supporting time-variant path delay

EVM function update (NR_DL_EVM and NR_UL_EVM)

    • Consistent demodulation performance with VSA 2020 Update 1
    • Demodulation for PDSCH DMRS of release 16
    • Demodulation for PUSCH DMRS of release 16
    • Demodulation for PUCCH format 3 and 4 DMRS of release 16

EVM Models Update

    • EVM models are updated because of the update on the bebop library. The new bebop library is based on the code set for the VSA2020u2 release (VSA 2020 Update 2.0).
    • EVM results of 5G NR EVM model may change because of bebop code update on the filter without noise, but the results will keep almost the same with noise. And EVM models based on new Bebop code which also internally fixed issues related to filter.
    • There might be a minor difference in other results compared with previous results of EVM models introduced by bebop code updated. 
    • PDSCH with a small number of RBs cases and mixed numerologies with resource grid-enabled cases may not get synchronization correctly. 

New examples

  • NR_Intermodulation_UE_Reception.wsv to demonstrate NR wideband intermodulation of UE receiver in the presence of two interfering signals which have a specific frequency relationship to the wanted signal.
  • NR_DL_Tx_CA.wsv to demonstrate NR downlink transmitter with at most 5 component carriers aggregation and its spectrum, CCDF, ACLR, and EVM measurements.
  • NR_UL_Tx_CA.wsv to demonstrate NR uplink transmitter with at most 5 component carriers aggregation and its spectrum, CCDF, ACLR, and EVM measurements.

Fixed Issues

    • Fixed crash issue in NR DMRS PUSCH model when NR UL Source is set up to Starting OFDM Symbol 2 and Number of OFDM Symbols of 1
    • Added the missing Design Analysis for SISO_AWGN_Fading design in the MIMO_SM_STC_BER example
    • Fixed NR_UL_Numerology_Rcv simulation error when HARQACK is enabled in UCI Multiplexing GUI setup page of PUSCH
    • Fixed range check of CSI1 BitInfoLength and CSI2 BitInfoLength when CSI1 and CSI2 are disabled
    • Fixed CORESET ID setup for PDSCH and DCI payload size setup in VSA setx file generation
    • Fixed Downlink EVM measurements when there is resource collision in PDSCH and PDCCH allocation
    • Updated all NR examples to support a frequency range of 410MHz to 7.125GHz in FR1

(W4523E) PathWave Wifi and Connectivity Library

WLAN 802.11ax 

  • Added a new subnetwork WLAN_11ax_Source_Mu to support different setting of parameter MPDUDataLength_UE for each UE.
  • Added band information of each RU in simulation log posting by WLAN_11ax source.

Bluetooth 5.2

  • Supports 2Msym/s symbol rate for uncoded PHY in Bluetooth LESource, Receiver, and EVM models according to Bluetooth specification V5.0.

  • Support coded PHY in Bluetooth LESource according to Bluetooth specification V5.0.

(W4800B) PathWave System Design Core


  • Added simplified versions for the getinterpdata function. The previous versions will be deprecated in a future release. 

  • Data Set Viewer now limits the amount of visible data to 200,000 rows and 500 columns, or 1,000,000 cells. To view variable larger than this, use formulas to create variables with less data, or filters in the viewer to reduce the amount of visible data.

  • Added buttons in the Probe Configuration tab of OTA_TxTest and OTA_RxTest models to display the probe setup or the probe and array set up on the same 3D plot.


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


  • Added a Beam Pattern Plot Wizard to the right-click menu options for dataset variables to help with plotting 3D Beam Patterns, UV Plots/Cuts, Theta/Phi Cuts for Data Flow Phased Array simulation data.


  • The script processor was obsoleted. The syntax language for a script 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.
  • Python is available as a scripting language in Script objects. but requires a version of python 3.8 to be installed separately for it to work. The python library matplotlib is not supported by python script objects in SystemVue.
  • External python scripts can now access datasets from SystemVue workspaces using the svepythonapi module. 

(W4510E) PathWave DPD Design Kit

3GPP NR test models signal and WLAN 11ax signal are supported in DPD examples and DPD VTB examples.

(W4513E)  PathWave Ray Tracing Kit

MRT 3D Scenario GUI related Enhancements:

  • Long guardrail models (3-Units, 6.1 meters in length, and 7-Units, 21.2 meters in length, respectively) were imported as standard targets to enhance the usability in establishing highway simulation scenarios.

MRT Signal Processing Example Enhancements

  • New Example: < AutomotiveRadar_RayTracing_SignalVerification_CR_FarRange.wsv>
    • This example is created to verify that MRT algorithm accuracy is satisfactory, regardless of calculation frequency and target sizing.
    • This example applies one dihedral corner-reflector with side-length = 0.05m, range is 1000m, MRT calculated RCS value is in close agreement (difference < 0.5 dB) with theoretical value of 10.1 dBsm.

  • New Example: <AutomotiveRadar_RayTracing_CurvedMotion_FileGen.wsv>
    • Using MATLAB script to guide you to generate customized curved motion file for a certain target (Equation ONLY);
    • Detailed equation comments and NOTE are provided in the example.

  • Enhanced Example: <AutomotiveRadar_RayTracing_Signal Verification_NearRange.wsv> 
    • The near range sphere verification example (0.01m radius PEC sphere at 50m) has been demonstrated together with the far-range example (0.1m radius PEC sphere at 1000m) to prove that MRT algorithm accuracy is regardless of target ranges;
    • The calculation accuracy is verified for both cases, the MRT returned EchoPwr, and RCS values are in close agreement with the corresponding theoretical values. 

  • Enhanced Example: <AutomotiveRadar_RayTracing_Demo.wsv>
    • Excessive warnings are eliminated for a better user experience.

MRT 3D Scenario GUI related improvements:

  • Fixed the incorrect display of target height defect:
    • For the last release, if one target height (Y-value) is set to other than half its height and saves the scenario file, reloading this file incorrectly returns the height to the default height of half the target height again.
    • After fixing, reloading the scenario keeps the correct height as in the original user file.

  • Fixed the "back wheels above the ground" defect for all built-in sedan targets.

  • Fixed the very long time MRT GUI opening (first time) defect (> 2min), now it can be opened promptly.

  • Fixed serious defects as the following:
    • MRT GUI hungs if setting steptime == 0 sec;
    • MRT GUI radar timing forceful resetting is annoying to most customers, so reset to StartTime = 0, StepTime = 0.1, and StopTime = 1 secs for easier handling;
    • MRT GUI cannot set one step point to run, whereas all RCS/Echo verification examples are set that way.

  • Fixed the defect of MRT GUI cannot clear the .trb (ray file display) files automatically even if the setting "Clear Results" == True.

Example improvements:

  • All shipping examples have been fixed for excessive warnings and errors.
  • The remaining warnings are assumed to be expected by design and have been explained in example notes.
  • Unzipped the scenario and ray result files for enhanced customer experience.

RayTracing Channel Model Fixings:

  • The Antenna Array Rotation function is Enabled with new parameters in the advanced parameter tab that:
    • Simplified customer operation when trying to align coordinate setup between MRT and RayTracing Channel by enabling Antenna Array Rotation capability;
    • Realized polarization separation of H/V data for imported antenna pattern files;
    • Renamed polarization setting parameters as P1/P2/P1+P2 in case antenna pattern rotations confuse polarization nominations.
  • Imported ray number setting information improved for clearer understanding.

(W4525E) PathWave Automotive Library 

Model Enhancements:

  • <TargetScatterLocation> and <Platform> models enabled for multi-platform/target trajectory and RCS generations by bus output ports;

Environment Modeling Enhancements:

  • <AutomotiveRadar_GroundClutter_Guardrail.wsv> example: the “curved velocity of multiple guardrail scattering effects” has been realized and updated in the Range-Doppler mapping result figures.

Generic Usability Example Enhancements:

  • Minor usability improvement for: <AutomotiveRadar_PhasedArrayTx.wsv> example;
  • Major usability improvements for: <AutomotiveRadar_PMCW_MIMO.wsv> example:
    • Improved parameter setting using equations, hard-number settings avoided;
    • Added Text Boxes for each sub-system part groups and important observation points for the customer to review, corresponds to result graphs;
    • Enabled grouped multi-target setting in one target model;
    • Improved Figure Texts to be consistent with observation point settings in the schematic; 

Model Defect improvements:

  • <PhasedArray Tx & Rx> models:
    • Both models fixed for extremely large output signal defect for ULA (element number > 8);
    • <PhasedArrayRx> model is updated to enable the bus size inconsistency error report if ArrayInput port size is NOT consistent with desired target number;
  • <Platform> and <TargetScatterLoc> models are updated to enable error report if Velocity/Acceleration/Jerk under Simple XYZ Frame is set to vector size other than 3;
  • <CFAR> model is fixed for the inconsistent output data defect if CFAR type == ClutterMap;
  • Parameter range checking fixings have been done to: <MicroDopplerTarget>,  <CFAR>, <Ground_Clutter>, <RCS>, <TargetScatterLocation>, <TargetTrajectory> models;
  • <DDS> model output timing defect fixed with properly timed output samples;

Example improvements:

  • All shipping examples are fixed for excessive warnings and errors.
  • The remaining warnings are assumed to be expected by design and are explained in example notes.

End of Life (EOL) support 

WiMAX Baseband Verification Library

Keysight announces feature End of Life (EOL) support for WiMAX Baseband Verification Library (W1911EP) effective PathWave System Design (SystemVue) 2021.

The WiMAX Baseband Verification Library has been moved under <InstallDirectory>\EndOfSupport\Autoload.

The WiMAX Baseband Verification Library examples are identical to the examples that are shipped with the previous version of SystemVue. You can access/copy them from there.

SystemC Library and features

Keysight announces feature End of Life (EOL) support for the SystemC Library and features effective PathWave System Design (SystemVue) 2021.

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. 

  • While naming a workspace, do not use non-alphanumeric characters as Equation calculations may fail with errors.

Licensing and Installation


  • SystemVue requires: a) the version 2020.02 of the EEsof EDA licensing software, b) a minimum code-word version 2020.02 or above, and c) the licensing server software, lmgrd and agileesofd, to be upgraded to at least the same versions as what are included in EEsof EDA Licensing software 2020.02  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 2020.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, 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

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